SCOM 2016 Scheduled Maintenance Mode won’t run if you picked a different database name during install

There is a bug in SCOM 2016 where if you choose a different Operations Manager Database Name during install, schedule maintenance mode won’t work!

The Jobs will run but nothing is put into Maintenance Mode. You won’t get an error in SCOM or in the event log.

As you can see below I named my “OperationsManager” Database “SCOMDB”

The stored procedure has ‘OperationsManager’ hard coded as the Database name so it fails!

The workaround is to change the stored procedure that creates these Schedules.

The stored procedure name is p_MaintenanceScheduleCreate

Right click Modify.

Find the line


and change OperationsManager to your database name and click Execute

You will have to delete all your Schedules in the console.

Now they run without issue.

This is a known bug and will be fixed in SCOM 2016 UR3.





Continue Reading

Identify SCOM Agent Version from the file system on SCOM 2012 R2 and SCOM 2016 Agents

When writing my SCOM Agent Update MP  I needed a way to get the SCOM Agent version from the file system.  There is one file that gets updated in every Update Rollup.  OMAgentTraceTMFVer.Dll that is located where in the \Tools\TMF directory where you installed the scom agent.  In my case C:\Program Files\Microsoft Monitoring Agent\Agent\Tools\TMF\OMAgentTraceTMFVer.Dll

I wrote this script to read the file version of this file to identify agent installed version.

Here is a similar VBscript that will pull that data. It works with SCOM 2012 R2 and SCOM 2016


Here is the script in Powershell.   Modified from Kevin’s Agent Management Pack.


Continue Reading

Install and Uninstall SCOM 2012 R2 UR11 agent updates from a command line

A customer was building a SCCM package to update SCOM Agents.  They needed the command lines to install and uninstall UR11.

Patch Install command

Patch Uninstall Command

The tricky part was getting the Uninstall GUID. You can get the GUID by using ORCA.

In ORCA load the msp file. Then go to View Summary Information.



They also needed a way to get the version information to know if it was installed or needed to be installed.

Here is a quick vbscript to get that information.


Continue Reading

Stop the madness of having outdated SCOM Agents in your environment

I have seen many SCOM environments where it takes multiple teams to update a single SCOM Agent to the latest Update Rollup.   Often it takes months or even years to update all Agents to the latest Update Rollup.  I created two management packs to make it easy to keep all your agents up to date.  With these Management Packs your Application Admins, Server Admins or SCOM Admins can update their servers when they feel comfortable or have an open change window without requiring admin permissions.

Management Pack 1: Contoso Agent Update Rollup

Download: Link

  • Discovers all Agents and their Update Rollup version
  • Monitors and alerts if agents don’t have the latest Update Rollup
  • Task to install the Update Rollup.  Only permissions required is Operator with permission to run the task. 

Management Pack 2: (Optional) Contoso Agent Update Rollup FileDeploy

  • Deploys out latest Update Rollup to Servers.

Download: Link


Getting Started

Management Pack 1  (Contoso Agent Update Rollup)

1.) Install Contoso Agent Update Rollup Management Pack



2.) Download UR11 from here, extract and copy the msp file to a folder on one of your management servers or on a file server that you can set permissions on.


3.) Share out the file to all Domain Computers, or you can individually add each server you want to give access to the patch.




4.) Open up the SCOM console, a new folder called Contoso Update Rollup will now show up

Expand that folder and click on the State View.

You can see I have two servers in my environment.  One has UR11 installed and one that is still at RTM


5.) To install the update on one or more servers I select the servers and click the Task called “Install Update Rollup”


You can see the default is my file location.  You need this to be the location of the file you shared out.  Click override and enter the location of your update rollup patch file.  Make sure you add double quotes around the location.filelocation




Side Note: If you don’t want to do this every time.  You can modify the xml and re-import the mp.  Just search and replace for the line (Make sure you include double quotes) <Arguments>”\\xOM01\UR11\KB3183990-AMD64-Agent.msp”</Arguments>


6.) Verify everything is correct and click run.



The task will run and output the results.


7.) After about 10 minutes.  Go back and check the state view.  The server should now show the updated UR Version and File Version


Management Pack 2 (Optional) Contoso Agent Update Rollup FileDeploy

For those who are not able to or don’t want to create a share for all domain computers for security reasons.  I have another option.  This management pack will embed the update rollup file in a management pack and deploy it to the servers.  Then you can use the task in management pack 1 to update the agent with a file on the local system.

For legal reasons I have not included the management pack containing the update rollup, but I will include the project so you can quickly build your own.

How to build the Management Pack File

1.) Open the Solution by double clicking on the .sln file.  This will open the file in visual studio.



2.) Select the Resources folder.  Right click Add Existing Item.



3.) Pick the drop down to show all files.  Then browse to to where you have the Agent UR file located.


4.) Click on the file now and for Build Action choose Embedded Resource


5.) Check that the Contoso.Agent.UpdateRollup.FileDeploy.Resource.mpx file has the correct file name.  This may need to be changed if you are using a newer or older update rollup then UR11.


6.) Build the solution under Build, Build Solution



7.) Browse out to the build location.  You should see a file called Contoso.Agent.UpdateRollup.FileDeploy.mpb



8.) Import the MPB Management Pack into SCOM.

After 10 minutes check your agents to see if the file was deployed.


The default location is C:\Windows\Temp  *Note this can be changed directly in the MP’s XML or with an override to the rule called “Contoso Agent UpdateRollup File Deploy”

Now you can run the task in Management Pack 1 with the local file location.


















Continue Reading