UR9 for SCOM 2012 R2 – Step by Step


This article has been updated/replaced.  The current article is at:

https://blogs.technet.microsoft.com/kevinholman/2016/05/16/ur9-for-scom-2012-r2-step-by-step-2/

 


Comments (60)

  1. SKusen says:

    Hi Kevin, love the posts related to the UR's, very helpful. I'm looking to put a DCM-style (compliance settings in 2012 SCCM terminology) check in place for each of my management/gateway servers to make sure they are all running the same UR. Would looking
    at the OMVersion.dll file (file version properties) in the AgentManagementamd64Agent directory be a safe way to evaluate that? Or, would it be best to simply look at the Get-Hotfix output for the provided KB for the UR and "assume" that it was installed
    for the various components.

    I come from the SQL Server world where the build number stored in the serverproperty and/or other registry entries makes it relatively easy to find out if we're patched or not.

  2. Kevin Holman says:

    @SKusen -

    Great question. Patchlist information is stored on agents in the Windows Installer data, and even our own built in discoveries to get the agent's Patchlist information comes from a script that connects to the Windows Installer data via Wscript: Wscript.CreateObject("WindowsInstaller.Installer")
    to pull the data back into SCOM. However, this location doesn't exist for management servers, it only works for agents.

    The reason I use the DLL versions as a spot check, is because LONG ago in the past, we had a bug where the patch installed, but didn't drop/update the DLL's and so the update never really applied. I guess I get stuck in my old ways and never trust update packages
    anymore.... so I still spot check the DLL's to get a file version info.

    There are plenty of DLL's you could check.... OMVersion.dll is certainly one of them you should be able to use for a check.

  3. KENT says:

    Hi Kevin
    thanks for your great work
    regarding "The DownTime report from the Availability report does not handle the Business Hours settings"

    Guess I have to perform the steps described, to have the issue solved

  4. SKusen says:

    Many thanks for the reply and confirmation of what I was seeing. Have a great day!

  5. JRPritchard says:

    Thank you Kevin, taking the fear our of the UR upgrade 🙂
    Good to note your point about the Windows Update vs. Manual Install of Agents.

  6. JStar73 says:

    Hi Kevin,
    Great post and explains everything very well.
    Since writing your post I noticed there has been a Linux mp updated for UR9 (https://support.microsoft.com/en-us/kb/3141435) . However; I see that the version is still 7.5.1045.0 (2015/08). Are you
    able to ask internally to find out where this updated release is?
    Also; I have never seen a rollback plan (or steps) for the T-SQL scripts. Is there a method to rollback the MS-SQL scripts, like just applying the previous UR scripts over the top? Or is it a case or restoring the database from last backup?
    Thanks again for your time and effort.
    J*73

  7. Bila828 says:

    Hi Kevin!
    I know it's not the right way but could it work if I update the Management Serves, Consoles and SQL databases at once and update the gateways and agents only the next day?
    Thanks!

  8. Chis says:

    I haven't touched SCOM in years. New job, inherited the SCOM environment which I will have to rebuild at some point. But, no Roll Ups had been applied. Appreciate the time you took to create this, its spot on.

    Bookmarked and saved your Blog.

    Thanks for helping out on a Sunday.

    Chris

  9. Kevin Holman says:

    @Jstar73 -

    I am aware of the issue with the Linux KB article being released for updated MP's, but the actual MP's are not available, and I am working that with the product group as we speak. I'll update this post when this gets resolved.

    @ Bila828 -

    Yes - you absolutely could update in the way you mentioned. We prefer to have all the infrastructure updated to the same level "as soon as possible" but we totally understand updating agents is a considerable effort, and customers often choose NOT to even update
    agents sometimes if the core benefits they were applying an update for apply to the infrastructure more than agent related fixes. I have customers running UR7 on the SCOM servers while the agents are running UR1. No issues.

  10. K Engelhardt says:

    https://support.microsoft.com/en-us/kb/3141435 -

    Issues that are fixed in this update rollup

    •Discovery of Linux computers may fail for some system locales
    Using the Discovery Wizard or Windows PowerShell cmdlets to discover Linux computers may fail during the final Agent Verification step for computers that have some system locales, such as zh_TW.UTF-8. The scxadmin command that is used to restart the agent during
    the discovery process did not correctly handle Unicode text in the standard out-of-the-service command.

    •The UNIX/Linux Agent intermittently closes connections during TLS handshaking

    Symptoms include the following:

    •Failed heartbeats for UNIX or Linux computers, especially when the SSLv3 protocol is disabled on the Management Servers.

    •Schannel errors in the System log that contain text that resembles the following:

    A fatal error occurred while creating an SSL client credentials. The internal error state is 10013.

    • WS-Management errors in the event log that contain text that resembles the following:

    WSManFault
    Message = The server certificate on the destination computer ( Encountered an internal error in the SSL library.

    Error number: -2147012721 0x80072F8F
    A security error occurred

  11. Cloud-Ras says:

    Beautyful blog on install UR 9 🙂
    Thanks.

  12. Cloud-Ras says:

    Beautyful blog on install UR 9 🙂
    Thanks.

  13. Nachi_M says:

    Hi Kevin, Really very helpful and explains everything very well. I wanted to ask you about the version that shows after the UR update. After the UR8 all the DLL's shows the correct version 7.1.10226.1118. But if i look at the SCOM Console [MS and Agent]
    Still it shows 7.1.10226.0 version. Is that something missing here?

  14. Kevin Holman says:

    @ Nachi_M -

    The console views do not show you the version information of patches - that is why I check the DLL's on each server just to make sure.

  15. Shaik_Saeed says:

    hi Kevin, thank you so much for all your hard work , i did upgrade my SCOM Server but i guess i made a little mistake on my SQL script, i only Ran "Update_rollup_mom_db.sql" , coz when i try to run "UR_Datawarehouse.sql" script i see lots of red, can i
    still run this "UR_Datawarehouse.sql" , would it cause any issue if it has lost of Red Syntex ?kindly reply .
    Thanks

  16. JStar73 says:

    Hi Kevin,
    Looks like the Linux mp has been updated, thanks for that 🙂
    Looking at shaikh's comment above - I emphasize the other question I had around rollback of the MS-SQL database work. Can you please provide some direction on what you recommend for rollback of the T-SQL scripts if/when required?
    Appreciated,
    Jock.

  17. Kevin Holman says:

    On rollback planning:

    1. Rollback for SQL scripts = restore DB's from backup.
    2. Rollback for management servers and GW's = restore Management server OS from backup, or rebuild new MS and patch to previous level.
    3. Rollback for management packs = restore DB's from backup, or delete MP's (not likely)

    I haven't seen a failed deployment or need for a rollback, ever. But I understand the need for planning for change control.

  18. MichielM says:

    Hi Kevin,
    A customer of us has updated their SCOM environment since UR3 without running the sql scripts and importing the management packs. I am not sure if its okay to run the queueries now and import the mp's or to rebuild the environment. Any ideas?

  19. Kevin Holman says:

    @MichielM -

    It should be fine to update the environment. Honestly - I'd recommend just applying UR9 completely.

    A rebuild should not be necessary. The biggest problem with an environment that never ran the SQL scripts - and still has an "RTM" patchlevel database.... will be that purging will timeout/fail during grooming and never complete. My experience is that customers
    can be in this condition for years and once we apply the SQL script part of the update, it cleans up nicely.

  20. patricia says:

    Hi Kevin, excellent post!!
    I´m having some issues with an agent, I made the manual installation using Msiexec.exe /i momagent.msi NOAPM=1, now when I tray to apply the UR9 to this agent won´t let me, any ideas?

    Best Regards,

  21. patricia says:

    Hi Kevin, excellent post!!
    I´m having some issues with an agent, I made the manual installation using Msiexec.exe /i momagent.msi NOAPM=1, now when I tray to apply the UR9 to this agent won´t let me, any ideas?

    Best Regards,

  22. Ramesh says:

    We want to integrate SCOM 2012 with OMS, and for that can we use UR9’s System Center Advisor MPs 9 (for branding update) with the UR6 SCOM 2012 R2 environment.

    Please let me know if this downgrade combination works? Or is it mandatory to upgrade the SCOM UR6 environment to UR9?

  23. Brian W says:

    The microsoft forums have been no help thus far, so I'm going to try here... It appears UR9 has a bug where the Microsoft Generic Report Library MP can't deploy reports. I get the following alert, and cannot resolve. I've reverted to pre-UR9 snapshot and
    tried multiple times using these steps provided.

    Failed to deploy reporting component to the SQL Server Reporting Services server. The operation will be retried.
    Exception 'DeploymentException': Failed to deploy reports for management pack with version dependent id '54879bf7-2676-e37a-6463-d3d2932a789f'. Failed to deploy report 'Microsoft.SystemCenter.DataWarehouse.Report.AvailabilityTime'. System.Web.Services.Protocols.SoapException:
    An unexpected error occurred in Report Processing. ---> Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: An unexpected error occurred in Report Processing. ---> System.UnauthorizedAccessException: Access to the path 'C:UsersSCOMR2DWSvcAppDataLocalTemp1asmjg1_.out'
    is denied.
    at Microsoft.ReportingServices.Library.ReportingService2005Impl.SetReportDefinition(String Report, Byte[] Definition, Guid batchId, Warning[]& Warnings)
    at Microsoft.ReportingServices.WebServer.ReportingService2005.SetReportDefinition(String Report, Byte[] Definition, Warning[]& Warnings)

    One or more workflows were affected by this.

    Workflow name: Microsoft.SystemCenter.DataWarehouse.Deployment.Report
    Instance name: Data Warehouse Synchronization Service
    Instance ID: {79F86925-00D2-D87A-2F01-231853036CC3}
    Management group: SCOMTEST

  24. Kevin Holman says:

    @Brian W -

    I have not seen this. However, this report was updated in UR9.

    Did you try and update the RDL file with a new one per the instructions in the KB article - or did you simply update the MP's and that's it?

    It looks like it is referencing something on your system - your DW service account is referencing a local path which it should not. I have not tested actually updating the RDL file.... that process even seems odd to me, as we should update the RDL using report
    deployment, not some manual process.... I find that whole thing odd.

    I am guessing since you follow the KB article, and not my blog for your updates - you did modify the RDL?

  25. stephen says:

    Would it be inadvisable to set the auto approve option to true before the install so that the remotely managed servers could be put right back into monitoring skipping the pending management?

    Seems like doing this would save some time and minimize the amount of time servers spent in this suspended state.

    1. Kevin Holman says:

      @ Stephen -

      There is no advantage to that. There is NOT any kind of monitoring outage when agents are in pending. I think you might misunderstand how that works. Putting agents in pending for update is simply a convenient way for you to update them, and is optional. It doesn't affect monitoring in any way.

      1. stemo76 says:

        Thanks for the response, I also found out setting it to auto-approve doesn't allow the update to happen automatically.

  26. Roger Salinas says:

    Hi Kevin, Just wanted to say Thank you- as always for providing your invaluable information in these blog posts. I've been a long time reader and follower of your blog... Thanks again!

  27. scomguruNM says:

    I am getting ready to update SCOM 2012R2 RTM 7.1.1.10226.0 to UR9. Do I need to apply the following per KB installation notes

    Installation Notes:
    To enable the web console fixes, add the following line to the %windir%\Microsoft.NET\Framework64\v2.0.50727\CONFIG\web.config file:

    Note Add the line under the section, as described in the following article in the Microsoft Knowledge Base:

    911722 You may receive an error message when you access ASP.NET Web pages that have ViewState enabled after you upgrade from ASP.NET 1.1 to ASP.NET 2.0
    The fix for the data warehouse BULK insert commands time out issue that is described in Update Rollup 1 for System Center 2012 R2 Operations Manager adds a registry key. This key can be used to set the time-out value (in seconds) for the data warehouse BULK insert commands. The following commands insert new data into the data warehouse.

    Note This key must be manually added on any management server on which you want to override the default BULK insert command time out.

    Registry location:
    HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft Operations Manager\3.0\Data Warehouse

    DWORD name: Bulk Insert Command Time Out Seconds
    DWORD Value: 40

    1. Kevin Holman says:

      No.

      This is why I do not reference them. The KB is very misleading and does a bad job of making you THINK those changes are required. They are NOT. They should only be changed IF you are impacted, because the UR's often open up optional settings that were previously not available to be changed.
      For example:
      Bulk Insert Command Time Out Seconds should NEVER be changed... unless specifically guided to do so by a Microsoft engineer. The KB makes customers think they need to set this to 40 seconds and that is WRONG. I support some of the largest customers in the world and we have never needed to change this. It should only be changed in specific customer scenarios where their SQL I/O is poor, or they are doing MASSIVE number of inserts and cannot reliably complete the insert in 30 seconds (default) but CAN reliably insert within 40 seconds. This is an incredibly rare condition.... because most customers failing bulk insert have serious I/O issues, and this Band-Aid will NOT solve their problem. This is why my opinion is that this should only be changed by a MS engineer.... and even then under great scrutiny.

  28. Sudarshan says:

    Which is more stable UR8 or UR9. We are planning to upgrade our SCOM R2 RTM version. Are there any prerequisites before we start the upgrade?

    1. Kevin Holman says:

      Neither is "more stable" than the other. If there were known issues in UR9, I'd have posted them to the "known issues" section of the blog. I'd always recommend applying the latest, as long as you do proper testing and the update has been released for more than 30 days. So I recommend UR9.

      1. Sudarshan says:

        Thanks Kevin. I would also like to know whether there are any prerequisites that needs to be done before starting to install UR9 from RTM?

        1. Kevin Holman says:

          No prerequisites. My article is about as step by step as you can get.

          1. Sudarshan says:

            Thanks Kevin. In our environment we have only 2 servers. One is SCOM Operations Console server and other is SCOM DB server. From my understanding we need to install all the above 4 files in Operations Console sever one after the other and run the SQL commands on the DB server. Please correct me if I am wrong.

      2. Bunny says:

        Hi Kevin,

        Agents which are installed manually are still showing as UR 7. Do we need to run the agent patch manually on those.

        Thanks.

        1. Kevin Holman says:

          Correct. Or use software distribution (SCCM) or change them to remotely manageable and then run a repair.

  29. Sudarshan says:

    Please reply to my above question Kevin!

    1. Kevin Holman says:

      My blog is about as step by step as I am willing to go. If you aren't clear between the KB article and this step by step, I'd highly recommend opening a support case with Microsoft to walk you through the process.

  30. Eric says:

    Hi Kevin, Thanks for all the UR posts they are very much appreciated. I am having trouble finding the download for UR9 for the past two days. Do you know if it has been removed or if there is an issue?

    1. Kevin Holman says:

      I believe there was an issue with the catalog a couple days ago, but it is working now.

  31. Peter Svensson says:

    Anyone noticed that the DisplayName changed on the Windows Computers object from FQDN to NETBIOS name after the agent got UR9?

    1. Kevin Holman says:

      Nope. Not the case for me.

      1. Eric says:

        I am now able to see the files for download but the last updated date for the UR9 files is 3/21/2016. I wonder if they updated something in the UR.

      2. Peter Svensson says:

        During the upgrade face the Gateways was unfortunately updated first (du to missunderstanding). Do you Think that could have produced the "error" with the Displayname?

        1. Peter Svensson says:

          Problem solved. It was a customised MP that changed the FQDN to NETBIOS name

          1. Kevin Holman says:

            Wow. I am not even sure how an MP would be able to modify data for a key property of Windows Computer. That's actually pretty cool. 🙂

  32. Peter Svensson says:

    Strangest thing. I have a case with MS on it. Just wanted to check if anyone else have experienced it.

  33. sime3000 says:

    Hello Kevin,

    As you’re probably aware .NET Framework 4.6.1 is in general release and it is available via Microsoft Update.

    There is no mention of 4.6.1 on the “.NET Framework Requirements for System Center 2012 R2″ page @ https://technet.microsoft.com/en-us/library/dn281926.aspx . Other Microsoft products have an issue with 4.6.1 and we have had to block installation on those servers.

    Is .NET Framework 4.6.1 supported on a SCVMM 2012 R2 server or do you suggest that we block its installation ???

    Thanks

    1. Sean says:

      Were having an issue where our 2k8 R2 servers (Core and Full) are failing the Agent update from pending management with failure of OS verification due to Network Path not Found (Nearly instantly upon instantiation) but our 2k12 servers take the update just fine. Any ideas?

  34. Sean says:

    Sean

    April 6, 2016 at 1:44 pm
    Apologies this originally was posted under someone else's comment forgive the duplicate.

    Were having an issue where our 2k8 R2 servers (Core and Full) are failing the Agent update from pending management with failure of OS verification due to Network Path not Found (Nearly instantly upon instantiation) but our 2k12 servers take the update just fine. Any ideas?

  35. Bunny says:

    Hi Kevin,

    When updating agents to UR9 ,few servers I am getting error like "failed to install performance counter"- Parameter is incorrect.

    Is it something I need to reinstall agent?

  36. Lapark says:

    Hi Kevin, always appreciate these posts! I've got 2 questions:

    - The order of running the SQL scripts differs than what's listed on the KB support site (OpsDB then DW), I can't remember what I've done in the past, but I take this to mean it doesn't really matter what order the scripts are run, as long as they are run not too far apart from each other?

    - The version number of the Unix/Linux MPs is actually 7.5.1050.0 (published 2/16/16), not 7.5.1045.0 as listed here. Not really a question, just wanted to point it out!
    https://www.microsoft.com/en-us/download/details.aspx?id=29696

    Thanks

  37. Kevin Holman says:

    Correct - the order of SQL scripts is irrelevant.

    As to the Linux version - at the time the article was written they were older. New ones have come out since then, but I don't go back and re-write the articles.

  38. eliad says:

    Thanks!
    In the official page, they tell that if the console is shuted down, a boot is not required when installing the MSP, does it true?

    1. Kevin Holman says:

      That's why I post articles like this. My experience does not always mirror the KB. I have found sometimes a reboot is necessary even when the console is closed. YMMV.

  39. nicole says:

    Hello Kevin!
    This worked like a charm! Thanks SOO much for all that you DO and SHARE!

  40. John Couch says:

    I see that the agents go into a pending management state. I have 2200 agents in the PROD enviornment. Are these still monitored while in the pending state? Not sure I'd get all 2200 updated the same day.

  41. RBK says:

    Hi Kevin,
    Is there any powershell script to update the SCOM agents from a list of servers created on .txt or .csv. We have done CU9 and agents were on pending management for long time. These agents were later rejected due to the same (Shows in Repair on Progress window for a longer period)
    Thanks,
    RBK

Skip to main content