You can always do a logoff of a NT/2K machine first and then do a shutdown. This would assure no user level processes are hanging. If it's a system service that is hanging, then you are kind'a SOL. You could create a batch file that would stop all possible offending services before you attempt a shutdown, and then, if you have the resource kit installed, or the SHUTDOWN.EXE, call 'SHUTDOWN /L /R /T:0 /Y'. ( Thanks Alex K. Angelopoulos)
Jake Hoover -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Tuesday, March 26, 2002 10:36 AM To: [EMAIL PROTECTED] Subject: Re: Forced Shutdown of Windows NT/2K Systems The problem needs to be addressed by the VNC developers, if PC Anywhere can do it, I don't see any reason why VNC can't. The shutdown tools are OK, but you still can't see what is happening during the shutdown process. PC Anywhere is the last service to shutdown, so you can actually stay connected and see the shutdown process, and if something hangs you know right away. We are moving to PC Anywhere because of this fact, all because of VNC service shutdown problem. VNC needs this functionality to be taken seriously by corp IT. Tony Caduto Programmer/Analyst M&I Trust and Investment Management "Alex K. Angelopoulos" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent by: cc: [EMAIL PROTECTED] Subject: Forced Shutdown of Windows NT/2K Systems ch.att.com 03/25/2002 05:18 PM Please respond to vnc-list As a general rule, I would suggest that it is a good idea to get a shutdown tool installed for NT4 and Win2k, and then use that when it is necessary to do a remote reboot - the point made earlier by Mike Miller and Tony Caduto about the lack of an integral tool for forcing shutdown produces significant issues with remote administration. (This actually reminds me of an old Mark Minasi line. At seminars he used to say that you need one specific tool for remote administration of Windows NT: a plane ticket.) I would suggest that part of the NT install/config process for administrators should involve adding specific small tools. When setting up remote control on NT 4/2000, I would suggest getting Sysinternals' psshutdown and putting it on the system. It's a 14KiB free download. URL for it is: http://www.sysinternals.com/ntw2k/freeware/psshutdown.shtml A good general command line to use for it is: psshutdown -f -r -l *DO NOT* forget the -r. -f forces shutdown; -r says to reboot after shutdown; -l specifies the local system. It defaults to waiting 20 seconds before rebooting, and can be aborted via psshutdown -a I've made it a practice in the past to put a batch file with the standard options in my path so I could quickly access it. On systems with significant resource starvation I even include a couple of preliminary lines which shut dwon the print spooler, IIS, and any other standard non-critical but memory-hungry services before initiating shutdown - then *always* rebooted via the batch file. --------------------------------------------------------------------- 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 --------------------------------------------------------------------- --------------------------------------------------------------------- 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 ---------------------------------------------------------------------
