Windows updating best practice

(virtual environment, virtual hosts, workloads) For instance this would result in a maintenance window for the virtual environment (where all virtual guests will go down temporarily when the virtual host reboots) every first Friday of the month, a maintenance window for all virtual Operating Systems running every second Friday of the month and a maintenance window for workloads running in the virtual guests (for instance Microsoft Exchange Server and Microsoft SQL Server) every third Friday of the month.One whole maintenance window remains to do maintenance on the Storage Area Network (SAN), the network, etc.Virtualization offers flexible means to test updates.Snapshot functionality even allows a rollback scenario for updates.

In a Microsoft server environment this would mean a divide between: Software products need to be patched to provide security and functionality.Depending on your environment you’d place your most critical layer on the second Friday of the month after you’ve tested them, since Microsoft releases updates every second Tuesday of the month.(except out-of-band updates) When you delay your updates (in lack of testing) place your most critical layer on the third Friday of the month.When your systems perform loads of transaction to other countries, you’d better apply all Daylight Savings Time (DST) patches, otherwise you can delay applying the updates a little while.Microsoft offers three levels of updates: Important, Recommended and Optional.

Leave a Reply