From more often than not, it gets tedious to install consoles on many administrators computers. SCOM 2016 seems to have changed a little bit. This is how I will now install the console.


First off, the same three pre-requisites still exist:

  1. .NET Framework 4.0
  2. SQL System CLR Types
  3. Report Viewer Redistributable


From a scripting or System Center Configuration Manager perspective, execute the following:

  • msiexec.exe /i SQLSysClrTypes.msi /qn
  • msiexec.exe /i ReportViewer.msi /qn
  • msiexec /i OMConsole.msi” /qn
  • msiexec /update KB4024941-AMD64-ENU-Console.msp /qn REBOOT=ReallySuppress


On-Going Bug

If you install the SCOM console and Service Manger console on the same machine with and try to use the SCOM console on any other version than RTM, you’ll encounter an error when you open the console – An object of class ManagementPackFolder with ID <MP GUID>

I’ve looked for the latest official fix for this, and the latest text on this as of this post is from September 12, 2017. Check out the link –


Automating the Bug Fix

Now this blog post is dedicated to a silent install. Who wants to edit each system and configuration file on each machine manually? I sure don’t! This code will automate that!

# Step 1 – Set the System Environment Variable

$InstallPath = “C:\Program Files\System Center Operations Manager 2016\Console”

[Environment]::SetEnvironmentVariable(“DEVPATH”, “$InstallPath\SDK Binaries”, “Machine”)

# Step 2 – Edit the Configuration File

$ConfigFile = “$InstallPath\Microsoft.EnterpriseManagement.Monitoring.Console.exe.config”

$xml = (Get-Content $ConfigFile)

$developmentMode = $xml.CreateElement(“developmentMode”)

$developerInstallation = $xml.CreateAttribute(“developerInstallation”)

$developerInstallation.Value = “true”




# Step 3 – Test and Deploy

I just added this step to say, after running the install and the fix, things should work without any log offs or reboots.