Month: October 2013

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

The following issues are fixed in this Update

  • When you try to run a Windows PowerShell script or module in an AllSigned environment.
  • Location points are not displayed on the GSM Map dashboard because of an SQL time-out error.
  • An incorrect message description is generated when security event 5140 is monitored.
  • An empty target group is created when endpoints are enumerated.
  • By default, when a generic performance report is exported, the object information (such as server name, disk label, and so on) is collapsed, and the information is missing.
  • When you start the network node dashboard on a computer that’s running a 32-bit edition of Windows 7 Service Pack 1, CPU usage is near 99 percent, and the console may stop responding.
  • A user role that is created by using Windows PowerShell on a non-United States locale-based system does not show the Display name and Description fields in the console.
  • When network discovery is run, duplicate entries for the same device may be added to the database.
  • Availability Reports may be displayed as blank because the vStateDailyFull aggregate is returned empty.
  • The monitored health state of the System Center Advisor agent is always in a "Warning" state on the Advisor Health State dashboard.
  • Application Performance Monitoring (APM) is not functional when you upgrade to later versions of Operations Manager.
  • A website cannot be discovered or monitored on a system that’s running Internet Information Services 8 if the HTTP binding is missing from the website configuration.
  • In rare cases, the Monitoringhost.exe process on the Management Server may crash with an access violation 0xc0000005 when log files are monitored on UNIX and Linux computers.
  • When discovering a Linux computer, discovery fails during secure shell (SSH) discovery, or the operating system name and version are determined incorrectly.

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

      BackupDatabase2012

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

      BackupDatabase2012OK

    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:\Backups"

    backupMPPowershell

    2. Install Update to the Management server

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

      UpdateManagementServer

    4. Installation is running. This can take some time. (The update doesn’t give any feedback. Check the application event-viewer if the setup is still running)

      SystemcenterOperationManagementserverUpdate

    3. Install Update to the Web Console

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

      UpdateWebconsole

    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 "KB2880799-AMD64-ENU-Console.msp"

      UpdateConsole

    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 "KB2880799-AMD64-Gateway.msp"

      UpdateGateway

    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 Datawarehouse Database
    3. On the tool bar, click New Query

      newsqlquery

    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

    8. Import the management Pack

    1. Start the System Center Operations Manager Console and select the "Administation 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.Advisor.Internal.mpb
      • Microsoft.SystemCenter.AlertAttachment.mpb
      • Microsoft.SystemCenter.Apm.Infrastructure.Monitoring.mp
      • Microsoft.SystemCenter.Apm.Infrastructure.mpb
      • Microsoft.SystemCenter.Apm.Library.mpb
      • Microsoft.SystemCenter.DataWarehouse.Report.Library.mp
      • Microsoft.SystemCenter.DataWarehouse.Reports.mp
      • Microsoft.SystemCenter.DataWarehouse.ServiceLevel.Report.Library.mp
      • Microsoft.SystemCenter.Image.Library.mp
      • Microsoft.SystemCenter.IntelliTraceProfiling.mpb
      • Microsoft.SystemCenter.Visualization.Library.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"

      ApproveAgent

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

      UpdateAgent

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

      AgentUp2Date

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

    Scom Managing Fragmentation levels

    Standard

    When you have imported the Windows Server Management Pack you can get a lot of warnings saying that your drives fragmentation levels are high

    LogicalDiskFragementationWarning

    First some background information on the monitor: This monitor runs on a periodic basis (Every Saturday at 3 a.m. by default) to check the fragmentation levels of all logical drives. If fragmentation levels are found to be above threshold then by default the state of the monitor will change to "Warning" and an alert will be generated.

    I used the following steps to solve this issue:

    1. Investigate if you are using virtualization solution or physical machines
    2. Create a group for the VMWare Virtual Machine
    3. Create a Group for the Physical Machines
    4. Disable the Monitor for a Group Vmware Virtual Machine
    5. Enable the logical disk fragmentation Recovery for group Physical machines

    Investigate if you are using virtualization solution of physical Machines

    In our environment we have physical machines with local storage and Virtual Machines with storage on a SAN (Storage Area Network).
    Because we are having Virtual Machines with storage on a SAN. I contacted our SAN supplier and he advised not to use any defrag tools in the Guest OS.
    Our Physical machines with local storage can use the local installed defrag tools to defrag the local storage

    Create a group for the Virtual Machines

    1. Start the operations Manager 2012 console
    2. Select the "Authoring" pane and select "Attributes"
    3. Right click "Attributes" and click "Create a New Attribute…"

      CreateaNewAttribute

    4. On the "General Properties" page, name the attribute and give the attribute a description and click "Next"

      GeneralPropertiesAttribute

    5. On the "Discovery Method" page, choose the discovery type "Registry" on the target click "Browse" and select "Windows Computer", Select the management pack where you want to store the Attribute and click "Next"

      DiscoveryMethodAttribute

    6. On the "Registry Probe Configuration" page, select "Key" on the properties fill in the followind path "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\VMTools" and change the frequency to "86400 to run Daily and click "Finish"

      RegistryProbeConfigurationAttribute

    7. Select the "Monitoring" pane and select "Discovered Inventory" click "Change Target Type" and select "Windows Computer_Extended" (You should see a list of servers with where the Vmware Tools are installed)

      VmwareToolsInstalled

    8. Select the "Authoring" pane and select "Group"
    9. Right click "Groups" and click "Create a New Group…"

      CreateNewGroup

    10. On the "General Properties" page, name the Group and give the Group a description. Select the management pack where you want to store the Group and click "Next"

      GeneralPropertiesGroup

    11. On the "Explicit Members" click "Next"
    12. On the "Dynamic Members" click "Create/Edit Rules…
    13. On the "Create Group Wizard – Query Builder" page select "Windows Computer_Extended" and click "Add". Select "VMWare Tools", "Equels", "True" and click "Ok"

      CreateGroupWizardQueryBuilder

    14. On the "Dynamic Members" click "Next
    15. On the "Subgroups" click "Next
    16. On the "Excluded Members" click "Create
    17. Select the "Authoring" pane and select "Group"
    18. In the look for type "Vmware Virtual Machines and click "view Group Members" (You should only see the Virual Machines that have the vmware tools installed)

      ManagedObjectsGroup

    Create a Group for the Physical Machines

    1. Select the "Authoring" pane and select "Group"
    2. Right click "Groups" and click "Create a New Group…"
    3. On the "General Properties" page, name the Group and give the Group a description. Select the management pack where you want to store the Group and click "Next"

      GeneralPropertiesGroupPhysicalMachines

    4. On the "Explicit Members" click "Next"
    5. On the "Dynamic Members" click "Create/Edit Rules…
    6. On the "Create Group Wizard – Query Builder" page select "Windows Computer_Extended" and click "Add". Select "VMWare Tools", "Equels", "false" and click "Ok"

      CreateGroupWizardQueryBuilderfalse

    7. On the "Dynamic Members" click "Next
    8. On the "Subgroups" click "Next
    9. On the "Excluded Members" click "Create
    10. Select the "Authoring" pane and select "Group"
    11. In the look for type "Physical Machines and click "view Group Members" (You should only see the Physical machines)

      ManagedObjectsGroupPhysical

    Disable the Monitor for the Group Vmware Virtual Machine

    1. Start the operations Manager 2012 console
    2. Select the "Authoring" pane and select "Monitors" in the look for type "Logical Disk Fragmentation Level"
    3. Right click "Logical Disk Fragmentation Level" select "Overrides", "Disable the Monitor", "For a Group"

      OverridesDisableMonitor

    4. On the "Select Object" select the group you created above and click "Ok"

      SelectObject

    5. On the "Override Properties" click "Apply" and click "Ok"

      OverrideProperties

    6. Repeat the steps for Windows Server 2008 and Windows Server 2012

    Enable the logical disk fragmentation Recovery for group Physical machines

    1. Start the operations Manager 2012 console
    2. Select the "Authoring" pane and select "Monitors" in the look for type "Logical Disk Fragmentation Level"
    3. Right click "Logical Disk Fragmentation Level" select "Overrides", "Override Recovery", "Logical disk defragmentation", "For a Group"

      OverrideRecovery

    4. On the "Select Object" select the group you created above and click "Ok"

      SelectObjectPhysicalMachine

    5. On the "Override Properties" select "Enable" and change the Override Value to "false" and click "Apply" and "Ok"

      OverridePropertiesPhysical

    6. Repeat the steps for Windows Server 2008 and Windows Server 2012

    If you did the configuration You virtual machines will not give any warnings for Logical disk fragmentation and physical machines will run a auto recovery.