|
Guy recommends :
Find out which of your VMs are a waste of space and which VMs need more resources.
|
Restart Services instead of Rebooting the Windows Server 2003Is your reflex to restart services or reboot the server?Best Practice (Litmus Test)Professionals: Prefer to restart faulty servicesAmateurs: Always reboot the server - even if there is no needRestart Services - Avoid RebootsThe good news is that Microsoft have reduced the number of actions that require a reboot from over 150 in NT 4.0 to just 7 in Windows 2003. The bad news is that rebooting the server is no longer as effective in curing problems as it was in NT. On occasions where rebooting solves a problem, restarting the individual service would work just as well. Think how much downtime you will save. Restart Services (Not Server)Restarting services is particularly useful when troubleshooting Exchange 2003 or SQL problems. Rebooting the machine would achieve the same result but would take an age and other services would not be available until the restart is complete. Stopping and restarting the services is more efficient and also teaches you the dependencies of service. For example, the Exchange Information Store is dependent on the System Attendant. Where do you find the settings? Administrative tools, Services here is a thumbnail: Or try a flashy PowerShell script to restart services
7 Main causes of a reboot in Windows 2000/3
Minor causes of a reboot
|
||||
Custom Search
|
Guy Recommends:
SolarWinds Free IP SLA Monitor
|
|
Home Copyright © 1999-2012 Computer Performance LTD All rights reserved Please report a broken link, or an error. |
|