![]() ![]() If your shop falls into the latter group (pertaining to a Windows Updates policy), we recommend a proactive regiment to reducing the length of time Windows Updates are pending. It has been our in-house experience (especially when maintaining older Windows Server versions), that “Pending” Windows updates have caused unusual behavior (system slowness, sporadic errors in log files), that when run and often requiring a reboot, have magically cleared up. Many of our customers have corporate policies that dictate a regular security and system update regiment, while other customer simply turn on automatic updates and hope for the best. However, Microsoft does make an honest attempt to improve deficiencies in software OS component and hardware drivers that can lead to poor performance. There are many reasons to maintain a frequent Windows Update regiment, mostly due to security concerns. If your organization falls into this category, I recommend that you read on. Check Windows Logs for Application and Hardware Issues.Monitor Memory Allocation and Availability.Check Disk Space Utilization and Free Space Availability.Implement a Regular Server Maintenance Plan.For those of you without this luxury, I have put together a few simple task that should help mitigate the influence of my old friends: Some of our customers have the luxury of these resources, while other customers do not. Proactive IT organizations maintain server health by first implementing a monitoring strategy that includes execution of a regular server maintenance plan. Its times like these I like to remind myself of the wisdom of my old friends “Murphy and Dodd” what can go wrong, will go wrong, and at the least convenient time”. Server performance is sluggish and at times, slowly grinds to a halt.Hardware controllers have failed, or filling event logs with errors.Memory utilization is peaked and not allowing processes to run upon demand.Disk is at a minimal or zero available space.Often we find one or more of the following: The story is often the same the system has been running flawless for months and all of a sudden, MIMS and/or field crews begin reporting server or resource access issues. On occasion, customers report MIMS ecosystem failures when nothing has changed supporting data, supporting services, MIMS server or MIMS configuration. For my second blog installment, I thought I would touch on a subject that is often overlooked, server health. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |