Hello all, Is there any frequency to reboot Window Servers? Is it advisable to reboot Window servers on a regular basis? Please advise for servers either physical or virtual. Thanks....

Is there any frequency to reboot Window Servers? Reboots are NOT needed on a regular basis just for the OS. Sometimes poorly written applications or undersized servers can change that, but that's an application issue or design issue, not an OS. Is it advisable to reboot Window servers on a regular basis? No, see above. It is advisable to patch on a regular basis (monthly), and that may require a reboot. Please advise for servers either physical or virtual. makes no difference.

also to note...If you are patching your servers at least once per month following the Microsoft Security Bulletins, your servers will be restarted during that time, for most updates. Visit: anITKB.com, an IT Knowledge Base.

Thanks for your comments. Actually my issue is as follows: - sometimes we do encounter performance issues on our windows servers, and after a reboot....it's fine. Here after rebooting, it releases the memory and perf goes high again. - do you think it's the application that is being hosted on the servers which is causing bottleneck?

Hello, it sounds for me that you are talking about lsass CPU problems: http://support.microsoft.com/kb/917257 http://blogs.technet.com/b/askds/archive/2007/08/20/troubleshooting-high-lsass-cpu-utilization-on-a-domain-controller-part-1-of-2.aspxBest regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

Hi , sometimes we do encounter performance issues on our windows servers, and after a reboot....it's fine. Here after rebooting, it releases the memory and perf goes high again. - This falls into a wide area of analysis. We need to have the systematic diagnosis of the problem to understand the root cause of the issue. When you are encountering performance problems, you need to verify the application / process which is causing the issue. There might be multiple app's consuming memory and resources and sometimes this would be very normal, for eg: if you have configured server with IIS and have all the users requests hitting the website and when all the users download certain documents, you would see w3wp.exe consuming heavy memory ( which is termed normal ). But there are other scenarios where one of the process consumes 100% cpu utilization and it would never decrease which is abnormal. This process would be from microsoft or from 3rd party vendor. Most of applications developed require the in-built microsoft dll's or sys files for their communication, so when you upgrade these files, you would see that 3rd party applications behaving wierd. Following are tools which you can use to nail down the problem a) Perfmon ( for generatingcomplete OS performance report ) b) Adplus ( for capturing the application dump )

Hello Sainath, Thanks for the post. if i understand well...you mean that the in-built microsoft dll's or sys files for the applications should be upgraded if i have upgraded my OS? let's say i have an application A...which was on a server having Win 2000. and now i have upgraded my server to Win 2003. i must upgrade the application A's dll or sys files to fit with the Win 2003 OS? Will try the tools you provided. Thanks a lot.

Hello Guys... actually when we have some performance issues on our windows servers...usually we do re-boot the server. This releases memory and performance is ok. Is there a script/tool that will release memory on our windows servers without having to re-boot the server. this will eliminate the downtime of our server. Thanks for a prompt response.

Is there a script/tool that will release memory on our windows servers without having to re-boot the server. this will eliminate the downtime of our server. Assuming the "application" is running as a Service, you can simply restart the service. The application is open on the desktop on the server, simply close and re-open. Again this isn't a OS issue, its a application issue, so in general simpy stop and restart the application(s) to release memory. Under Windows Server 2003, applications can use the memory notification function QueryMemoryResourceNotification to determine when they may allocate memory and release memory. This is essentially a dedicated thread that listens for one of two notification types: low-memory-resource or high-memory-resource. The default level of available memory that signals a low-memory-resource notification event is approximately 32 MB per 4 GB, to a maximum of 64 MB. The default level that signals a high-memory-resource notification event is three times the default low-memory value (96MB by default). As of Windows Server 2003 SP1, Windows does not balance memory across applications with the Memory Notification functions. It merely provides global feedback as to the availability of memory on the system. However, application must be written specifically to use these functions, for example SQL Server does this. Check out the More information section of the following article. It is written for SQL Server, but memory pressure and how the OS responds applies to any application. http://www.networkadminkb.com/kb/Knowledge%20Base/SQL/SQL%20Error%20A%20significant%20part%20of%20sql%20server%20process%20memory%20has%20been%20paged%20out.aspx