Wednesday, October 31, 2012

SCOM 2012 - Installing Agent from Command Line

I have run into environments where it is difficult or impossible to install the monitoring agent directly from the Operations Manager console. Either there are security restrictions or company policy prevents "unauthorized" deployment methods. Whatever the situation, there are ways of setting up command line installation through other third party tools (usually something the client already has) or creating a script to push the agent out. You can even run it locally from a command prompt.

There are a couple things you will need in advance to prep for the install. On the installation media in the AGENT folder there are three sub folders, AMD64, I386 and IA64 where you can find MOMAgent.msi for your respective OS. So depending on your environment you may actually have to create up to three packages/scripts for your domain. If you are using gateway servers that number can multiply by the number of gateway domains.

So once you have your install media you need the execution script below:

You will need to modify the installation directory to suit your requirements. Also you will need to update the switches using the following information
Switch Description
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=MGname Specifies the management group that will manage the computer.
MANAGEMENT_SERVER_DNS=MSname Specifies 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=ADname Use 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=PortNumber Sets 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=path Optional 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=UserName Sets the Agent Action account to UserName. This parameter is required if you specified ACTIONS_USE_COMPUTER_ACCOUNT=0.
ACTIONSDOMAIN= DomainName Sets the domain for the Agent Action account identified with the ACTIONSUSER parameter.
ACTIONSPASSWORD= Password The password for the user identified with the ACTIONSUSER parameter.
NOAPM=1 Optional 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.

You can find additional information on agent delivery methods in the Microsoft Technet Article.

More to come!

If you like this blog, give it a g+1

No comments:

Post a Comment