It can depend on what options the particular thin client has. I have some set up that when the user hits the power button, the thin client boots, connects to a predefined server and displays the Windows login screen for that server session. When the user enters thier name/password, thier profile starts up a set program. (You have full Windows profile control there) On other units, I have it setup that when the client boots, it lists two connections (different servers) and the user clicks on the one they want to connect to. The rest is automatic and the Windows login screen appears.
On most thin clients you have options such as redirecting serial/printer/usb ports (2003), auto login, various network controls, and reconnect settings. As far as Windows TS is concerned, the session does not start until the thin client connects to the server and the user sees the login screen. When they logoff, the session closes. However, if the connection gets broken, such as the internet drops out, the session continues to run on the server (if you have it set this way). When the client reconnects, the user sees the screen running exactly as it was when the connection was broken. This is really great for remote sites where the internet connection can be suspect. No crashed databases! -Bob -- Thompson Technology Consultants LaPorte, IN 46350 219-363-7441 -------------- Original message -------------- From: Lawrence Lustig <[EMAIL PROTECTED]> << The machines boot into the specific applications we have assigned to them, but there is no reason you couldn¢t boot into a desktop session. >> What I'm asking here is do the machines boot locally, and then the user connects to the remote session or, when they boot, are the _already_ attached and running a remote session. I'd like the experience to be as much as possible like "boot and go" instead of the user having to worry about the local and remote desktop. If they never see the local machine's operating system or desktop, it's fine by me. -- Larry
