Installing Update Rollup 9 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 8 to Update Rollup 9

The following issues are fixed in this Update

  • Operational Insight through Operations Manager
  • Support for “SUSE Linux Enterprise Server systems

You can download the Update Rollup 9 form here
The downloaded files consist of an update for the “System Center Operations Manager Console” and the “System Center Operations Manager Server. 

Microsoft Update Catalog

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 Operations Manager Console
  5. Run the SQL scripts
  6. Import Management Pack’s
  7. 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

    Backup Database

  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

You can backup your management pack’s using the powershell Operations Manager shell and type 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 powershell command prompt"
  3. Run the "KB3023167-AMD64-Server.msp"

    ManagementServerUpdate

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

    ManagementServerUpdate1

  5. On the Dialog Screen "System Center Operations Manager 2012" klik "Yes" to restart the server

    ManagementServerUpdate2

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 Operations Manager Console

  1. If you don’t want to reopen the System Center Operations Manager Console close the
  2. Extract the cabinet file
  3. Start a "elevated Powershell command prompt"
  4. Run the "KB3023167-AMD64-ENU-Console.msp"

    UpdateConsole1

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

    UpdateConsole2

 

5. Run the SQL scripts

  1. Start the "SQL Server Management Studio"
  2. Connect to the Database server and select the “OperationsManagerDW" 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.SQL" 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 “OperationsManager" 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

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

    ImportManagmentPacks

  6. Click "Close"

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 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" view you should see something like this:

    Ready

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

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

The following issues are fixed in this Update

  • The Health Service bouncing that is caused by high memory usage in the MonitoringHost process.
  • This update includes a fix to prevent resynchronization of all managed entities from the Operations Manager to the Operations Manager Data Warehouse (OMDW) database and to prevent the failure to sync that this causes because of duplicate entries.
  • The import of Visualization.component.library and Visualization.library binary files (.mpb) fails. The import succeeds on a successive try.
  • System Center Operations Manager agents randomly time out when authenticating to the Gateway or Management Server because of domain controller or network performance issues. The time-out value was set to 1 second earlier. A fix was made to increase server time out to-20 seconds and client time out to 5 minutes.

You can download the Update Rollup 8 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

You can backup your management pack’s using the powershell Operations Manager shell and type 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 powershell command prompt"
  3. Run the "KB2991997-AMD64-Server.msp"

    UpdateManagementServer

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

    UpdateManagementServerRunning

  5. On the Dialog Screen "System Center Operations Manager 2012" klik "Yes" to restart the server

    UpdateManagementServerRestart

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 powershell command prompt"
  3. Run the "KB2991997-AMD64-Gateway.msp"

    UpdateGatewayServer

  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 powershell command prompt"
  3. Run the "KB2991997-AMD64-ENU-ACS.msp"

    UpdateACS

  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 powershell command prompt"
  3. Run the "KB2991997-AMD64-ENU-WebConsole.msp"

    UpdateConsole

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

    UpdateWebConsoleRunning

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

7. Install Update to the Operations Manager Console

  1. If you don’t want to reopen the System Center Operations Manager Console close the
  2. Extract the cabinet file
  3. Start a "elevated Powershell command prompt"
  4. Run the "KB2991997-AMD64-ENU-Console.msp"

    UpdateConsole

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

    UpdateConsoleRunning

 

8. Run the SQL scripts

  1. Start the "SQL Server Management Studio"
  2. Connect to the Database server and select the “OperationsManagerDW" 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.SQL" 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 “OperationsManager" 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

9. 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.mpb
  5. Click "Install"

    UpdateManagementPacks

  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 8 for System Center Operations Manager 2012 sp1 can be found here. To install this Update Rollup 8 I used the deployment plan from Kevin Holman

Backup Management Pack’s

Standard

Backup all System Center Operations Manager 2012 Management Pack’s. I took the following steps to complete this task.

Launch the System Center Operations Manager shell

OperationsManagerShell

Get-SCManagementPack | Export-SCManagementPack -Path D:\Backup\ManagementPack

OperationsManagerShellBackup

If you are using System Center Operations Manager 2007 r2 Use the following command line:

Get-ManagementPack | Export-ManagementPack -Path D:\Backup\ManagementPack

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

    Veeam Quick Migration

    Standard

    I usual y blog about System Center Operations Manager 2007 r2 or 2012. This time I am not going to blog about System Center but about migrating vmware host from one Hardware Box to another Hardware Box.

    For a customer of mine I needed to migrate his Virtual machines from one Hardware Box to Another Hardware Box. This customer was using vmware ESXi as hyper-visor with his storage directly in his server. Because the customer didn’t want to buy VMware Vsphere Enterprise just for the Storage V-Motion function. I thought Veeam Quick Migration would help and also a great option to test Veeam Backup and Recovery tool.

    Before you start the migration download the Veeam Backup Free Edition for Vmware and Hyper-V from here. I did the installation of the software on my laptop and it’s a straight forward installation

    I used the following steps to migrate the Virtual Machines:

    1. I shut-down the virtual Machines that needed to be migrated
    2. Start the Veeam backup free edition.

      StartScreenVeeam

    3. Click "Add Server" and select "Vmware VSphere"

      AddServerWizzard

    4. On the "Name" page, enter the host name or IP-address of the Server and click "Next"

      SpecifyDNSnameOrIPAdressofVMWareServer

    5. On the "Credentials" page, enter the "User name" and "Password" and click "Next"

      Credenitals

    6. On the "Summary" page, click "Finish"

      SummaryAddServer

    7. Repeat Step 3 to 6 for the other Server
    8. On the Server that you want to migrate "Right Click" and click "Quick Migration"

      RightclickQuickMigration

    9. On the "Virtual Machines" page, click "Next"

      VirtualMachinesSelection 

    10. On the "Destination" page, Select the "Host or Cluster" and the "Datastore and click "Next"

      DestinationVMwareServer.

    11. On the "Transfer" page, click "Next"

      Transfer

    12. The Job Will start

      MigrationWorking

    13. When the Job is completed you will need to start the Virtuals Machines. When you start the Virtual Machine, Vsphere will give the mention "msg.uuid.alterd: This virtual machine may have been moved OU copied". Choose "I Moved It".

    I Think this tool is extremely useful and the best part the tool is completely free. More information on Veeam Backup and Recovery can be found here