Installing Update Rollup 6 SCOM 2012 Sp1

Standard

In this blog post I will take you true the steps of installing System Center Operations Manager 2012 Sp1 update Rollup 5 to Update Rollup 6

The following issues are fixed in this Update

  • Service Level Objectives (SLO) dashboards sometimes load in several seconds and sometimes take minutes to load. Additionally, in some cases, the dashboard is empty after it loads.
  • SQL Time Out Exceptions for State data (31552 events) occur when you create Data Warehouse work flows.
  • This update rollup includes a fix for the dashboard issue that was introduced in Update Rollup 5.
  • Adding multiple regular expressions (RegEx’s) to a group definition causes a SQL exception when adding or running the group.
  • The System Center Operations Manager console is slow to load views if you are a member of a custom Operator role.
  • All IBM WebSphere application servers that run on Linux or AIX computers will not be automatically discovered by the Management Pack for Java Enterprise Edition (JEE) if multiple application servers are defined in a single WebSphere profile.

    You can download the Update Rollup 6 form here

    The following steps outline the process of installing the Update

    1. Backup the operations Manager Databases and unsealed Management Pack’s
    2. Install Update to the Management server
    3. Install update to the secondary Management Servers
    4. Install update to the gateway servers
    5. Install update to the ACS servers
    6. Install Update to the Web Console
    7. Install Update to the Operations Manager Console
    8. Run the SQL scripts
    9. Import Management Pack’s
    10. Deploy the update to the agents

    1. Backup the operations Manager Databases and unsealed Management Pack’s

    I did a manual backup from my databases using the SQL Console

    1. Start the "SQL Server Management Studio"
    2. Connect to the Database server
    3. Right click on the database that you want to backup, select "Tasks" and click "Backup

      BackupDatabase

    4. On the "Backup Database Select the setting that you want to use and click "Ok

      BackupRunning

    5. When the Backup is completed click "Ok"
    6. Repeat the steps Above for all the databases

    U can backup your management pack’s using the following command:

    Get-SCManagementPack | Export-SCManagementPack -path D:\Backup\MP

    backupMP

    2. Install Update to the Management server

    1. Extract the cabinet file
    2. Start a "elevated command prompt"
    3. Run the "KB2929885-AMD64-Server.msp"

      kb2929885ManagementServer

    4. Installation is running. This can take some time.

      kb2929885ManagementServerRunning

    3. Install update to the secondary Management Servers

    I installed the update the same way is installed it on the Management Server. So follow Step 2

    4. Install update to the gateway servers

    1. Extract the cabinet file
    2. Start a "elevated command prompt"
    3. Run the "KB2929885-AMD64-Gateway.msp"

      kb2929885Gateway

    4. The update doesn’t give any feedback. Check the application event-viewer if the setup is finished.

    5. Install update to the ACS servers

    1. Extract the cabinet file
    2. Start a "elevated command prompt"
    3. Run the "KB2929885-AMD64-ENU-ACS.msp"

      kb2929885Acs

    4. The update doesn’t give any feedback. Check the application event-viewer if the setup is finished.

    6. Install Update to the Web Console

    1. Extract the cabinet file
    2. Start a "elevated command prompt"
    3. Run the "KB2929885-AMD64-ENU-WebConsole.msp"

      kb2929885Webconsole

    4. Installation is running. This can take some time.

      kb2929885WebConsoleRunning

    5. The update doesn’t give any feedback. Check the application event-viewer if the setup is finished.
    6. After installing the update, you need to add the following line to the %windir%\Microsoft.NET\Framework64\v2.0.50727\CONFIG\web.config file:

      < machineKey validationKey="AutoGenerate,IsolateApps" decryptionKey="AutoGenerate,IsolateApps" validation="3DES" decryption="3DES"/>

      I did that using the following steps:

      • Start "Powershell" as administrator and stop the IIS Service "iisreset /Stop"
      • In a text editor such as Notepad, open the application-level Web.config.default file.
      • In the Web.config.default file, locate the "<system.web>" section.
      • Under the "<system.web>" add the following line:

        < machineKey validationKey="AutoGenerate,IsolateApps" decryptionKey="AutoGenerate,IsolateApps" validation="3DES" decryption="3DES"/>

      • Start "Powershell" as administrator and stop the IIS Service "iisreset /Start"

    7. Install Update to the Operations Manager Console

    1. If you do not want to restart the computer after you apply the console update, close the console before you apply the update for the console role.
    2. Extract the cabinet file
    3. Start a "elevated command prompt"
    4. Run the "KB2929885-AMD64-ENU-Console.msp"

      kb2929885Console

    5. Installation is running. This can take some time.

      kb2929885WebConsoleRunning

    6. I did a restart of the computer.

    8. Run the SQL scripts

    1. Start the "SQL Server Management Studio"
    2. Connect to the Database server and select the OperationManagerDW" Database

      SelectOperationManagerDW

    3. On the File menu, click Open, browse to D:\Program Files\System Center 2012\Operations Manager\Server\SQL Script for Update Roll ups , select the "UR_Datawarehouse" file and then click Open.
    4. When the file is loaded, click "Execute" in the SQL Editor tool bar
    5. Your Result should look something like:

      RowsAffected

    Next we need to run the following script against the OperationsManager database

    1. Start the "SQL Server Management Studio"
    2. Connect to the Database server and select the OperationManager" Database

      SelectOperationManager

    3. On the File menu, click Open, browse to D:\Program Files\System Center 2012\Operations Manager\Server\SQL Script for Update Roll ups , select the "update_rollup_mom_db" file and then click Open.
    4. When the file is loaded, click "Execute" in the SQL Editor tool bar
    5. Your Result should look something like:

      RowsAffected3

    8. Import the management Pack

    1. Start the System Center Operations Manager Console and select the "Administration pane"
    2. Right click "Management Pack" and click "Import Management Packs…"
    3. In the "Import Management Packs" and click "Add" and click "Add from Disk…"
    4. Browse to "D:\Program Files\System Center 2012\Operations Manager\Server\Management Packs for Update Rollups" and select the management Pack’s in that folder
      • Microsoft.SystemCenter.AlertAttachment.mpb
      • Microsoft.SystemCenter.IntelliTraceProfiling.mpb
        • Microsoft.SystemCenter.IntelliTraceCollectorInstallation.mpb which should be installed from SCOM 2012 SP1
        • MediaMicrosoft.Windows.InternetInformationServices.Common.mpb which should be installed from the online catalog
      • Microsoft.SystemCenter.Visualization.Library.mpb
      • Microsoft.SystemCenter.Image.Library.mp
      • Microsoft.SystemCenter.Advisor.Internal.mpb
      • Microsoft.SystemCenter.Apm.Infrastructure.Monitoring.mp
      • Microsoft.SystemCenter.Apm.Infrastructure.mpb
      • Microsoft.SystemCenter.Apm.Library.mpb
      • Microsoft.SystemCenter.DataWarehouse.Report.Library.mp p
      • Microsoft.SystemCenter.DataWarehouse.Reports.mp
      • Microsoft.SystemCenter.DataWarehouse.ServiceLevel.Report.Library.mp
      • Microsoft.SystemCenter.TFSWISynchronization.mpb
      • Microsoft.SystemCenter.Visualization.Component.Library.mp
      • Microsoft.SystemCenter.Visualization.Component.Library.mpb
    5. Click "Install"
    6. Click "Close"

    10. Deploy the update to the agents

    1. Start the System Center Operations Manager Console and select the "Administration pane"
    2. Select " Device Management" and then "Pending Management"
    3. Select the a "Agent" and click "Approve"

      Aprove

    4. On the "Agent Update" page click "Update"

      Update

    5. when you open de the "Agent by Version" you should see something like this:

      Ready

    More information on installing Update Rollup 6 for System Center Operations Manager 2012 sp1 can be found here. To install this Update Rollup 6 I used the deployment plan from Kevin Holman

    Installing Cumulative Update 7 SCOM 2007 R2

    Standard

    In this blog post I will take you true the steps of installing System Center Operations Manager 2007 r2 Cumulative Update 7

    The following uses are fixed in this Update

    • Console performs poorly when User Roles are used to scope object access.
    • Availability data is not shown for the current day when daily aggregation is used.
    • Behaviour is inconsistent between some views on web console and console.
    • Log files do not roll over when the Unicode log file is monitored.
    • Several security issues are fixed.
    • Logical disk performance statistics are not collected for some volume types on Solaris computers.
    • Some Network Adapters on HP-UX computers may not be discovered.
    • Network adapter performance statistics are not collected for HP-UX network adapters.
    • The Solaris 8 and 9 agent may not restart after an ungraceful shut-down.

    You can download the Cumulative Update 7 form here

    The following steps outline the process of installing the Update

    1. Backup the operations Manager Databases and unsealed Management Pack’s
    2. Apply the hot fix to the RMS
    3. Run the SQL Scripts after you updated the RMS
    4. Import the management Pack provided
    5. Install update to the secondary Management Servers
    6. Install update to the gateway servers
    7. Deploy the update to the agents
    8. Install the update to the computers that using the Console
    9. Install the update to the web console
    10. Install the update to the ACS Servers
    11. Update the manual installed agents

    1. Backup the operations Manager Databases and unsealed Management Pack’s

    I did a manual backup from my databases using the SQL Console

    1. Start the "SQL Server Management Studio"
    2. Connect to the Database server
    3. Right click on the database that you want to backup, select "Tasks" and click "Backup

      BackupDatabaseSCOM

    4. On the "Backup Database Select the setting that you want to use and click "Ok"

      RunBackupScom

    5. When the Backup is completed click "Ok
    6. Repeat the steps Above for all the databases

    U can backup your management pack’s using the following command: "get-managementpack | export-managementpack -path c:\backup"

    2. Apply the hot fix to the RMS

    First you need to install the hot fix Utility

    1. Run the "SystemCenterOperationsManager2007-R2CU7-KB2783850-X86-X64-IA64-ENU.MSI"
    2. On the "System Center 2007 R2 Hot fix Utility License Agreement" page click "I Agree" and click "Next"
    3. On the "System Center 2007 R2 Hot fix Utility Information" page click "Next"
    4. On the "Select Installation Folder" page, Put in the settings you want and click "Next"

      InstallHotfixFolder

    5. On the "Confirm Installation" page click "Next"
    6. On the "Installation Completed" page click "Close"

    Now its time to do the update on the RMS

    1. Browse to the place you installed the hot fix Utility and start the "Launch Cumulative Update Set-up"
    2. On the "System Center Operations Manager 2007 Software update" splash screen click "Run Server update"

      RMSupdate1

    3. The installation Process will start automatic and click finish when completed

      RMSUpdate2

    4. You have to click finish three times

    3. Run the SQL Scripts after you updated the RMS

    Now Run the SQL Scripts that must be applied manually to the database

    1. Start the "SQL Server Management Studio"
    2. Connect to the Database server and select the OperationManager Database
    3. On the tool bar, click New Query

      NewSQLQuery

    4. On the File menu, click Open, browse to C:\program files (x86)\System Center 2007 R2 hot fix utility\KB2783850\SQLUpdate, select the "CU_Database.sql" file that was extracted by the Windows installer (.msi file), and then click Open.
    5. When the file is loaded, click Execute in the SQL Editor tool bar
    6. Your Result should look like:

      CUdatabasesSQLResult

    7. Select the OperationsManagerDW database
    8. On the File menu, click Open, browse to C:\program files (x86)\System Center 2007 R2 hot fix utility\KB2783850\SQLUpdate, select the "CU_DataWarehouse.sql" file that was extracted by the Windows installer (.msi file), and then click Open.
    9. When the file is loaded, click Execute in the SQL Editor tool bar
    10. Your Result should look like:

      CUDatawarehouseSQLResult

    4. Import the management Pack provided

    1. Start the System Center Operations Manager Console and select the "Administration pane"
    2. Right click "Management Pack" and click "Import Management Packs…"
    3. In the "Import Management Packs" and click "Add" and click "Add from Disk…"
    4. Browse to "D:\Program Files (x86)\System Center 2007 R2 Hot fix Utility\KB2783850\ManagementPacks" and select the management Pack’s in that folder
      • Microsoft.SystemCenter.DataWarehouse.Report.Library.mp
      • Microsoft.SystemCenter.WebApplication.Library.mp
      • Microsoft.SystemCenter.WSManagement.Library.mp
    5. Click "Install"
    6. Click "Close"

    5. Install update to the secondary Management Servers

    I installed the update the same way is installed it on the RMS. So follow Step 2

    6. Install update to the gateway servers

    I installed the update the utility on the gateway server and instead of running the Run Server Update I ran the "Run gateway update"

    7. Deploy the update to the agents

      1. Start the System Center Operations Manager Console and select the "Administration pane"
      2. Select " Device Management"

    and then "Pending Engagement"

    • Select the a "Agent" and click "Approve"
    • On the "Agent Update" page click "Update"

      UpdateAgent

    • When the Update of the agent is finished you should see:

      UpdateAgentSuccesfull

    8. Install the update to the computers that using the Console

    1. Run the "SystemCenterOperationsManager2007-R2CU7-KB2783850-X86-X64-IA64-ENU.MSI"
    2. On the "System Center 2007 R2 Hot fix Utility License Agreement" page click "I Agree" and click "Next"
    3. On the "System Center 2007 R2 Hot fix Utility Information" page click "Next"
    4. On the "Select Installation Folder" page, Put in the settings you want and click "Next"

      InstallHotfixFolder

    5. On the "Confirm Installation" page click "Next"
    6. On the "Installation Completed" page click "Close"
    1. Browse to the place you installed the hot fix Utility and start the "Launch Cumulative Update Set-up"
    2. On the "System Center Operations Manager 2007 Software update" splash screen click "Run Server update"

      RMSupdate1

    3. The installation Process will start automatic and click finish when completed

      RMSUpdate2

    4. You have to click finish three times

    9. Install the update to the web console

    I run my web console on a management server witch I all ready updated to Cumulative Update 7 So the only thing that I need to adjust is:

    1. Open the "Web.config" file
    2. Add the following configuration "" or when U using https ""

    10. Install the update to the ACS Servers

    When you have a standalone ACS server follow the steps mentioned in step 2 of the post

    1. Browse to the place you installed the hot fix Utility and start the "Launch Cumulative Update Setup"
    2. On the "System Center Operations Manager 2007 Software update" splash screen click "Run ACS update"

      RMSupdate1

    3. The installation Process will start automatic and click finish when completed

      RMSUpdate2

    When your finished you need to run a update to SQL database "OperationsManagerAC" on your database Server

    1. Start the "SQL Server Management Studio"
    2. Connect to the Database server and select the OperationManager Database
    3. On the tool bar, click New Query

      NewSQLQuery

    4. On the File menu, click Open, browse to %SystemDrive%\Windows\System32\Security\AdtServer\DbUpgV6toV7.sql , select the "DbUpgV6toV7.sql" file that was extracted by the Windows installer (.msi file), and then click Open.
    5. When the file is loaded, click Execute in the SQL Editor toolbar
    6. Your Result should look like:

      DbUpgV6toV7SQLResult

    11. Update the manual installed agents

    You can install this manual using the following command "msiexec.exe /p "C:\temp\CU7_Agent\KB2783850-x64-Agent.msp" REBOOT="ReallySuppress"

    More information on installing System Center Operations Manager 2007 r2 can be found here. To install this Cumulative update I used the deployment plan from Kevin Holman

    System Center Operations Manager Firewall ports

    Standard

    When installing System Center Operations Manager you want to keep the local firewall on your servers up and running. You can use the following commands to open the ports you need.

    For the command's below to work run the "command prompt as administrator".

    Run this on the SQL Server that is the Database server for your Management Servers:

    • netsh advfirewall firewall add rule name = SQLPort dir = in protocol = tcp action = allow localport = 1433 remoteip = localsubnet profile = DOMAIN
    • netsh advfirewall firewall add rule name = SQLBrowserPort dir = in protocol = tcp action = allow localport = 1434 remoteip = localsubnet profile = DOMAIN
    • netsh advfirewall firewall add rule name = ServiceBroker dir = in protocol = tcp action = allow localport = 4022 remoteip = localsubnet profile = DOMAIN

    un this on the Server that is the The web server for Operations Manager:

    • netsh advfirewall firewall add rule name = HTTP dir = in protocol = tcp action = allow localport = 80 remoteip = localsubnet profile = DOMAIN
    • netsh advfirewall firewall add rule name = HTTPS dir = in protocol = tcp action = allow localport = 443 remoteip = localsubnet profile = DOMAIN

    Run this on each of the System Center Management Servers:

    • netsh advfirewall firewall add rule name = MgmtPort dir = in protocol = tcp action = allow localport = 5723 remoteip = localsubnet profile = DOMAIN
    • netsh advfirewall firewall add rule name = MgmtConsole dir = in protocol = tcp action = allow localport = 5724 remoteip = localsubnet profile = DOMAIN

    When you are using SNMP Network Monitoring run the following commands System Center Management Servers:

    • netsh advfirewall firewall set rule name="Operations Manager Ping Response (Echo Response – ICMPv4 IN)" new enable=yes
    • netsh advfirewall firewall set rule name="Operations Manager SNMP Response" new enable=yes
    • netsh advfirewall firewall set rule name="Operations Manager SNMP Trap Listener" new enable=yes

    More information on the "netsh advfirewall firewall" command, can be found here. If you want more information on the firewall ports take a look at the following technet article. This can be found here