Command Shell Examples
Useful SQL Queries
How to install Operations Manager 2012 single server configuration from the command prompt - Jonathan Almquist on Operations Manager - Site Home - TechNet Blogs

How to install Operations Manager 2012 single server configuration from the command prompt

How to install Operations Manager 2012 single server configuration from the command prompt

  • Comments 2
  • Likes

I was reading the Operations Manager 2012 RC documentation today and thought this was interesting enough to put up here.  For those of you that might need to save some time building out a lab or two, this can be handy.

 

1. Log on to the server by using an account that has local administrative credentials.

 

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

Note: Setup.exe requires administrator privileges because the Setup process requires access to system processes that can only be used by a local administrator.

 

3. Change the path to where the Operations Manager setup.exe file is located, and run the following command.

Important: Use the /WebConsoleUseSSL parameter only if your website has Secure Sockets Layer (SSL) activated.

For a default web installation, specify Default Web Site for the /WebSiteName parameter.

 

Important: The following command assumes that you specified the Local System for the Management server action account (/UseLocalSystemActionAccount) and Data Access service (/UseLocalSystemDASAccount). To specify a domain\user name for these accounts, you must provide the following parameters instead.

/ActionAccountUser: <domain\username> /ActionAccountPassword: <password>

/DASAccountUser: <domain\username> /DASAccountPassword: <password>

 

 

Here it is

setup.exe /silent /install

/components:OMServer,OMConsole,OMWebConsole,OMReporting

/ManagementGroupName: "<ManagementGroupName>"

/SqlServerInstance: <server\instance>

/DatabaseName: <OperationalDatabaseName>

/DWSqlServerInstance: <server\instance>

/DWDatabaseName: <DWDatabaseName>

/UseLocalSystemActionAccount /UseLocalSystemDASAccount

/DatareaderUser: <domain\username>

/DatareaderPassword: <password>

/DataWriterUser: <domain\username>

/DataWriterPassword: <password>

/AcceptEndUserLicenseAgreement

/WebSiteName: "<WebSiteName>" [/WebConsoleUseSSL]

/WebConsoleAuthorizationMode: [Mixed|Network]

/SRSInstance: <server\instance>

/SendODRReports: [0|1]

/EnableErrorReporting: [Never|Queued|Always]

/SendCEIPReports: [0|1]

/UseMicrosoftUpdate: [0|1]

I do not moderate this blog anymore. If you have a question regarding this post, send me a message.

Comments
  • Jonathan: Please add the parameter "InstallPath:" and ev other possible setup parameters. I miss the parameter for SQLport. Perhaps there is none? Still searching the net.......

  • Hi again

    When looking into the installation log at c:\users\username\appdata\local\SCOM\Logs\OpsMgrSetupWizard.log (appdata is a hidden catalog)

    you can se how the installation proceeds and all that goes wrong.

    We did use the following command for our installation: (ports, accounts and passwords are reset)

    setup.exe /silent /install /components:OMServer,OMConsole /InstallPath: "E:\APP\MOMX\" /ManagementGroupName: "SHBMomXSED02" /SqlServerInstance: semomxf005.shbdev.shb.biz\MSSQLSERVER /SqlInstancePort: portnr /DatabaseName: OperationManager /DatabaseSize: 4000 /DatabaseLogPath: "F:\DLog" /DatabasePath: "E:\DBas" /DbMode: new /DatabaseScenario: NewDatabase /ServerScenario: FirstServer /DWSqlServerInstance: semomxf005\MSSQLSERVER /DWSqlInstancePort: portnr /DWDatabaseName: OperationManagerDW /DWDatabaseSize: 4000 /DWDatabaseLogPath: "F:\DLog" /DWDatabasePath: "E:\DBas" /DataWarehouseScenario: NewDatabase /ActionAccountUser: useraccount /ActionAccountPassword: password /DASAccountUser: useraccount /DASAccountPassword: password /DatareaderUser: useraccount /DatareaderPassword: password /DataWriterUser: useraccount /DataWriterPassword: password /AcceptEndUserLicenseAgreement /SendODRReports: 0 /EnableErrorReporting: Never /SendCEIPReports: 0 /UseMicrosoftUpdate: 0

    In the logfile you can get other parameters the MS uses. We use a different portnr why we needed that parameter. And of course we need to set DB-size. This ex is only for a test environment.

    Regards

    Thomas