The following is the methodology for that idea.
I can't count the number of times that we have been patching Exchange, ISA, or even the server OS itself and we have been kicked off. No RWW access, no access via VPN.
The only respite in that case was, up until this point, to have someone log in and reboot the server, head down to the client site, or have a back door into the system.
So, how do we schedule a reboot?
It is actually very simple.
- Log on to the server as admin.
- Right click on the desktop and create a new text document.
- shutdown -r -t 30 -f
- The -r is for Restart, the -t is the time delay for the restart with the amount of time expressed in seconds after it, the -f forces the shutdown no matter what service tries to deny it. This last one is VERY important.
- You can change the time delay to whatever you want to. We suggest 30 to 90 seconds. This time setting is not the way to "schedule" the reboot by the way. Continue on for that.
Susan, awesome tip! Thank you very much for sharing it as it solves a dilemma many of us would never even have come close to figuring out.
Kudos to the person who shared the tip with Susan!
UPDATE 2007-06-05: One thing that I missed with regards to the remote reboot!
Make sure to leave the Scheduled Tasks window open so that you can delete that scheduled task if you do NOT get kicked off your RDP session!
Otherwise, you will get a surprise when the scheduled reboot kicks in if you are still working on the server!
Microsoft Small Business Specialists