Thursday, November 29, 2012

SCOM 2012 - Unattended Installation

In SCOM 2012 - Installation I covered the traditional way to install SCOM using the GUI interface, and this method works just fine if you only have a few machines to build. I have found, however, when doing a larger type of engagement it is helpful to be able to setup and launch unattended installations for SCOM. When you are building half a dozen management servers and a dozen gateway servers and a web/reporting server, having unattended script files makes the install go much faster. So I thought I would go through and iterate what all the switches are as well as provide a few install samples for you.

Please be aware that all of the prerequisites still need to be met before running the silent install.

Switches
Below are the switches I have been able to pull together from various sources including the Microsoft Technet article.
Parameter Value
/silent Does not display the installation wizard.
/install Runs an installation. Use /components to indicate specific features to install.
/installpath Determines the location of the installation directory.
/components OMServer: Installs the management server.

OMConsole: Installs the Operations console.

OMWebConsole: Installs the web console.

OMReporting: Installs the Reporting server.

/ManagementGroupName: The name of the management group
/SqlServerInstance: The SQL server and instance (<server\instance>).
/DatabaseName: The name of the Operational database.
/DWSqlServerInstance: The data warehouse server and instance (<server\instance>).
/DWDatabaseName: The name of the data warehouse database.
/UseLocalSystemActionAccount Used to specify the Local System for the Management server action account.
/ActionAccountUser: The domain and user name of the Management server action account.

Used if you do not want to specify the Local System

/ActionAccountPassword: The password for the Management server action account.

Used if you do not want to specify the Local System.

/UseLocalSystemDASAccount Used to specify the Local System for the Data Access service account.
/DASAccountUser: The domain and user name of the Data Access service account.

Used if you do not want to specify the Local System.

/DASAccountPassword: The password for the Data Access service account.

Used if you do not want to specify the Local System.

/DataReaderUser: The domain and user name of the data reader account.
/DataReaderPassword: The password for the data reader account.
/DataWriterUser: The domain and user name of the data writer account.
/DataWriterPassword: The password for the data writer account.
/EnableErrorReporting: Never: Do not opt in to sending automatic error reports.

Queued: Opt in to sending error reports, but queue the reports for review before sending.

Always: Opt in to automatically send error reports.

/SendCEIPReports: 0 : Do not opt in to the Customer Experience Improvement Program (CEIP).

1 : Opt in to CEIP.

/UseMicrosoftUpdate: 0 : Do not opt in to Microsoft Update.

1 : Opt in to Microsoft Update.

/AcceptEndUserLicenseAgreement Used to specify that you accept the End User License Agreement (EULA). This is only required when you install the first management server in the management group.
/ManagementServer Used to specify the name of the management server associated with a web console and/or Reporting server that is not installed on a management server.
/WebSiteName: The name of the website. For default web installation, specify “Default Web Site”.

Used for web console installations.

/WebConsoleUseSSL Specify only if your website has Secure Sockets Layer (SSL) activated.

Used for web console installations.

/WebConsoleAuthorizationMode: Mixed: Used for intranet scenarios.

Network: Used for extranet scenarios.

Used for web console installations.

/SRSInstance The reporting server and instance (<server\instance>).

Used for Reporting Server installations.

/SendODRReports: 0: Do not opt in to sending operational data reports.

1: opt in to sending operational data reports.

Used for Reporting Server Installations.


Samples:
These are a few examples of the unattended install scripts.

To Install Management Servers (PowerShell)
Start-Process -FilePath setup.exe -ArgumentList '/silent /install /components:OMServer,OMConsole /ManagementGroupName:SCOMMgmt /SqlServerInstance:SQLServer\OpsInstance /DatabaseName:OperationsManager /DWSqlServerInstance:SQLServer\DWInstance /DWDatabaseName:OperationsManagerDW /ActionAccountUser:domain\SCOMActionAccount /ActionAccountPassword:password /DASAccountUser:domain\SCOMDataAccessAccount /DASAccountPassword:password /DatareaderUser:domain\SCOMDataReader /DatareaderPassword:password /DataWriterUser:domain\SCOMDataWriter /DataWriterPassword:password /EnableErrorReporting:Always /SendCEIPReports:1 /UseMicrosoftUpdate:1 /AcceptEndUserLicenseAgreement'
To Install IIS (PowerShell)
Import-Module ServerManager Add-WindowsFeature NET-Framework-Core,Web-Static-Content,Web-Default-Doc,Web-Dir-Browsing,Web-Http-Errors,Web-Http-Logging,Web-Request-Monitor,Web-Filtering,Web-Stat-Compression,Web-Mgmt-Console,Web-Metabase,Web-Asp-Net,Web-Windows-Auth,Web-ASP,Web-CGI -Restart
Please review SCOM 2012 - Web & Reporting Services Install for additional IIS configuration

To Install Web/Reporting Services (PowerShell)
Start-Process -FilePath setup.exe -ArgumentList '/silent /install /components:OMWebConsole,OMReporting /ManagementServer:SCOMServer /SRSInstance:Server\OpsInstance /WebSiteName:"Default Web Site" /WebConsoleAuthorizationMode:Mixed /DatareaderUser:domain\SCOMDataReader /DatareaderPassword:password /SendODRReports:1 /UseMicrosoftUpdate:1'
To Install Gateway Services (Command Line)
%WinDir%\System32\msiexec.exe /i path\Directory\MOMGateway.msi /qn /l*v path\Logs\GatewayInstall.log
ADDLOCAL=MOMGateway 
MANAGEMENT_GROUP=""
IS_ROOT_HEALTH_SERVER=0
ROOT_MANAGEMENT_SERVER_AD=
ROOT_MANAGEMENT_SERVER_DNS=
ACTIONS_USE_COMPUTER_ACCOUNT=0
ACTIONSDOMAIN=
ACTIONSUSER=
ACTIONSPASSWORD=
ROOT_MANAGEMENT_SERVER_PORT=5723
[INSTALLDIR=]



More to come!


Contributing Documentation
Technet, Technet, Powershell Daily

2 comments:

  1. Hi Jim,

    you tested all these commands before, and all work successfully?

    Thanks a lot man...

    ReplyDelete
  2. Wilsterman,

    I have not tested all of them but have used quite a few. The examples I provided are the most common ones I use.

    Hope you find them helpful

    ReplyDelete