UR5 for SCOM 2012 R2 – Step by Step



KB Article for OpsMgr:  http://support.microsoft.com/kb/3023138

KB Article for all System Center components:  http://support2.microsoft.com/kb/3021802

Download catalog site:  http://catalog.update.microsoft.com/v7/site/Search.aspx?q=3023138


Key fixes:


    • Monitoringhost process crashes because of bind failures against Active Directory
      A fix was made to prevent Monitoringhost.exe from crashing when it cannot connect to Active Directory Domain Services (AD DS). The stack trace from the crash displays a "System.DirectoryServices.ActiveDirectory.ActiveDirectoryServerDownException" error.
    • RunAs accounts cannot be edited because of "Specified cast is invalid" exception
      RunAs accounts can be distributed only to a selected computer through the distribution tab of Run As Account properties. When a computer that is in the distribution list is decommissioned from Operations Manager and the Run As account is opened, you receive the following exception, and no computers are shown on the list:

      System.InvalidCastException: Specified cast is not valid. at Microsoft.EnterpriseManagement.Monitoring.Internal.MonitoringObjectGenerated.get_Id()

    • Application crashes when a search is finished without filter criteria on Distributed application designer
      A fix was made to make sure that the console does not crash when a search is finished without filter criteria on Distributed application designer.
    • MonitoringHost crashes with the exception - System.OverflowException: Value was either too large or too small for an Int32
      Changes to entities are tracked by using the EntityChangeLogId in the EntityChangelog table and the EntityChangeLogId is mastered in the table as an Int64 value. ManagedType tables that begin with a MT_* refer to the EntityChangeLogID. The code that was used to insert into the ManagedType table had an Int32 data type instead of an Int64 data type. When the EntityChangeLogID reached greater than the Int32 limit, the exception crashed the MonitoringHost. This is fixed and the MonitoringHost no longer crashes.
    • Support to troubleshoot PowerShell scripts
      When traces are collected to troubleshoot PowerShell scripts, the logs do not display the parameters that are passed to PowerShell scripts. A code change was made to log this information to make troubleshooting easy.
    • Operational Insights through Operations Manager
      System Center Advisor is improved with many exciting features and is rebranded as "Operational Insights." Learn more about the new Operational Insights feature. The product name is updated in the Operations Manager plug-in for System Center Advisor.
    • "Reset the Baseline," "Pause the baseline," and "Resume the baseline" tasks fail when they are run against an Optimized performance collection rule
      You receive the following exception when this problem occurs:

      Microsoft.EnterpriseManagement.ContainerException: The container could not find a component with name 'TaskRuntime' compatible with type 'Microsoft.EnterpriseManagement.ServiceDataLayer.ITaskRuntimeServiceInternal, Microsoft.EnterpriseManagement.DataAccessService.Core

    • An exception occurs when you edit subscriptions that contain deleted monitors or objects
      A subscription is created by using the "created by specific rules or monitors" criterion. When such a subscription is edited and the monitors or rules associated with them are deleted, you receive the following exception:

      System.NullReferenceException: Object reference not set to an instance of an object.
      at Microsoft.EnterpriseManagement.Mom.Internal.UI.Controls.SourceChooserCriteriaItem.GetSources()
      at Microsoft.EnterpriseManagement.Mom.Internal.UI.Controls.SourceChooserCriteriaItem.Search(CancelFlagWrapper cancelFlag)

      This is fixed not to throw an exception and display the other valid rules or monitors.

    • You can't set Widget column width
      When an explicit column width is set for a widget, the width is not honored in the grid that is displayed. This was caused because of an incorrect Regex validation expression. This has now been fixed and the explicit column width should start reflecting in the UI.
    • Event 4506: Data was dropped because of too much outstanding data
      When too much data is pushed into a module, Operations Manager logs 4506 messages and then drops data. The hardcoded limit is 5120 items globally (in the agent). This global limit is parameterized and exposed through the registry. You can set the value by creating one of the two following registry keys:

      Registry location:

      HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\System Center\Health Service

      DWORD Name: MaximumGlobalPendingDataCount
      DWORD Value:nnnn
      (Where nnnn is the number of items globally. Set this value to more than 5120, as needed.)
      Registry location:


      DWORD Name: MaximumGlobalPendingDataCount
      DWORD Value:nnnn
      (Where nnnn is the number of items globally. Set this value to more than 5120, as needed.)

    • Support for handling Datawarehouse time-outs
      Operations Manager datawarehouse throws events such as 31551, 31552, 31553 when there are problems inserting data to the datawarehouse. One reason these events can occur are because of SQL time-out exceptions. When such events related to SQL time-out exceptions are logged, the logs now also contain information about how to extend these timeouts. You can read more about these exceptions here
    • Can't continue scan with NOLOCK because of data movement
      When a component such as Orchestrator tries to call the Operations Manager database function fn_AlertViewChanges, it could throw the "Could not continue scan with NOLOCK because of data movement" exception. This is triggered by a redundant NOLOCK statement in the SQL SP. This is fixed, as are any failures that are caused by this exception.
    • $ScriptContext.Context does not persist the value in PowerShell widgets
      PowerShell widgets that use $ScriptContext.Context display a blank. With this fix, the context now persists.
    • Evaluation version alert
      Operations Manager previously displayed a Warning 60 days, 30 days, 1 day, and last-day hourly before the expiration of the evaluation period. This has been changed to an error so that you know Operations Manager will stop working as soon as the evaluation period is over. It also contains a link to a KB article that helps you convert the evaluation version to a registered version.
