Yes. Essentially the experience of using one of these terminals is that of every user having the host machine at their desk to use as their own computer with the exception of actual workload the machine is handling.
I should be able to set the host machine up as if it were just one pc of many running on a domain. Only in this case it almost becomes a 1-to-1 model which is the only reason I said "perhaps a domain server". I think a domain server will be the way to go, but since Ncomputing changes some of the dynamics, my thoughts remain open to alternative ideas.
These are good sugestions. It is my fault that I did not say in my OP that I wanted to run with a file server as you say. My original thinking included a concern for disk access to the host OS. But I know the load (at least for now) should not be sufficient to really create much bottle necking. Unfortunately this project has had some delays and somewhere along the way, I think I have strayed from my original plan with distorted thinking which creeped in along the way. Discussing things like this will help in grounding my thoughts as well as provide ideas and input that I may be able to incorporate.
I will look into Deep Freeze and Johnny Long. Thank you.
Ncomputing could be considered a zero client. I feared thin clients would present too much maintenance. Where there is an OS, there are bound to be administrative problems. A zero client eliminates the potential points of failure which was a big consideration. This way, troubleshooting is confined to only the host machines and the servers.
Ncomputing's Vspace can be installed into vmware or other virtual server solutions so the host machine becomes a server and the host becomes a virtual machine.
I would prefer to get as much right as I can from the start rather than potentially redesigning the deployment. Unfortunately I don't have as much time as I would like for testing... no testing phase at all. So I will need to deploy to production and then hopefully I will be able to setup a secondary host machine to use for testing over time and can then redeploy once I am more seasoned with Ncomputing and have gained a better understanding of how it can be deployed from a virtual machine.
I have had some discussion with Ncomputing reps. I need to have more. I also need to address this on the forum at Ncomputing's site.
I decided to start here since I felt that individually, topics like raid, NAS, server virtualization, etc were topics this forum would be especially good at. Plus I thought people here might find this an interesting subject matter.
Running Ncomputing's Vspace from within a virtual server such as vmware is not officially supported by Ncomputing. They leave it to users to figure out amongst themselves on the forums. I will need to address putting the host on a virtual machine on their forums, but I am not that far along yet. For now, I need to get things started.
This is essentially an entire office from the ground up. No infrastructure exists yet. I have my work cut out for me, but I have a chance to try getting this right from the start... well at least to try to get much of it right from the start.
