Script the shutdown of the OS's and then SSH into the ESX host and do
shutdown -h now. 

 

Psshutdown from sysinternals will do the trick, and force the
applications to close. 

 

So basically psshutdown -f \\servername <file:///\\servername>  for all
the servers ( A looping batch script would probably be the best)

 

PSShutdown v2.52 - Shutdown, logoff and power manage local and remote
systems

opyright (C) 1999-2006 Mark Russinovich

ysinternals - www.sysinternals.com

 

sage:

sshutdown -s|-r|-h|-d|-k|-a|-l|-o [-f] [-c] [-t [nn|h:m]] [-v nn] [-e
[u|p]:xx:

y] [-m "message"] [-u Username [-p password]] [-n s]
[\\computer[,computer[,...

|@file]

  -a          Abort a shutdown (only possible while countdown is in
progress)

  -c          Allow the shutdown to be aborted by the interactive user

  -d          Suspend the computer

  -e          Shutdown reason code (available on Windows XP and higher).

              Specify 'u' for unplanned and 'p' for planned

              shutdown reason codes.

              xx is the major reason code (must be less than 256)

              yy is the minor reason code (must be less than 65536)

  -f          Forces running applications to close

  -h          Hibernate the computer

  -k          Poweroff the computer (reboot if poweroff is not
supported)

  -l          Lock the computer

  -m          Message to display to logged on users

  -n          Specifies timeout in seconds connecting to remote
computers

  -o          Logoff the console user

  -p          Specifies optional password for user name. If you omit
this

              you will be prompted to enter a hidden password.

  -r          Reboot after shutdown

  -s          Shutdown without poweroff

  -t          Specifies countdown in seconds until shutdown (default is
20) or

              the time of shutdown (in 24 hour notation)

  -u          Specifies optional user name for login to remote

              computer.

  -v          Display message for the specified number of seconds before

              the shutdown. If you omit this parameter the shutdown

              notification dialog displays and specifying a value of 0

              omits the dialog.

  computer    Shutdown the computer or computers specified

  @file       Shutdown the computers listed in the file specified

 

 

easons defined on this computer (U = unplanned, P = planned):

ype   Major   Minor   Title

 U      0       0     Other (Unplanned)

 P      0       0     Other (Planned)

 U      1       1     Hardware: Maintenance (Unplanned)

 P      1       1     Hardware: Maintenance (Planned)

 U      1       2     Hardware: Installation (Unplanned)

 P      1       2     Hardware: Installation (Planned)

 U      2       3     Operating System: Upgrade (Unplanned)

 P      2       3     Operating System: Upgrade (Planned)

 U      2       4     Operating System: Reconfiguration (Unplanned)

 P      2       4     Operating System: Reconfiguration (Planned)

 U      4       1     Application: Maintenance (Unplanned)

 P      4       1     Application: Maintenance (Planned)

 U      4       5     Application: Unresponsive

 U      4       6     Application: Unstable

 

Edward Ziots

Network Engineer

Lifespan Organization

MCSE,MCSA,MCP+I, ME, CCA, Security +, Network +

[email protected]

Phone:401-639-3505

________________________________

From: [email protected] [mailto:[email protected]] 
Sent: Thursday, November 12, 2009 8:32 AM
To: NT System Admin Issues
Cc: Augusta_Kimble/[email protected]
Subject: Shutting down an entire VMWare system

 


Greetings!  As an emergency call center, we are 24 x 365.25. 

We have about 30 or so virtual servers in a VMWare ESX 3.5 system.  Its
datastore is an IBM DS 3400 SAN.  The SAN needs a firmware upgrade... 

The upgrade requires, at one point, shutting down the ESX servers and
then shutting down the SAN.  (Obviously, with the ESX servers down, the
VMWare environment ceases to exist for a period.) 

What is the least bad way to go about shutting this down?  Does one need
to log into each virtual server and power it off from the vm's OS (ie,
log into Windows, then "Start -> Shut down")?  Is it all right to, from
the VM managment system, simple right-click each one and select "power
down"?  Would it be just as "safe" to log into the ESX consoles and shut
them down from there first with the VMs running?  (We have had our
environment survive when the ESX servers shut themselves down due to a
room cooling failure, but it was rather rough on the nerves!) 

Whatever, I'm obviously not looking forward to this - but thanks!
-- 
Richard D. McClary 
Systems Administrator, Information Technology Group 
  
ASPCA(r) 
1717 S. Philo Rd, Ste 36 
Urbana, IL  61802 
  
[email protected] 
  
P: 217-337-9761 
C: 217-417-1182 
F: 217-337-9761 
www.aspca.org <http://www.aspca.org/>  
  

The information contained in this e-mail, and any attachments hereto, is
from The American Society for the Prevention of Cruelty to Animals(r)
(ASPCA(r)) and is intended only for use by the addressee(s) named herein
and may contain legally privileged and/or confidential information. If
you are not the intended recipient of this e-mail, you are hereby
notified that any dissemination, distribution, copying or use of the
contents of this e-mail, and any attachments hereto, is strictly
prohibited. If you have received this e-mail in error, please
immediately notify me by reply email and permanently delete the original
and any copy of this e-mail and any printout thereof. 
  

 

 

~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~

Reply via email to