Xplat updates:
    • Updating the UNIX/Linux agent for Operations Manager resets deep monitoring status for JEE application servers.
      This issue applies to Java Application Server instances that have “Deep Monitoring” enabled. When you upgrade the UNIX/Linux agent for Operations Manager, the instances are no longer “Deep Monitored,” and they require another execution of the Enable Deep Monitoring management pack task.
    • By default, the rpcimap monitor for Red Hat Enterprise Linux 5 is now disabled.
      Red Hat Enterprise Linux 5.10 and later versions removes the default rpcimap daemon that's present in earlier Red Hat Enterprise Linux 5 releases. Critical alerts are generated for the rpcimap service that's not running on Red Hat Enterprise Linux 5.10. By default, the rpcimap monitor for Red Hat Enterprise Linux 5 is now disabled. However, it can be re-enabled by an override in the management pack.
    • Monitoring in time zone UTC +13 (for example, Auckland, New Zealand with daylight saving time) causes the “Unix Process Monitoring template” to fail.
      This issue applies to all UNIX/Linux servers that are located in the UTC +13 time zone. When you try to use the Unix Process Monitoring template for a server that's located in UTC +13 time zone, the following warning may be logged in the agent’s log (/var/opt/microsoft/scx/log/scx.log):

      Warning [scx.core.providers.provess_provider:266:2250:140361722332992] SCX_UnixProcess_Class_Provider: EnumerateInstances - Formal argument 'offsetFromUTC' is invalid: SCXRelativeTime: years=0 months=0 days=0 hours=0 minutes=780 microseconds=0 - [/home/serviceb/ScxCore_R2URNext_Debian50_x64/pal/source/code/scxcorelib/pal/scxtime/absolute.cpp:856]

    • When you use the "scxadmin -log-rotate" utility, this stops logging to the agent’s log (/var/opt/microsoft/scx/log/scx.log) after log rotation is completed.
      When you use the scxadmin program together with the -log-rotate option, logging in /var/opt/microsoft/scx/log/scx.log may not resume unless a restart is issued (scxadmin -restart).


Lets get started.

From reading the KB article – the order of operations is:

  1. Install the update rollup package on the following server infrastructure:
    • Management servers
    • Gateway servers
    • Web console server role computers
    • Operations console role computers
  2. Apply SQL scripts.
  3. Manually import the management packs.
  4. Update Agents

Now, we need to add another step – if we are using Xplat monitoring – need to update the Linux/Unix MP’s and agents.

       5.  Update Unix/Linux MP’s and Agents.



1.  Management Servers


