Hi there, I run WinVNC-3.3.3r9 on many W2K_Servers as service. Problem is if I remotely initiate a shutdown or reboot, the VNC is one of the very first processes to be stopped. If after that any of the running applications or services cannot close properly, i.e. user interaction is required, I have to go to the machine to press OK. I know there is no 100% solution to this, the VNC Service has to stop at some time and there can always be errors after that. But e.g. ControlIT stops very much later, so if there is let's say an open notepad.exe which asks at shutdown to save or cancel the document, with ControlIT you can say save, with VNC you're already disconnected. Any ideas how to solve this? Is there a way to tell NT/W2K to kill VNC later? At the very last? :) Thanks, -- Daniel --------------------------------------------------------------------- To unsubscribe, send a message with the line: unsubscribe vnc-list to [EMAIL PROTECTED] See also: http://www.uk.research.att.com/vnc/intouch.html ---------------------------------------------------------------------
