Yes, no problem there. I would recommend doing a straight service installation. Here's my "recipe".
(1) Run the WinVNC install. (2) Install the service using the shortcut in VNC\Administrative Tools\Install WinVNC Service. I *would not* do the "default registry settings" since it switches some things to using global per-user settings, making it a bit more difficult to modify and diagnose. (3) Start the service ( use "net start winvnc"). You will be prompted to enter a password, which will then become the universal VNC password. At that point, you should be set. ----- Original Message ----- From: "Adam Dale" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, 2002-04-26 08:25 Subject: Can I install VNC via Terminal Services? > Hi, > > I have a couple of Win 2K Advanced Servers in a remote rack and my only > access to them is via Terminal Services (in Remote Admin mode) - is it > OK to be installing VNC (as a service) via TS or do I need to be > actually at the console to do it - i.e. can the TS session write all the > correct values to the correct registry etc? > > Thanks > > Adam Dale > --------------------------------------------------------------------- > 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 > --------------------------------------------------------------------- --------------------------------------------------------------------- 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 ---------------------------------------------------------------------
