Export (0) Print
Expand All

Install Agent Using the Command Line


Updated: April 13, 2016

Applies To: System Center 2016 Technical Preview - Operations Manager

You can use MOMAgent.msi to deploy System Center Operations Manager agents from the command line. Deploying agents from the command line is also referred to as a manual install.

Before you begin deployment, ensure the following conditions have been met:

  • The account that is used to run MOMAgent.msi must have administrative privileges on the computers on which you are installing agents.

  • A management group (or single management server) must be configured to accept agents installed with MOMAgent.msi or they will be automatically rejected and therefore not display in the Operations console. For more information, see Process Manual Agent Installations. If the management group or server is configured to accept manually installed agents after the agents have been manually installed, the agents will display in the console after approximately one hour.

  • If an agent is manually deployed to a domain controller and an Active Directory management pack is later deployed, errors might occur during deployment of the management pack. To prevent errors from occurring before deploying the Active Directory management pack, or to recover from errors that might have already occurred, you need to deploy the Active Directory management pack helper object by running the file OomADs.msi on the affected domain controller. The file OomADs.msi is on the computer that is hosting the agent at C:\Program Files\System Center Operations Manager\Agent\HelperObjects. After an agent has been manually deployed to a domain controller, locate OomADs.msi and double-click the file to install the Active Directory Management Pack helper object. The Active Directory Management Pack helper object is automatically installed when the agent is deployed using the Discovery Wizard.

  • Each agent that is installed with MOMAgent.msi must be approved for a management group.

MOMAgent.msi can be found in the Operations Manager installation media and the management server installation directory.

Use the following procedure to deploy an agent. For examples of ways in which you can customize the MOMAgent.msi command, see Examples of Using MOMAgent Command to Manage Agents.

To deploy the Operations Manager agent from the command line

  1. Log on to the computer where you want to install the agent by using an account with local administrator privileges.

  2. Open a command window.

  3. Run the following command:

    System_CAPS_ICON_note.jpg Note

    Ensure you use the correct 32-bit or 64-bit version of MOMAgent.msi for the computer you are installing the agent on.


    USE_SETTINGS_FROM_AD={0|1}Indicates whether the management group settings properties will be set on the command line. Use 0 if you want to set the properties at the command line. Use 1 to use the management group settings from Active Directory.
    MANAGEMENT_GROUP=MGnameSpecifies the management group that will manage the computer.
    MANAGEMENT_SERVER_DNS=MSnameSpecifies the fully qualified domain name for the management server. To use a gateway server, enter the gateway server FQDN as MANAGEMENT_SERVER_DNS.
    MANAGEMENT_SERVER_AD_NAME=ADnameUse this parameter if the computer's DNS and Active Directory names differ to set to the fully qualified Active Directory Domain Services name.
    SECURE_PORT=PortNumberSets the health service port number.
    ENABLE_ERROR_REPORTING={0|1}Optional parameter. Use this parameter with “1” to opt in to error report forwarding to Microsoft. If you do not include this parameter, the agent installation defaults to “0”, which opts out of error report forwarding.
    QUEUE_ERROR_REPORTS={0|1}Optional parameter. Use this parameter with “1” to queue error reports or with “0” to send reports immediately. If you do not include this parameter, the agent installation defaults to “0”.
    INSTALLDIR=pathOptional parameter. Use this parameter if you want to install the agent to a folder other than the default installation path. Note that \Agent will be appended to this value.
    ACTIONS_USE_COMPUTER_ACCOUNT={0|1}Indicates whether to use a specified user account (0) or the Local System account (1).
    ACTIONSUSER=UserNameSets the Agent Action account to UserName. This parameter is required if you specified ACTIONS_USE_COMPUTER_ACCOUNT=0.
    ACTIONSDOMAIN= DomainNameSets the domain for the Agent Action account identified with the ACTIONSUSER parameter.
    ACTIONSPASSWORD= PasswordThe password for the user identified with the ACTIONSUSER parameter.
    NOAPM=1Optional parameter. Installs the Operations Manager agent without .NET Application Performance Monitoring. If you are using AVIcode 5.7, NOAPM=1 leaves the AVIcode agent in place. If you are using AVIcode 5.7 and install the Operations Manager agent by using momagent.msi without NOAPM=1, the AVIcode agent will not work correctly and an alert will be generated.
    AcceptEndUserLicenseAgreement=1Used to specify that you accept the End User License Agreement (EULA).

Operations Manager Agent Installation Methods
Install Agent on Windows Using the Discovery Wizard
Install Agent on UNIX and Linux Using the Discovery Wizard
Install Agent Using the MOMAgent.msi Setup Wizard
Install Agent and Certificate on UNIX and Linux Computers Using the Command Line
Managing Certificates for UNIX and Linux Computers
Process Manual Agent Installations
Applying Overrides to Object Discoveries
Configuring Agents
Examples of Using MOMAgent Command to Manage Agents
Upgrading and Uninstalling Agents on UNIX and Linux Computers
Manually Uninstalling Agents from UNIX and Linux Computers
Uninstall Agent from Windows-based Computers

© 2016 Microsoft