![]() |
If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
![]()
Are there any specific recommendations or rules of thumb on how frequently
your should reboot a Windows Server 2000 or 2003 server? Is it necessary to reboot weekly, monthly, etc? Is it better to leave them running and not reboot? |
Ads |
#2
|
|||
|
|||
![]()
Don't know that MS has ever recommended periodic reboots not
required by hardware/software installation or to correct problems. MS seems to concur with general IT admin policy - never reboot a server unless absolutely necessary: "A common IT industry term for maximum reliability is "five nines," meaning that a server is running 99.999 percent of the time. (Which translates into just under 6 minutes of downtime over a year.)" See: http://www.microsoft.com/windows2000...s/relavail.asp There are more than few horror stories that begin with something like: "My server was running fine, but I thought memory usage was a little high so I decided to reboot ............." Even if there is a sign of trouble, most admins will try a service restart, run clearmem.exe, etc. before they risk rebooting a server. Doug Sherman MCSE Win2k/NT4.0, MCSA, MCP+I, MVP "consultguy" wrote in message ... Are there any specific recommendations or rules of thumb on how frequently your should reboot a Windows Server 2000 or 2003 server? Is it necessary to reboot weekly, monthly, etc? Is it better to leave them running and not reboot? |
#3
|
|||
|
|||
![]()
Hi!
We use 5 terminalservers based on w2000server. windows tends to build up some trash during operation, some applications are not nicely closed down and other app do not release all used memory after closing. Therefore we reboot these servers every night automatically, since there's no one on them anyway at that time of day. We think this helps to keep the speed and accuracy. experiments learned that if we do not reboot them regularly, our servers slow down over time. Think it depends on the apps, server configuration and the possibility of a reboot. "consultguy" wrote: Are there any specific recommendations or rules of thumb on how frequently your should reboot a Windows Server 2000 or 2003 server? Is it necessary to reboot weekly, monthly, etc? Is it better to leave them running and not reboot? |
Thread Tools | |
Display Modes | |
|
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
networking xp with 98SE issue | Paul Dean | Networking and the Internet with Windows XP | 11 | January 7th 05 06:41 PM |
Windows XP FTP Server time out errors with FTP clients | Dillboi | Networking and the Internet with Windows XP | 1 | December 3rd 04 10:00 AM |
Connecting to XP's built-in VPN Server | Jeff Cooper | Security and Administration with Windows XP | 0 | November 24th 04 02:41 PM |
error log | David King | Networking and the Internet with Windows XP | 2 | August 30th 04 04:06 PM |
Group policy defaults if the server is down | Jeffrey Mount | Networking and the Internet with Windows XP | 6 | July 16th 04 06:54 PM |