General Operations Manager 2012 upgrade tipps

Here are some general tipps if you upgrade or plan to upgrade from Operations Manager 2007 to 2012.

  1. Supported configuration
    If you recognize that your servers do not meet the required supported configurations, then do not upgrade windows. I would recommend to build a new machine and move the role to the new server.
  2. Operations Manager 2007 PowerShell snapin
    If you have PowerShell scripts running in your management packs, that utilize the Operations Manager 2007 snapin, then check that the snapin is still available on the upgraded servers.
    Open Powershell and enter get-pssnapin -registered. If you see the following lines then you can use the OM2007 cmdlets.
    Name: Microsoft.EnterpriseManagement.OperationsManager.Client
    PSVersion: 1.0
    Description: Microsoft Operations Manager Shell Snapin
    Otherwise you will need to register the snapin (also possible on management servers!).
    You will need to copy the files from a om 2007 server with the operations manager shell installed.
    You can follow this blog:
    http://derekhar.blogspot.de/2007/07/operation-manager-command-shell-on-any.html.
    You will get more time to update your scripts and management packs if you can use the old snapin in the meantime.
  3. AD Integration
    If you use AD integration in your environment then check your agents after the upgrade! I saw some strange behaviour.
    Agents that are multi-homed lost their AD integration setting. The manual added management group entry was still in there but the AD integration checkbox was empty.
    Servers with the operating system Windows Server 2003 SP2 could not read the SCP entries anymore, so we had to switch them to manual configs.  The error looked like this:
    Event ID 2000
    Source: HealthService
    Description: The Management Group failed to start. The error message is: The environment is incorrect (0x8007000A). A previous message with more detail have been logged.
    There was no previous message. Microsoft had no reason for that.
  4. Agent Error: Management Group cannot be saved

    I had this error (the management group configuration could not be saved) on one machine when I entered the management group information manually and clicked on apply. The solution was easy: Reinstall the agent. It looked like that the upgrade was not really successful.
    If that does not help try to delete the following registry keys and restart the healthservice.
    HKLM\Software\Microsoft\Microsoft Operations Manager\3.0\Agent Management Groups\[MG name]
    HKLM\System\CurrentControlSet\Services\HealthService\Parameters\Management Groups\[MG name]
  5. Fix Bug: https://systemcentertipps.wordpress.com/2012/12/17/scom-2012-upgrade-bug-health-service-ping-diagnostic-fails/
Advertisements
Post a comment or leave a trackback: Trackback URL.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: