Month: January 2014

Installing Update Rollup 5 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 4 to Update Rollup 5

The following issues are fixed in this Update

  • An error occurs when you run the p_DataPurging stored procedure. This error occurs when the query processor runs out of internal resources and cannot produce a query plan.
  • By default, data warehouse bulk-insert commands use an unchangeable 30-second time-out value that may cause query time-outs.
  • Many 26319 errors are generated when you use the Operator role. This issue causes performance problems.
  • Diagram component does not publish location information in the component state.
  • Renaming a group works correctly on the console. However the group appears with the old name when you try to override a monitor or scope a view based on group.
  • SCOM synchronization is not supported in the localized versions of Team Foundation Server.
  • An SDK process deadlock causes the Exchange correlation engine to fail.
  • In rare cases, the agent on a Solaris Zone that is configured to use dynamic CPU allocation with Dynamic Resource Pools may hang during routine monitoring.
  • Availability Reports may be displayed as blank because the vStateDailyFull aggregate is returned empty.
  • If the agent fails to retrieve process arguments from the getargs subroutine on an AIX-based computer, the monitored daemons may be incorrectly reported as offline.
  • The Universal Linux agent fails to install on Linux computers with OpenSSL versions greater than 1.0.0 if the library file libssl.so.1.0.0 does not exist.
  • Spurious errors that are related to the InstanceID property of the SCX_Endpoint are logged in the System log every four hours.

    You can download the Update Rollup 5 form here

    The following steps outline the proces 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 Web Console
    4. Install Update to the Operations Manager Console
    5. Install update to the secondary Management Servers
    6. Install update to the gateway servers
    7. Run the SQL scripts
    8. Import Management Pack’s
    9. 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 "KB2904680-AMD64-Server.msp"

      kb2901680

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

      kb2901680Runnning

    5. The update will give a reboot screen. Click "Yes to restart the server

      reboot

    3. Install Update to the Web Console

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

      kb2901680Webconsole

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

    4. Install Update to the Operations Manager Console

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

      kb2901680Console

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

    5. 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

    6. Install update to the Gateway server

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

      kb2901680Gateway

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

    7. Run the SQL scripts

    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

      UpdateRollupMomDb

    4. 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.
    5. When the file is loaded, click Execute in the SQL Editor tool bar
    6. Your Result should look something like:

      RowsAffected

    Next we need to run the following script against the OperationsManagerDB 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

      UpdateRollupMomDb

    4. 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.
    5. When the file is loaded, click Execute in the SQL Editor tool bar
    6. Your Result should look something like:

      RowsAffected2

    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.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
    5. Click "Install"
    6. Click "Close"

    9. Deploy the update to the agents

    1. Start the System Center Operations Manager Console and select the "Administation pane"
    2. Select " Device Management" and then "Pending Mangement"
    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 5 for System Center Operations Manager 2012 sp1 can be found here. To install this Update Rollup 5 I used the deployment plan from Kevin Holman

    Updating Custom Fields

    Standard

    In this blog post I will take you true the steps of updating the custom fields in System Center Operation manager 2012

    The powershell script is written by Graham Davies and you can find his blog here. So a big thanks to him

    The script will fill the following Custom fields.

    1. Customfield 1 contains the Server Principal name
    2. Customfield 2 Contains the Severity of the alert
    3. Customfield 3 Contains the Management Pack that the Alert generated.

    The following steps should be taken to make it all work.

    1. Create a Alert Resolution State Setting
    2. Place the script on you Management Server
    3. Create a System Center Operations Manager 2012 Rule

    1. Create a Alert Resolution State Setting

    1. Start the System Center Operations Manager 2012 Console and chose “Administration“Administartion
    2. Click “Settings” settings
    3. Double click “Alerts“Alerts
    4. On the “Global Management Group Settings – Alerts” Click “new“, Give the name for the “Resolution State” and enter the “Unique Id“AddAlertResolutionState
    5. Click “Ok“, “Apply“, “Ok“

    2. Place the script on you Management Server

    1. You can download the script from here. Replace the “XXXXXX” with the name of your Management ServerPlace the script on your management server. In my case I placed it on “D:\Scripts“

    3. Create a System Center Operations Manager 2012 Rule

    1. Start the System Center Operations Manager 2012 Console and chose “Authoring“Authoring
    2. Expand “Management Pack Objects” and right click “Rules” and click “Create a new rule…“CreateANewRule
    3. In the Create Rule Wizard select “Execute a command and select the destination management pack that you want to use (Note: Don’t use the Default Management pack) and click “Next“CreateRuleWizzard1
    4. On the Rule Name and Description page, Give the Rule a Name and Description. Choose the catagory you want to use and target the Rule to the “Root Management Server Emulator” and click “Next“CreateRuleWizzard2
    5. On the Schedule page, select “based on fixed simple recurring schedule” and create a period. Mine will be every 3 minutes. CLick “Next” to continueCreateRuleWizzard3
    6. On the Configure command line Execution Settings page, Enter the Full path to file “%SystemRoot%\system32\WindowsPowerShell\v1.0\powershell.exe” and the parameters “D:\Scripts\AlertUpdate.ps1“. In the additional settings enter the working directory “%SystemRoot%\system32\WindowsPowerShell\v1.0” and the timeout(in seconds) “180. Click “Create“CreateRuleWizzard4

    The rule will now run and your alert should be looking something like this.

    final

    Hope this post will help you updating your custom fields.