But if you start it manually on the console, or a TS session.. then its not really acting like a true service in my opinion, but thats just my view..
It will still get his job done, but will require somone logging in somehow as we both point out ) as root.. errr admin :P Unlike 'workstation' when you only have one 'screen' to deal with.. Reason i suggested the actual console, is that if it IS a network issue that is causing his TS session to drop, when he looses connection with the vnc server, his app wont die on the server... And can just reconnect at will. Too bad we cant use Xvnc on TS and get around the problem totally.. > Message: 13 > From: "Steve Palocz" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Subject: RE: RE : VNC On Terminal Server - URGENT HELP Pl. > Date: Fri, 21 Jun 2002 20:49:02 -0400 > Reply-To: [EMAIL PROTECTED] > > There is no problem running winvnc as a service on windows terminal server > as long as you install it from the console. and for the first start, start > it from the console. After that winvnc run's fine as a service, and anyone > can connect to the service and log on to the console. > Otherwise the ts connection must be active and winvnc needs to be ran as an > app. As soon as the ts connection closes, the vnc connection closes, even if > the ts didn't log off just disconnect. > > We use vnc on ts all the time for training purposes. > > Steve _______________________________________________ VNC-List mailing list [EMAIL PROTECTED] http://www.realvnc.com/mailman/listinfo/vnc-list
