I just traded a couple of emails with Josh Bogart about his problem with VNC install from on-console on a Win2K server.
It turns out Floyd's method from "Can I install VNC via Terminal Services?" was THE answer. Since this will show up in a different thread than the one Floyd Russell was responding to, I am repeating his instructions for doing it this way. I'm also going to try snapshotting a clean install of VNC on TS at some point and see what the entire set of registry changes is when taking various routes through the setup process... > -----Original Message----- > From: Floyd Russell [mailto:[EMAIL PROTECTED]] > Sent: 26 April 2002 15:56 > To: [EMAIL PROTECTED] > Subject: RE: Can I install VNC via Terminal Services? > > This is such a neat problem. I figured it out one day because it irrated > me so much. > > 1. Install VNC > 2. Install VNC Service > 3. Start->Programs->VNC->Run WinVNC(AppMode) > 4. Enter your password, this is for the current user. > 5. Start->Programs->VNC->Administrative Tools->Show Default Settings > 6. Enter your password, this is for the local machine > 7. Close WinVNC > 8. Start WinVNC Service > > You may need to start the service helper if you want to modify settings > of the winvnc instance running. This problem is due to the way Terminal > Services operates. Since you are working in a virtual desktop. --------------------------------------------------------------------- To unsubscribe, mail [EMAIL PROTECTED] with the line: 'unsubscribe vnc-list' in the message BODY See also: http://www.uk.research.att.com/vnc/intouch.html ---------------------------------------------------------------------
