I'm giving the installation of VNC 3.3.4 on a Windows 2000 Terminal Server a rating of 9.9 (because there is never a 10).
This works great for Win2K console access. The only thing you need to do is check the "register as a service" and "start the service" settings during install, and it is immediately available. Simplest setup for Win2K I've done yet... Here's the process I followed. ================ Test Platform Windows 2000 SP3 TS in licensed Application Mode. (System was actually a VMware machine) ================ Install Process (1) Manually did a "change user /install" since I prefer controlling the entire process (and this ensures that it stays in install mode until I say stop). (2) Did the default install with the following 2 modifications on the "Select Additional Tasks" screen: + checked "Register as a service" + checked "start the service" (3) After setup completed, the service window launched and I set the password. (4) switched to execute mode with "change user /execute". ================= Post-Install Testing I was immediately able to connect successfully to the console session with no one logged on and with one other user logged on remotely. Logging on to the console directly first and then opening VNC and connecting worked fine as well. I powered the machine down completely, then restarted. VNC access was available moments after the Ctl-Alt-Del screen popped up on the VMware virtual console. Again, no issues with logging on. _______________________________________________ VNC-List mailing list [EMAIL PROTECTED] http://www.realvnc.com/mailman/listinfo/vnc-list
