To deploy the OpsMgr 2012 console, there are three items that need to be deployed. The first is .NET 4.0, the second is Report Viewer, and the third is the OpsMgr 2012 console itself. Configure both the .NET 4.0 and Report Viewer to be dependencies for the Operations Manager console.
.NET example installation syntax: (dotNetFx40_Full_x86_x64.exe /q /norestart /ChainingPackage ADMINDEPLOYMENT)
Report Viewer example syntax: (msiexec /I “reportviewer_redist2010core.msi” /q)
OpsMgr console example syntax: (msiexec /I “OMCONSOLE.MSI” /q)
OpsMgr console dependencies:
Based upon our testing, using the OMconsole.msi worked without an issue as long as the the appropriate pre-requisites was installed prior to installation of the OpsMgr 2012 console. However, per Microsoft’s documentation at:
Installation of the OpsMgr console without using the OMconsole.msi:
From http://technet.microsoft.com/en-us/library/hh298607.aspx the syntax to install the OpsMgr 2012 console is:
setup.exe /silent /install /components:OMConsole /EnableErrorReporting:[Never|Queued|Always] /SendCEIPReports:[0|1] /UseMicrosoftUpdate: [0|1]
Syntax example: setup.exe /silent /install /components:OMConsole /EnableErrorReporting:Never /SendCEIPReports:0 /UseMicrosoftUpdate:0
Additional reading on this topic:
Don’t install using the OMconsole: http://blogs.catapultsystems.com/jcowan/archive/2012/06/12/scom-2012-operations-manager-console-will-not-initialize.aspx
TechNet article on installing the OpsMgr console: http://technet.microsoft.com/en-us/library/hh298607.aspx
Thank you to Ambers Ferrara, Eric Morrison and Jonathan Cowan for their help putting this together and pointing out the pitfalls to avoid!