Events
Apr 29, 2 PM - Apr 30, 7 PM
Join the ultimate Windows Server virtual event April 29-30 for deep-dive technical sessions and live Q&A with Microsoft engineers.
Sign up nowThis browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
In System Center – Operations Manager, when you install an agent on a computer, a Microsoft Monitoring Agent application is added to the Control Panel. You can use the application to change the account that the agent will use when performing actions requested by the management server to remove a management group from an agent configuration and to configure the Active Directory integration setting for the agent. To perform these tasks, you must have local Administrator permissions on the computer.
Note
If you want to automate the process of adding or removing management groups from an agent, you can use the Operations Manager cmdlets or the Agent API from the Operations Manager Agent Configuration Library, allowing you to write scripts that can automate the agent configuration process.
Note
When you save changes in the Microsoft Monitoring Agent application, the Microsoft Monitoring Agent service will be stopped and restarted.
Use the following procedure to make an Operations Manager agent a member of multiple management groups, also referred to as multi-homing. For example, an agent can be configured to report Active Directory data to the Directory Services Management Group and Exchange data to the Messaging Management Group. An agent can be a member of up to four management groups.
You don't need to use the same deployment method for all the management groups.
Note
It might take one day or longer for the discovered instances of the agent to be made part of the new management group. They will be added after the next discovery interval.
Do one of the following:
On the agent-managed computer, in the Control Panel, double-click Microsoft Monitoring Agent. In Microsoft Monitoring Agent, on the Operations Manager tab, select Add, enter the information for the new management group, and then select OK.
Run the Discovery Wizard from the Operations Manager Operations console that is connected to the new management group, select the desired computers, and deploy the agent to them. For more information, see Install agent on Windows using the Discovery Wizard. (The menu item in the Operations console named Discovery Wizard opens the Computer and Device Management wizard.)
Run the MOMAgent.msi Windows installer package on the desired computers, and modify the installation by adding a new management group. For more information, see Install Windows Agent Manually Using MOMAgent.msi.
You can use the following procedure to change the account that the agent will use when performing actions requested by the management server.
You can use the following procedure to remove a management group from the agent configuration.
Note
You can remove all management groups while leaving the agent installed. This is useful in situations such as when you want to prepare a computer for imaging and want an image with the agent installed but without assignment to a specific management group.
You can use the following procedure to change the Active Directory integration setting for an agent.
To deploy the Windows agent from the Operations console using the Discovery Wizard, review Install Agent on Windows Using the Discovery Wizard.
If you would like to manually install the Windows agent from the command line or automate the deployment using a script or other automation solution, review Install Windows Agent Manually Using MOMAgent.msi.
To understand what options and steps need to be performed to properly uninstall the agent from your Windows computers, review Uninstall Agent from Windows-based Computers.
Events
Apr 29, 2 PM - Apr 30, 7 PM
Join the ultimate Windows Server virtual event April 29-30 for deep-dive technical sessions and live Q&A with Microsoft engineers.
Sign up now