The opinions expressed in this blog are strictly personal and reflect the author's point of view, based on his own experience and knowledge. In the same way, attachments must be considered as Proof of Concepts. Therefore, the author declines any responsibility for problems arising from their use and recommends caution and testing before using them in the production environment. The content of this blog also does not represent (necessarily) Microsoft's views, does not provide any warranty, nor does it confer any rights.

Installing prerequisites for System Center Operations Manager 2016 Web Console

20170919 – Thanks to my colleague' suggestion, the post and the attached script were changed to remove IIS components which are not necessary to the Web Console installation. Thanks Tyson.

Hi all,

Maybe this has been already blogged, but in the attempt to make IT guys' life easier I want to share a small Power Shell script which I Used to install the necessary Web Console prerequisites for System Center Operations Manager 2016 on Windows Server 2016.

Instead of going back and forth with the System Center Operations Manager prerequisite checker and install the required components one by one, you can use the script in attach which is also screenshotted below:

You can simply launch it from an elevated Windows Power Shell prompt.

The script will ask for an optional parameter, the Source, that will allow the user to specify the path to feature files if the files are not available in the local feature store of the target computer.

This parameter can be left blank or null, hence should you not need to enter any source path, just hit Enter and the script will move forward.

If you want to test it before running in Prod, you can add the -Whatif switch at the end of the Add-WindowsFeature command line and you will get something similar to the screenshot below wit some nice info at the end:

The script will automatically restart the server ONLY if needed (thanks to the restart switch).

My 0.02 🙂

Comments (3)

  1. Kris Turner says:

    Thanks for the PowerShell Script.

  2. Nick says:

    need ASP.NET role service

    1. Hi Nick,
      thank for you comment. I double checked and can confirm that the necessary ASP.NET role(s) like ASP.NET 3.5 and ASP.NET 4.6 are automatically when running the script.
      You can see if from the image I included in the post. I couldn’t find any ASP.NET role in Windows Server 2016


Skip to main content