Jaa


How to Upgrade Agents from Operations Manager 2007 R2

 

Updated: May 13, 2016

Applies To: System Center 2012 R2 Operations Manager, System Center 2012 - Operations Manager, System Center 2012 SP1 - Operations Manager

The order in which you upgrade agents depends on how they were installed and whether you are upgrading a single-server management group or a distributed management group. For more information, see Upgrading Agents in an Operations Manager 2007 R2 Single-Server Management Group and Upgrading Operations Manager 2007 R2 Agents in a Distributed Management Group.

When you upgrade an agent, the System Center 2012 – Operations Manager installer service runs and is not removed until after the completion of the upgrade. If the agent upgrade fails, you might have to re-install the agent, because the installer service was not properly removed. If you attempt to upgrade the agent again and it fails, you should re-install the agent after you have completed upgrading all features of Operations Manager.

Use the following procedures to upgrade System Center Operations Manager 2007 R2 agents to System Center 2012 – Operations Manager agents.If you are upgrading agents that are deployed to a computer that has other Operations Manager 2007 R2 features installed, you must take the following steps:

  • If the agent is installed on a computer that has the Operations Manager 2007 R2 Operations console or web console installed, you must first uninstall the consoles before you upgrade the agents. You can do this by uninstalling System Center Operations Manager 2007 in Programs and Features. You can reinstall these consoles after upgrade is completed.

  • If the agent is installed on computer that has an Operations Manager 2007 R2 operational database and at least one Reporting feature (such as the data warehouse server or Reporting server), uninstall System Center Operations Manager 2007 in Programs and Features. Do not uninstall System Center Operations Manager 2007 Reporting.

  • If the agent is installed on a computer that is an Operations Manager 2007 R2 secondary management server, you should remove the agents from the management server. After management group upgrade is completed, you should run repair on that management server.

If you have ACS installed, after the agent upgrade is complete, you must manually start the ACS forwarding service and change the startup setting to automatic.

After you upgrade the server hosting ACS and any agents that act as ACS forwarders, you may need to re-enable ACS forwarding on the agents. In Operations console, go to the Monitoring workspace and in the navigation pane, select Microsoft Audit Collection Services, then expand Forwarder, then expand State View. If any of your forwarders do not appear, re-enable them. For more information, see How to Enable Audit Collection Services (ACS) Forwarders.

To learn more about each upgrade path and the order in which to perform each upgrade task, see the Upgrade Path Checklists for Operations Manager.

Before you follow any of these procedures, make sure that you verify that the servers in your Operations Manager 2007 R2 management group meet the minimum supported configurations for System Center 2012 – Operations Manager. This will help you determine whether you need to add any new servers to your management group before you upgrade. For more information, see Supported Configurations for System Center 2012 – Operations Manager.

You should also verify that the agents meet the supported configurations for System Center 2012 – Operations Manager. For more information, see Supported Configurations for System Center 2012 - Operations Manager.

Note

If you attempt to upgrade a 32-bit agent that was installed on a 64-bit machine, the upgrade of the agent will fail.

Note

If UAC is enabled, you must run the agent upgrade from an elevated command prompt.

Note

Information about upgraded agents might not appear in the Operations console for up to 60 minutes after performing the upgrade.

Upgrading Push-Installed Agents

To upgrade push-installed Windows agents by using the Operations console

  1. If you are upgrading agents in a distributed management group or if you have added a secondary management server, log on to the computer hosting the Operations Manager 2007 R2 Operations console. Use an account that is a member of the Operations Manager Administrators role for the Operations Manager 2007 R2 management group.

    If you are upgrading agents in a single-server management group, log on to the computer hosting the Operations Manager Operations console by using an account that is a member of the Operations Manager Administrators role.

  2. In the Operations console, click Administration.

    Note

    When you run the Operations console on a computer that is not a management server, the Connect To Server dialog box appears. In the Server name box, type the name of the management server to which you want to connect.

  3. In the Administration workspace, in the navigation pane under Device Management, click Pending Management.

  4. In the Pending Management pane, under Type: Agent Requires Update, right-click each agent-managed computer listed, and then click Approve.

    Warning

    You should not approve more than 200 agents at one time.

  5. In the Update Agents dialog box, enter the administrator account credentials, and then click Update. The upgrade status is displayed in the Agent Management Task Status dialog box.

  6. When the upgrade is completed, click Close.

Upgrading Manually Installed Agents

To upgrade a manually installed Windows agent by using the Setup Wizard

  1. Log on to the computer that hosts the agent with an Operations Manager Administrators role account for your Operations Manager 2007 R2 management group.

  2. Run Setup.exe from the System Center 2012 – Operations Manager installation media.

  3. On the first page of the Setup Wizard, click Local agent. When the Welcome to the System Center 2012 - Operations Manager Agent Upgrade Wizard page opens, click Next.

  4. In the System Center 2012 - Operations Manager Agent Setup dialog box, click Upgrade. The status page displays the progress of the upgrade.

  5. When the Completing the System Center 2012 - Operations Manager Agent Setup wizard page appears, click Finish.