Since there is no RMS anymore, it doesn’t matter which management server I start with.  There is no need to begin with whomever holds the RMSe role.  I simply make sure I only patch one management server at a time to allow for agent failover without overloading any single management server.

I can apply this update manually via the MSP files, or I can use Windows Update.  I have 3 management servers, so I will demonstrate both.  I will do the first management server manually.  This management server holds 3 roles, and each must be patched:  Management Server, Web Console, and Console.

The first thing I do when I download the updates from the catalog, is copy the cab files for my language to a single location:


Then extract the contents:


Once I have the MSP files, I am ready to start applying the update to each server by role.

***Note:  You MUST log on to each server role as a Local Administrator, SCOM Admin, AND your account must also have System Administrator (SA) role to the database instances that host your OpsMgr databases.

My first server is a management server, and the web console, and has the OpsMgr console installed, so I copy those update files locally, and execute them per the KB, from an elevated command prompt:


This launches a quick UI which applies the update.  It will bounce the SCOM services as well.  The update does not provide any feedback that it had success or failure.  You can check the application log for the MsiInstaller events for that:

Log Name:      Application
Source:        MsiInstaller
Date:          2/22/2015 1:40:06 PM
Event ID:      1036
Task Category: None
Level:         Information
Keywords:      Classic
User:          OPSMGR\foo
Computer:      SCOM01.opsmgr.net
Windows Installer installed an update. Product Name: System Center Operations Manager 2012 Server. Product Version: 7.1.10226.0. Product Language: 1033. Manufacturer: Microsoft Corporation. Update Name: System Center 2012 R2 Operations Manager UR5 Update Patch. Installation success or error status: 0.


You can also spot check a couple DLL files for the file version attribute. 


Next up – run the Web Console update:


This runs much faster.   A quick file spot check:


Lastly – install the console update (make sure your console is closed):


A quick file spot check:




Secondary Management Servers:


I now move on to my secondary management servers, applying the server update, then the console update. 

On this next management server, I will use the example of Windows Update as opposed to manually installing the MSP files.  I check online, and make sure that I have configured Windows Update to give me updates for additional products:


This shows me two applicable updates for this server:


