2000 server remote re-boot

[alex0628]

We have multiple shifts, so I can only re-boot the servers during the weekend. I don't care to drive into work on a Saturday. We have a VPN. Can I VPN into my network and re-boot the server via terminal services? If I do, will the server re-boot and be accessible come Monday morning?

 

[Goner05]

Yes this will work, but be aware if somthing burps during the rebooting you will have to drive in anyways, or deal with it monday.

Goner05

 

[technome]

Gonner05 is on the mark...
Rebooting via a remote connection works >90% of the time. There are DRAC cards and devices which connect to the power cord for the other 10%.

........................................
Chernobyl disaster..a must see pictorial

http://www.kiddofspeed.com/default.htm

 

[alex0628]

Thanks for the answers. I get tired of all of the daily or weekly Microsoft updates and was hoping to do it this way so I can update the servers, but not deal with going to the office so often. Up to now, I've been ignoring all of the updates. Unless I can find a way to perform a re-boot during office hours, this should work.

 

[Goner05]

A good way that I do it is to download the updates at lunch and restart the servers just before I go home at the end of the day. I then show up 15-20 min early the next day to make sure everything went ok.

Goner05

 

[alex0628]

Unfortunately for me, I work for a manufacturer and second shift works until midnight. I can only re-boot on the weekends.

If no one is writing to the servers, can't I re-boot at, say lunchtime, and not affect the users? Won't all of the Win2000 and XP desktops re-connect once the server is back up?

 

[markdmac]

Why not schedule a reboot for after midnight?

put this code into a txt file and give it a .VBS extension. Then add it to the scheduled tasks for an evening launch at 1AM. Remote in at say 5:00AM just to see if you need to get into the office early and you should be OK.

As has been noted however there are always risks associated with remote restarts of servers, but my experience is those are the exceptions and not the rules.

mname = "."

Set OpSysSet = GetObject("winmgmts:{impersonationLevel=impersonate,(RemoteShutdown)}//" & mname).ExecQuery("select * from Win32_OperatingSystem where Primary=true")
		for each OpSys in OpSysSet
			OpSys.Reboot()
 		next

I hope you find this post helpful.

Regards,

Mark

 

[technome]

With multiple server why not us WUS, at least for getting the MS patches downloaded to a machine in your network, automatically.

With multiple clients I manually update server via TS. The only time reboots fail is due to patch bugs, mainly with TS, which does not get tested well by MS.

I would love to have a control center with the ability to reboot all devices in the server rooms, particularly the firewall routers (expensive)..I have more freeze-ups with these than with servers not rebooting

........................................
Chernobyl disaster..a must see pictorial

http://www.kiddofspeed.com/default.htm