|Subject:||Reboot Automation advice|
|Posted by:||MsnLincs (MsnLin…@discussions.microsoft.com)|
|Date:||Tue, 14 Apr 2009|
We were curious about how others are handling updates of mission critical
servers and thier subsequent reboots...
For example, after applying updates to our SQL 2005 server we have to reboot
it. If we reboot the SQL server, we will also have to reboot every server
that references a database on it which may be 10-15 other servers. Of those
10-15 other servers, if they are rebooted, we may have to reboot yet more
servers to resynch everything depending what services are running on the
third tier servers.
There has got to be a way to automate this so that if a server reboots, its
dependent servers are also rebooted shortly after. Would anyone have any
Thanks in advance.