I apply these updates (along with some additional Windows Server Updates I was missing, and reboot each management server, until all management servers are updated.


Updating Gateways:


I can use Windows Update or manual installation.


The update launches a UI and quickly finishes.

Then I will spot check the DLL’s:


I can also spot-check the \AgentManagement folder, and make sure my agent update files are dropped here correctly:




2. Apply the SQL Scripts

In the path on your management servers, where you installed/extracted the update, there are two SQL script files: 

%SystemDrive%\Program Files\Microsoft System Center 2012 R2\Operations Manager\Server\SQL Script for Update Rollups

(note – your path may vary slightly depending on if you have an upgraded environment of clean install)


First – let’s run the script to update the OperationsManager database.  Open a SQL management studio query window, connect it to your Operations Manager database, and then open the script file.  Make sure it is pointing to your OperationsManager database, then execute the script.





Click the “Execute” button in SQL mgmt. studio.  The execution could take a considerable amount of time and you might see a spike in processor utilization on your SQL database server during this operation.

You will see the following (or similar) output:





IF YOU GET AN ERROR – STOP!  Do not continue.  Try re-running the script several times until it completes without errors.  In a large environment, you might have to run this several times, or even potentially shut down the services on your management servers, to break their connection to the databases, to get a successful run.

Technical tidbit:  This script has been updated in UR5.  Even if you previously ran this script in UR1, UR2, UR3, or UR4, you must run this again.



Next, we have a script in UR5 to run against the warehouse DB.  Do not skip this step under any circumstances.    From:

%SystemDrive%\Program Files\Microsoft System Center 2012 R2\Operations Manager\Server\SQL Script for Update Rollups

(note – your path may vary slightly depending on if you have an upgraded environment of clean install)

Open a SQL management studio query window, connect it to your OperationsManagerDW database, and then open the script file UR_Datawarehouse.sql.  Make sure it is pointing to your OperationsManagerDW database, then execute the script.

If you see a warning about line endings, choose Yes to continue.


Click the “Execute” button in SQL mgmt. studio.  The execution could take a considerable amount of time and you might see a spike in processor utilization on your SQL database server during this operation.

You will see the following (or similar) output:




3. Manually import the management packs?


There are 25 management packs in this update!

The path for these is on your management server, after you have installed the “Server” update:

\Program Files\Microsoft System Center 2012 R2\Operations Manager\Server\Management Packs for Update Rollups

However, the majority of them are Advisor, and language specific.  Only import the ones you need, and that are correct for your language.  I will remove all the Advisor MP’s for other languages, and I am left with the following:


The TFS MP bundles are only used for specific scenarios, such as DevOps scenarios where you have integrated APM with TFS, etc.  If you are not currently using these MP’s, there is no need to import or update them.  I’d skip this MP import unless you already have these MP’s present in your environment.

The Advisor MP’s are only needed if you are using System Center Operational Insights (Previously known as Advisor) services.

However, the Image and Visualization libraries deal with Dashboard updates, and these always need to be updated.

I import all of these without issue.




4.  Update Agents


Agents should be placed into pending actions by this update (mine worked great) for any agent that was not manually installed (remotely manageable = yes):


If your agents are not placed into pending management – this is generally caused by not running the update from an elevated command prompt, or having manually installed agents which will not be placed into pending.

In this case – my agents that were reporting to a management server that was updated using Windows Update – did NOT place agents into pending.  Only the agents reporting to the management server for which I manually executed the patch worked.

You can approve these – which will result in a success message once complete:



Soon you should start to see PatchList getting filled in from the Agents By Version view under Operations Manager monitoring folder in the console:




5.  Update Unix/Linux MPs and Agents


Next up – I download and extract the updated Linux MP’s for SCOM 2012


7.5.1042.0 is current at this time for SCOM 2012 R2 UR5. 

****Note – take GREAT care when downloading – that you select the correct download for R2.  You must scroll down in the list and select the MSI for 2012 R2:


Download the MSI and run it.  It will extract the MP’s to C:\Program Files (x86)\System Center Management Packs\System Center 2012 R2 Management Packs for Unix and Linux\

Update any MP’s you are already using.   These are mine for RHEL, SUSE, and the Universal Linux libraries.  Looks like we have added RHEL7 and SUSE12 since I last updated:


You will likely observe VERY high CPU utilization of your management servers and database server during and immediately following these MP imports.  Give it plenty of time to complete the process of the import and MPB deployments.

Next up – you would upgrade your agents on the Unix/Linux monitored agents.  You can now do this straight from the console:



You can input credentials or use existing RunAs accounts if those have enough rights to perform this action.

Mine FAILED, with an SSH exception about copying the new agent.  It turns out my files were not updated on the management server – see pic:


I had to restart the Healthservice on the management server, and within a few minutes all the new files were there.





6.  Update the remaining deployed consoles


This is an important step.  I have consoles deployed around my infrastructure – on my Orchestrator server, SCVMM server, on my personal workstation, on all the other SCOM admins on my team, on a Terminal Server we use as a tools machine, etc.  These should all get the UR5 update.





Now at this point, we would check the OpsMgr event logs on our management servers, check for any new or strange alerts coming in, and ensure that there are no issues after the update.




Known issues:

See the existing list of known issues documented in the KB article.

1.  Many people are reporting that the SQL script is failing to complete when executed.  You should attempt to run this multiple times until it completes without error.  You might need to stop the Exchange correlation engine, stop all the SCOM services on the management servers, and/or bounce the SQL server services in order to get a successful completion in a busy management group.  The errors reported appear as below:

(1 row(s) affected)
(1 row(s) affected)
Msg 1205, Level 13, State 56, Line 1
Transaction (Process ID 152) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.
Msg 3727, Level 16, State 0, Line 1
Could not drop constraint. See previous errors.

Comments (49)
  1. Kevin Holman says:

    @Bix – for any agents that you want to update remotely like that, you simply run a "repair" action on them from the console.

  2. Anonymous says:

    Found my issue, the Agent is part of the client. Some of my servers I had to install the client manually, I just update it one manually to the latest version.

  3. Kevin Holman says:

    The agent update not working in the console was only with a specific UR. I believe that was addressed. I applied the update via pending for mine and it worked just fine. What MSI/MSP patch files are present in your AgentManagementAMD64 folder?

  4. Kevin Holman says:

    Just to be clear – this UR5 does not cause or increase the chances of a 31551/31552, or SQL timeout – all we did was make some of the alerts and events clearer as to root cause for troubleshooting.

  5. Anonymous says:

    Great job! Easy to follow up. I have successfully update it to UR5. The only module I couldn’t install was the Agent, got an error "the upgrade patch cannot be installed by the Windows Installer…upgrade patch may be update a different version" which
    I do believe has to do with some old clients still in my infrastructure.

  6. Anonymous says:

    Hi Kevin, UR 5 installed OK using the UR4 procedure some time ago. I too am curious about the correct way to update the web.config file as described on March 3 by Mike Flanagan. This came to my attention after I was unsuccessful in editing session timeout
    values for a monitoring account using a desktop client to access the Web Console.. That "fix", specifically deals with the web.config XML file located in %Program Files%System Center Operations Manager 2012WebConsoleWebHost . There is a post about modifying
    the values but it’s not from a member of the System Center team. Any suggestions you may have about either the correct placement of the new line RE: KB 911722 and/or the default timeout settings for Web Console are appreciated!!

  7. Kevin Holman says:

    No issues patching server 2008 R2 here. Patched by push and manually.

  8. Anonymous says:

    At one point the agent update didn’t work via console. Update was successful but it didn’t actually patch the agent. As far as I remember this was also documented as a known issue on one of the UR’s. I’m running UR4 at the moment and it’s not still working
    for me though the agents appear on pending management.

  9. Anonymous says:

    I have KB2992020-amd64-Agent.msp (UR4) on AgentManagementAMD64 (there is also KB2965445-amd64-Agent.msp (UR3)).

    I have a big environment with thousands of agents behind several (hundreds) gateways so patching all the agents each UR has been a bit challenging especially when the console update hasn’t always worked for me as supposed to.

    I’m doing UR5 tomorrow and after I’ve updated all my gateways I will have another look at the agent update via console.

  10. Kevin Holman says:

    @SCOM Artist –

    For SCCM collections, UR5 is part of Windows Update, and registers in the applied updates, so you would treat this just like any other update to see if it is applied or not.

  11. Kevin Holman says:

    @Ivo –

    Yes. Although our tested order is to update infrastructure first, I have never seen any serious issue with agents having a higher UR version than the infrastructure.

  12. Kevin Holman says:

    Yes, unfortunately you will need to stop the services on your management servers – they are locking the DB tables and preventing the update script.

  13. Kevin Holman says:

    @Enrique – that means you are missing some management packs which were part of the UR MP import.

    If you did import these MP’s but still not seeing it – restart the management server services.

  14. Kevin Holman says:

    @Chris –
    We don’t really break it down by role or update….. In order to apply software, of course you need local admin rights…. unless you are using WSUS/SCCM to apply the software. However, some of our CU’s write data directly to the databases, and this is what
    has required SQL SA. Therefore, we just make a blanket statement that these are the rights required. It might be totally possible to patch the web console and never need SQL admin rights…. we just aren’t going to test at that level. The expectation is that
    the person doing updates has SCOM admin, local admin, and SQL admin rights.

  15. Kevin Holman says:

    Yes – my post above covers two way to validate that.

  16. Anonymous says:

    This is updated as of 2-22-2015 In general – you should evaluate all hotfixes available, and only apply

  17. Artur says:

    Thank you Kevin! You´re awesome 🙂
    I have actually no installed UR, do i need fist UR1,2,3,4 before i can install UR5 or can i just install the UR5 ?

  18. Hi Artur

    You can go straight to UR5. You do not need to install 1,2,3 or 4.



  19. Souvick Roy says:

    Thanks Kevin for for your great article…….
    after this upgrade customer may face SQL time-out error and see event ID 31551 and 31552 in the Ops Mgr logs.
    Please use below link for troubleshooting


  20. Jonathan says:

    I like this format for the UR postings. Thanks.

  21. Oliver says:

    Anyone has also issues installing the Update (Agent) on Windows Server 2008 R2? I’m not able to install by push (from scom) or even apply manuel the patch.

  22. Andrew Curtis says:

    Clean install of R2 straight to UR 5 with no issues following Kevins guide. As always spot on.

  23. Mike Flanagan says:

    Thanks Kevin for doing such an excellent post on on getting environments updated! this will certainly help me tremendously! One question I have pertains to the adding of the machinekey in the web.config file to enable the console fixes. I see a couple
    of system.web sections within this file. This snippet is from the KB article: To enable the web console fixes, add the following line to the %windir%Microsoft.NETFramework64v2.0.50727CONFIGweb.config file:

    I’m wondering if it would work to use the iis administration piece, and select Machine key within the ASP.NET section?

    Thanks for any suggestions!

  24. Ivo Naiman says:

    Thanks Kevin. Can we update agents via SCCM to UR5 before updating whole environment to this version?

  25. GallEsco says:

    I Installed a new scom 2012 R2 with ur5, and i know i don’t need ur1,2,3,4 I just went straight to the ur5 but when i want to create a new dashboard I’m missing PowerShell Grid widget and others that were available in UR2. is there some extra packages
    that i need to install to get those or how can i get them in my server?

  26. mohammad says:

    Hi Kevin,

    After updating the management pack for 2 customers, the "objects by performance" widget is not displaying any data? do we need to check somthing?


  27. GallEsco says:

    Thanks Kevin,
    I was missing some management packs. they were in the rollup folder in SCOM.

  28. SCOM Artist says:

    Is there a way to determine that the UR5 agent update is installed besides using the "Agent Version" view in the console? I’m working on deploying the UR5 update .msp as an SCCM application, but when I get to the detection method step, I’m unable to find any
    flag to know the agent has had the UR5 update installed.

    I’m trying to automate the SCOM agent rollout and trying to find a way to install the base 2012 R2 agent, then apply the required UR.


  29. Sam John says:

    Step 6:

    Must be a typo – "These should all get the UR3 update."

  30. Tony Ellis says:

    We updated our environment via Windows Update and the agents are not going into Pending Management. Is there a way to force the agent into the pending management state? I’m trying to figure out how I can update my agents through the console without having
    to push out a SCCM package.

  31. Gurdeep says:

    Hi Kevin, I am working on doing an upgrade to UR5. RE the agent updates, do I run that against every monitored server with an agent? Apologies for the basic question! Thanks

  32. Bix says:

    Greetings Kevin and as always, thanks much for your detailed guide.
    I have a question about step #4 and it happens to be the same as Tony Ellis from March 18th.

    I used the Windows Update way in order to apply (successfully) the UR5 to my MS’s – they both report version 7.1.10266.0 in Admin>Device Management>Management Servers.

    And as you mention in step #4, there are no server in Pending Management; they’re all still in Device Management>Agent Managed, reporting version 7.1.10184.0 which is still UR4 (if I’m not mistaken).
    So, if I didn’t apply a manual update, am I forced to update every agent manually through remote logon and executable launch? or is there a workaround to "force" the update push from the OpsMgr Console ?

  33. shahid says:

    Thanks kevin for great post. Is there way to validate if CU5 has been applied on agents

  34. Ashish Sharma says:

    Your blog is full of good thinks and your tips for Learning Path are clear.
    For know about RHCE, RHCSA, RHCA, LINUX Concepts and Exam visit here: –

  35. Magdy Kamel says:

    @Kevin Holman, Thanks a lot for your support.
    I deploy UR4 as you article, everything working well and i make check of files version.
    but when i open scom console and click on help > about i get product version 7.1.10226.0

    Note: when i access folder ServerAgentManagementamd64 i found KB3023138-amd64-Agent.msp (it is Agent of UR5)
    Thanks again for your usual cooperation

  36. Magdy Kamel says:

    @Kevin Holman, Thanks a lot for your support.
    I deploy **UR5** as you article, everything working well and i make check of files version.
    but when i open scom console and click on help > about i get product version 7.1.10226.0
    Note: when i access folder ServerAgentManagementamd64 i found KB3023138-amd64-Agent.msp (it is Agent of UR5)
    Thanks again for your usual cooperation

  37. Jeo says:

    Hi Kevin, we currently have UR4 installed, how critical is UR5 if we opt to not install it? Thank you.

  38. Andreas Zuckerhut says:

    I’m getting the deadlock error for the 50th time now always after a few seconds. That normal?

  39. Andreas Zuckerhut says:

    Yea, didn’t want to stop the Management Server’s Health Services because it’d end up in a ton of heartbeat failures.
    What I did now was disabling the Management Server Action Account on the db, killing processes, then enabling it again.

  40. Arthur says:

    Kevin, I have installed the update agents by SCCM 2012 and some of servers asked for reboot. Have you experienced this behavior before?

  41. Mark W says:

    Re: E3C3ACD0-54E6-493B-9256-A33C6CF5457C – that was me, with a blank user ID – I worked on the web.config file under …WebHost using an online XML validator, and eventually came up with the correct strings to disable the default 30 minute timeout for
    clients using a browser. I will be happy to share if anyone needs them. Still curious about the correct placement of the modifications to the configuration files within the bulleted items under
    https://support.microsoft.com/en-us/kb/2904680 "Installation Notes"; also the reference to the ASP error / KB 911722 after a version upgrade. Thanks!

  42. Chris Durman says:

    Hello Kevin, Thanks heaps for the post. I’m having difficulty understanding the following sentence;

    ***Note: You MUST log on to each server role as a Local Administrator, SCOM Admin, AND your account must also have System Administrator (SA) role to the database instances that host your OpsMgr databases.

    I’m reading it as – For each server role (Management, webconsole, console, SQL), you must be logged in with an account that is a Local Admin, a SCOM Admin, and SQL SA, when running the update.

    Is this correct?

  43. Srini says:

    Hi Kevin,
    How do i validate that my DW has been updated with UR5 as the sql script completed successfully in less than a second (00:00:00). It ran for more than 2 minutes in the DB so I suppose whether the update was successful in DW?


  44. Ted H says:


    What implements the rpm and related (Z, gz and DEB) files for Linux agent into C:Program FilesMicrosoft System Center 2012 R2Operations ManagerServerAgentManagementUnixAgentsDownloadedKits ?

    We used Windows Update but the files in that path start with "scx-1.5.0-128" instead of the UR 5 version of "scx-1.5.1-150". I just tried running the msp file from an elevated prompt, but nothing seemed to change. I also tried to install the "System Center
    2012 R2 Management Packs for UNIX and Linux.msi" directly on the management server, but that had no impact either.

    Is there a way to just put a newer version of the rpm, et. al. files into that directory or does it take some registry or data base changes to get SCOM to recognize the newer Linux agent files are available?

  45. Hi Kevin,

    I really liked of your article. It’s very cool and easy to understand step by step. Congratulations. I am preparing my environment with SCOM 2012 SP1 and then, I must update for Update Rollup 9. I could see that there is no update until now. So, could you advise
    if the agent would to request the restart on the boxes after update?


  46. Kevin Holman says:

    @Rodney – the agent generally does not require a restart. If it did, you can just suppress that and wait for the next available maintenance window.

  47. Marvi Valdez says:

    I have updated our Lab from SCOM 2012 SP1 to R2 and I have no issues during the upgrade. When I was installing the UR6 patch for the console I am encountered the error of the "The upgrade patch cannot be installed by the Windows Installer service because
    the program to be upgraded may be missing. or the upgrade patch may update different version of the program. Verify that the program to be upgraded exists on your computer and that you have the correct patch.

    Console current build version is 7.1.10226.0.
    MS server is already 7.1.10226.1064

    Can you please help? From SCOM 2012 R2 I should be able to upgrade to UR6 directly right?

  48. Fazal Zaidi says:

    does scom should be installed on every server?

Comments are closed.

Skip to main content