To upgrade a manually installed Windows agent by using the Command Prompt window

  1. Log on to the computer hosting the agent with an Operations Manager Administrators role account for your Operations Manager 2007 R2 management group.

  2. Open a Command Prompt window by using the Run as Administrator option.

  3. Change directory to agent, and then change directory again to AMD64, i386, or ia64, as appropriate for the current system.

  4. Run the following command, where D:\ is the location for the upgrade log file.

    Note

    If you upgrade manually installed agents that also run the AVIcode 5.7 agent (or earlier versions of the AVICode agent), you must include the option: NOAPM=1 in the command. For more information, see Install Agent Using the Command Line.

    msiexec /i MOMAgent.msi /qn /l*v D:\logs\AgentUpgrade.log  
    

Verifying Windows Agent Upgrade

To verify the Windows agent upgrade

  1. In the Operations console, in the navigation pane, click the Administration button.

  2. Under Device Management, click Agent Managed.

  3. In the Agent Managed pane, verify that the value listed in the Version column is 7.0.85xx.x, where x is any positive integer.

    Note

    It can take up to one hour for the console to show the updated version of the agent.

Upgrading UNIX and Linux Agents

To upgrade UNIX and Linux agents in a distributed management group

  1. Log on to the root management server hosting the Operations Manager 2007 R2 Operations console with an account that is a member of the Operations Manager Administrators role for the Operations Manager 2007 R2 management group.

  2. In the Operations console, click Administration.

  3. At the bottom of the navigation pane, select the Discovery Wizard link.

    You must initiate the upgrade by running the Discovery Wizard in Operations Manager 2007 R2 on agents that have been moved to a secondary management server that has been upgraded to Operations Manager. There is no Pending Management feature for UNIX and Linux agents in either version.

  4. In the Computer and Device Management Wizard, select Discovery Type, select Unix/Linux Discovery Wizard, and then click Next.

  5. On the Discovery Method page, click Add.

  6. On the Define discovery criteria page, type the credentials and necessary information to locate the secondary management server, and then click OK.

  7. On the Discovery Method page, click Add to add the secondary management server to the Discovery Scope list.

  8. In the Management Server list, select the secondary management server that will monitor the agents.

  9. Click Discover to initiate system discovery.

  10. On the Discovery results page, the wizard detects that the agents are already managed and that an upgrade is available. Continue with the upgrade.

  11. Click Done to close the wizard.

Any existing Run As profiles and Run As accounts continue to have valid configurations. For information about changes to Run As profiles and accounts for UNIX and Linux monitoring in System Center 2012 – Operations Manager, see Accessing UNIX and Linux Computers in System Center 2012 - Operations Manager.

You can specify the resource pool that manages a particular UNIX or Linux computer and allows you to create a resource pool dedicated to managing only UNIX and Linux computers. For more information see Managing Resource Pools for UNIX and Linux Computers.

To upgrade UNIX and Linux agents in a single-server management group by using the Operations console

  1. On the management server that was upgraded to System Center 2012 – Operations Manager, configure at least an Agent Maintenance account (for a Run As account) for the predefined UNIX and Linux profiles. Optionally configure other accounts.

    Note

    If any UNIX or Linux agents are not upgraded to the System Center 2012 – Operations Manager version, and a Run As account is configured for a normal user account on the UNIX or Linux computer that uses sudo elevation, the elevation fails under that circumstance. A normal user account does not have root-level access or special permissions, but allows monitoring of system processes and of performance data. For more information about credentials and elevation, see Accessing UNIX and Linux Computers in Operations Manager 2012.

  2. Run the UNIX/Linux Upgrade Wizard. For more information, see Upgrading and Uninstalling Agents on UNIX and Linux Computers.

To manually upgrade UNIX and Linux agents in a single-server management group

  1. Copy the System Center 2012 – Operations Manager agent package to the managed UNIX or Linux computer. The default location of the agent package is C:\Program Files\System Center 2012\Operations Manager\Server\AgentManagement\UnixAgents.

  2. Run the appropriate package upgrade command. For example, the following command upgrades the agents on a Linux computer.

    rpm –Uvh <filename>.rpm  
    

To verify the UNIX or Linux agent upgrade

  1. In the Operations console, in the navigation pane, click the Administration button.

  2. Under Device Management, click UNIX/Linux Computers.

  3. In the Agent Managed pane, verify that the value listed in the Version column is 1.2.0-xxx, where x is any positive integer.

    Note

    It can take up to one hour for the console to show the updated version of the agent.

See Also

Upgrading Agents in an Operations Manager 2007 R2 Single-Server Management Group
Upgrading Operations Manager 2007 R2 Agents in a Distributed Management Group
Upgrading a Distributed Operations Manager 2007 R2 Environment
Upgrade Path Checklists for Operations Manager