Different product manufacturers release security updates, functional updates and fixes to known issues within their products. Keeping the products updated to the latest version helps avoiding any unexpected outages on the IT infrastructure. Products matching the latest version of the release by OEM can also provide enhanced functionality compared to legacy versions as well as improved stability of the server systems.
This document is intended to be a handbook for the administrators and IT managers for managing product updates across organization or specific server systems owned by individuals or groups. This document outlines the standard practices to be followed by the IT administrators and IT managers to ensure smoother and fault free product updates which may have been released by OEM to provide enhanced functionality, security vulnerability fix, known issue fix, rollup updates and service packs.
The goal for the Identify phase is to:
- Discover new software updates in a reliable way.
- Determine whether software updates are relevant to production environment.
- Obtain software update source files and confirm that they are safe and will install successfully.
- Determine whether the software update should be considered a normal change or an emergency, and submit a request for change (RFC) to deploy it.
Evaluate the software update and—assuming that it is approved for deployment—plan for its deployment into the production environment.
The entry point for the Evaluate and Plan phase is a request for change (RFC) for a software update that has been identified as relevant to production environment.
By the end of the Evaluate and Plan phase, it should have determined whether the change request should be classified as an emergency, reviewed and approved the request, and determined the tasks necessary to deploy the approved changes into production. Test the software update in a production-like environment to confirm that it does not compromise business-critical systems and applications.
Follow the ITIL management Process, such as Change Management and Release management.
The following permissions will be required.
1. Windows Patching: Local Administrator
2. Exchange Patching: The following group membership will be required:
· Local Administrator
· Schema Admins
· Enterprise Admins
· Domain Admins
· Organization management.Prerequisite
1. Test the patches in the Lab
2. Raise a change and wait for the approval. Also write tested in the lab.
3. Once Change has been approved go ahead with further steps.
Because of the relationship between the various server roles the recommended order of upgrade is:
· Edge Transport servers
· Client Access servers. Upgrade the internet-facing Client Access servers first.
· Hub Transport servers.
· Mailbox servers.
· Unified Messaging servers.
After upgrading the servers you should also upgrade the management tools on administrator workstations.
Note that there is no rolling back from the SP1 upgrade. If you uninstall the service pack it will remove Exchange entirely from the server, it will not revert to Exchange 2010 RTM.