Applying update rollup 5 to Operations Manager 2012 Service Pack 1

3:19 pm in #scom, #sysctr by Jan Van Meirvenne

Hey guys, this is a quick procedure based on the official KB guide @ http://support.microsoft.com/kb/2904680

This guide assumes that you are running with administrative rights.

  • Validate the sources
    • Download all updates from Microsoft Update
    • Extract the appropriate cab files
      For each downloaded update, enter its downloaded folder and extract the cab file. If more than one cab file is present then extract each file containing your language code (usually ENU) and / or processor architecture (x64 or x86). The other cab files can be deleted.
    • Create folder structure
      • Create a folder structure like this:

      • Move the extracted MSP files in their appropriate folder
  • Apply the update to
    • Management Servers
      • Perform these steps for each management server
        • Log in on the system
        • Use a file explorer to go to the remote or local location of the patch file structure you created
        • Go to ‘Server’, right-click the MSP file and click ‘Apply’
        • When the installation completes, you will be prompted for a reboot, do this as soon as you can.
    • Gateway Servers
      • Perform these steps for each gateway server
        • Log in on the system
        • Use a file explorer to go to the remote or local location of the patch file structure you created
        • Go to ‘Server’, right-click the MSP file and click ‘Apply’
        • When the installation completes, you might be prompted for a reboot, do this as soon as you can.
    • ACS
      • Perform these steps for each gateway server
        • Log in on the system
        • Use a file explorer to go to the remote or local location of the patch file structure you created
        • Go to ‘ACS’, right-click the MSP file and click ‘Apply’
    • Web console servers
      • Perform these steps for each web console server
        • Log in on the system
        • Use a file explorer to go to the remote or local location of the patch file structure you created
        • Go to ‘WebConsole’, right-click the MSP file and click ‘Apply’
        • Use a file explorer to navigate to ‘C:\Windows\Microsoft.NET\Framework64\v2.0.50727\CONFIG’ and open the web.config file
        • Add the following line under the system.web node in the xml structure:

<machineKey validationKey=”AutoGenerate,IsolateApps” decryptionKey=”AutoGenerate,IsolateApps” validation=”3DES” decryption=”3DES”/>
  • Operations Console servers
    • Perform the following steps on all systems with an Operations Console
      • Log in on the system
      • Use a file explorer to go to the remote or local location of the patch file structure you created
      • Go to ‘Console’, right-click the appropriate (x86 or x64)MSP file and click ‘Apply’
  • Update the databases
  • Data Warehouse
  • Connect to the Operations Manager Data Warehouse using SQL management studio
  • Use the studio to load the following query-file from a Operations Manager management server:
< Base Installation Location of SCOM>\Server\SQL Script for Update Rollups\UR_Datawarehouse.sql

  • Execute the loaded query against the Operations Manager Data Warehouse database
  • Operational
    • Connect to the Operations Manager database using SQL management studio
    • Use the studio to load the following query-file from a Operations Manager management server:
< Base Installation Location of SCOM>\Server\SQL Script for Update Rollups\update_rollup_mom_db.sql

  • Execute the loaded query against the Operations Manager database
  • Import the management packs
    • Open the Operations Console and connect to the management group you are updating
    • In the left hand pane, go to ‘Administration’, right-click on ‘Management Packs’ and choose ‘Import Management Packs’
    • In the dialog, click ‘Add’ and select ‘Add from diskā€¦’. When prompted to use the online catalog, choose ‘no’.
    • In the file select dialog, navigate to the following location on a management server and select all files, click ‘Open':
<Root SCOM Installation Directory>\Server\Management Packs for Update Rollups

  • The import dialog will complain about a missing dependency management pack called ‘Microsoft.SystemCenter.IntelliTraceCollectorInstallation.mpb’. You must use add this dependency by using the same method as the previous management packs. This file can be found under the ‘ManagementPacks’ folder on the SCOM installation media.
  • When all management packs are ready to import, click ‘Import’ to import them.
  • When prompted for security consense, click ‘Yes’