GUIDE, News, SCOM, System Center, Update

SCOM 2019 – One-click Update Rollup installer

Back at Ignite 2019 the System Center product team announced that a one-click Update Rollup installer for SCOM will be released in the near future, the time has come and it’s finally here!


Previously it was required to manually perform multiple installation steps for each Update Rollup installations, and the updates had to be installed in a specific order for each SCOM component installed.

As of today (2020-02-04) we have finally received a “one-click installer” for Update Rollups in SCOM, this will definitely ease up and save time for us SCOM administrators out there.

First impressions

The one-click installer is a single executable file, well that’s just it 🙂


Step-by-step Installation

Let’s go through how the one-click installer looks like for real.

1. Download the one-click installer installation file to your SCOM management server from here:

2. Right-click the KB4533415-AMD64-Server.exe and select Run as administrator to run the installer.


3. Check the box for “I have tread, understood, and agree with the license terms” and then click on Install.


Once the installation has started, the installer will show what it’s currently doing:


4. Once the installation is complete, click Close to finish.


Note: If you encountered any errors, click on Setup Log for more information why the installation failed.


How do I know if the patch has been successfully applied?

1. Navigate to Administration > Operations Manager Products in the Operations Console, select Management Servers and check the following fields:

  • Update Installed
  • KB Number
  • Version


The installation failed on the “Management Packs” step

If the installation failed on Management Packs step, click on the here link in the middle of the installation wizard to view which management packs failed to import.


This will open up a log file called ManualMPImport_{version}.log showing the names of the management pack(s) that failed to import during the installation.


The location of this log file can be found over here:

  • <SCOM install directory>\Server\ Management Packs for Update Rollups


To find the root cause why the installer failed to import the specific management pack, we will need to check a log file called OpsMgrPatchWizard.log, it is located over here:

  • %LocalAppData%\SCOM\Logs

Once we open the log, scroll down to the very end of the OpsMgrPatchWizard.log and we should see error:

oneclick_7(Right-click on the image and open it in a new tab to get a better view)

The error is as follows:

Management pack import failed. Argument Exception : System.ArgumentException: The requested management pack is not valid. See inner exception for details.
Parameter name: managementPack —> Microsoft.EnterpriseManagement.Common.ManagementPackException: Cannot import sealed management pack . The database already contains an unsealed management pack with the same name: .

The error is very clear, it appears that we have a management pack with the name of that is unsealed, and the installer is trying to import a sealed management pack, thus failing.

How do we fix this?

Since the happens to be a core management pack that comes with SCOM 2019, export the unsealed version of the management pack (just to be safe), and import the management pack management from the SCOM 2019 installation media.

Frequently Asked Questions (FAQ)

Will the one click patching experience patch the entire SCOM deployment including the agents?
No, it’ll only update the:

  • Management server
  • Databases
  • Management packs

All other components need to be patched in the existing manner.

What will happen in case of a failure at any step?
The patch will stop at the first point of failure. You will be shown the links to view the respective logs so that you may fix the issues and execute the patch again.

Where can I see the logs if I am using the msp file and not the User Interface for patching?
In case you’re not using the UI for patching then you may visit the following locations to view the logs:

Setup Log

  • %LocalAppData%\SCOM\Logs\OpsMgrPatchWizard.log

SQL Logs

  • <SCOM install directory>\Server\ SQL Script for Update Rollups \SqlExceptions_{version}.log

MP Import Logs

  • <SCOM install directory>\Server\ Management Packs for Update Rollups\ManualMPImport_{version}.log

In circumstances where you’re unable to find SQL and/or MP Import logs at the above locations, then refer the Setup log to root cause the issue.

Will the databases be updated every time the patch is run on each management server?
No, the databases will only be updated once when the patch is run on the first management server.

Will all the management packs be imported as a part of the ‘integrated’ experience?
Only the management packs existing in your environment will be updated if an update is available for them.

Will I be able to uninstall the management server patch?
An Uninstall of the management server patch will only rollback the server binaries, the database changes and imported management packs will not be rolled back.

 3,730 total views,  2 views today

5 thoughts on “SCOM 2019 – One-click Update Rollup installer”

  1. I have a question for post-upgrade 🙂 If we upgrade the agent from the Pending management screen, the APM module will be installed. How can we get to UR1 level without installing APM module?

    1. Hello!

      This is a known thing actually and it is actually by design, you could manually upgrade the agent with the NOAPM switch:

      To repair an existing SCOM agent, but remove the APM components:
      msiexec.exe /fvomus "\\server\share\agents\scom2016\x64\MOMagent.msi" NOAPM=1

      To upgrade an agent, such as upgrading the agent:
      msiexec.exe /i "\\server\share\agents\scom2016\x64\MOMagent.msi" NOAPM=1 AcceptEndUserLicenseAgreement=1

      Best regards,

      1. Thank you for your answer.
        You are right, I use this feature in manual installations.
        But I couldn’t find the momagent.msi file for UR1.
        There is an installation file named KB4533415-AMD64-Agent.msp but I could not use it for upgrading. I couldn’t find the UR1 agent upgrade setup file.

  2. Hi,

    Use the MOMAgent.msi which is located under %SystemDrive%\Program Files\Microsoft System Center\Operations Manager\Server\AgentManagement\amd64\

    Best regards,

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.