[OpsMgr 2012] Patience is a virtue with the System Center 2012 Operations Manager SP1 installation

Published on 2013, January the 16 by J.C. Hornbeck this article is very interesting and please read it before installing SP1 on your SCOM 2012 infrastructure. 

Now that System Center 2012 Service Pack 1 is released, you need to take care when applying this to your Operations Manager servers. As part of the Service Pack installation we make some changes to the OperationsManager database objects, adding additional indexes, etc... As all the management servers share the same database, these changes only need to be made when installing the Service Pack on the very first server you install to. When you run the Service Pack 1 installation it communicates with the database to determine if this is the first installation, and then decides if it needs to run a SQL update script or not.

This means that you need to be patient with your installation and wait for the first management server to have Service Pack 1 installed before beginning the next installation. If you don’t then the SQL script will run again and issues may occur. It is very early on in the Service Pack installation process that the management server checks to see if the DB has already been upgraded, so do not be tempted to tee up your other management servers and run through the initial wizard while you wait for the first server to install because by then it will be too late.

Read the full article directly on technet.

This posting is provided "AS IS" with no warranties.