UR11 for SCOM 2012 R2 – Step by Step

 

 

KB Article for OpsMgr:  https://support.microsoft.com/en-us/kb/3183990

Download catalog site:  https://catalog.update.microsoft.com/v7/site/Search.aspx?q=3183990

 

 

NOTE:   I get this question every time we release an update rollup:   ALL SCOM Update Rollups are CUMULATIVE.   This means you do not need to apply them in order, you can always just apply the latest update.  If you have deployed SCOM 2012R2 and never applied an update rollup – you can go straight to the latest one available.  If you applied an older one (such as UR3) you can always go straight to the latest one!

 

Key Fixes:

• Network discovery fails because of monitoring host crash if no paging file is set on the operating system
  When no paging file is set on the operating system, the page file size is implicitly set to 0. This causes the monitoring host to crash. This update fixes such an exception.

• Backport PuTTY 0.64 and 0.66 updates from 2016 release
  Operations Managers ssh-based administration of UNIX/Linux computers (agent discovery and installation, upgrade, uninstallation) now supports UNIX and Linux computers that are configured to require SHA2 HMACs and those with Key Exchange Algorithm changes, as specified in RFC 4419 (Ubuntu 15.10, 16.04 LTS).

• Update Register-SCAdvisor cmdlet for WEU workspaces
  This update adds support to register the Operations Manager Management group to workspaces in regions other than Eastern US by using the Register-SCAdvisor cmdlet. The cmdlet takes an additional optional parameter (SettingServiceUrl), which is the URL for setting the service in the region of the workspace. If it is not specified, the workspace is assumed to be in the Eastern US.

• ACS eventschema.xml has incorrect parameter mappings for multiple audit events
  The report named Usage_-_Sensitive_Security_Groups_Changes used to say n/a\n/a for some events in the Changed By column. And in some events, the Member User column contained the account name of the user who made the change instead of the account that was added or removed. This fix resolves this issue, as the Changed By column now contains the account name of the user who made the change, and the Member User column contains the name of the added or removed account, where applicable.

• Memory leak when monitoring network devices by using SNMPv3
  This update fixes a memory leak in Network Monitoring area that occurs while monitoring network devices by using SNMPv3.

• Web Console user can view datawarehouse performance or SLA widget data outside of their scoped dashboard views
  This update implements verification of the logged-in user to confirm that the user has access to the opened dashboard before loading the same.

• Downtime duration doesn't take business hour into consideration
  Business hours are being calculated even when the Business hours check box is cleared. This update resolves this issue.
  The updated RDL files are located in the following location:

  %SystemDrive%\Program Files\Microsoft System Center 2012 R2\Operations Manager\Server\Reporting

  To update the RDL file, follow these steps:

  1. Go to https://MachineName/Reports_INSTANCE1/Pages/Folder.aspxMachineName //Reporting Server.
  2. On this page, go to the folder to which you want to add the RDL file. In this case, click Microsoft.SystemCenter.DataWarehouse.Report.Library.
  3. Upload the new RDL files by clicking the upload button at the top. For more information, see the Upload a File or Report (Report Manager) topic on the Microsoft Developer Network website.

• Cisco 3172 PQ network device certification issues
  This update fixes issues in monitoring the Cisco 3172 PQ network device and its components.

• Adding SCOM assessment links in the Operations Management Suite view in the SCOM console
  Links for Operations Manager Assessment and Pre-Configuration steps for Operations Manager Assessment are added in the Operations Management Suite Connection node under the administration pane. SCOM assessment solution in OMS is currently in private preview, please reach out to your "TAM or other Microsoft contact" to obtain access to the solution.

• SQL Server Seed relationship with a server that is running Windows
  The dynamic members of the group are not populated if the dynamic rule is based on a hosted relationship with Windows Server. This fix enables retrieval of hosting entity.

• Alert subscriptions are not always fired for 3 state monitors
  This update allows for configuration of a 3 state monitor to raise alerts; whose severity is in sync with monitor’s health state. One can create a subscription to be notified on modification of alert severity. Even if the monitor’s state keeps toggling between warning and critical, severity of the alert keeps being updated, and a notification fired on an update to the severity of an alert.

• When you connect SCOM to OMS, Availability monitors health state of some management servers changes to Warning state
  If OMS workspace is configured to collect certain event logs and if those event logs are not present on the management servers that are connected to that workspace, the “Availability” monitor’s health state on those management servers that are used to change the Warning state. This state change scenario is fixed. This prevents the switch to Warning state.

• RunAs Account password expiration does not work with Active directory Password Settings Objects that breaks the validation of LOCAL User Accounts
  Local Accounts could not be validated by using ADSystemInfo. Therefore, when any local account is added into RunAs account, an Error event is logged in Event Viewer for an exception in validating the local account. After this update, local accounts are validated.

• MPB Entries in Catalog database for the VersionIndependentGuid column is updated
  This update enables the SCOM console to show the correct mpb installation status in the management server when it tries to connect to an online catalog to update mpbs.

• If the first try of importing MPB failed then re-importing the MPB was not possible until the SCOM console is closed and reopened
  This update enables re-download and installation of an mpb, without closing and reopening the SCOM console, even if the first try installation of that mpb failed because of a dependency issue.

• Change of the displayname field for a group in a sealed or unsealed management pack
  Renaming a group through PowerShell cmdlets was not displaying the new group name in the SCOM console. This update resolves this issue and the renaming of a group correctly displays the renamed group name in the SCOM console.

New Linux operating system versions supported

• Ubuntu Linux 16.04 LTS (x86 and x64) is now supported in System Center 2012 R2 Operations Manager.

Issues that are fixed in the UNIX and Linux management packs

• During UNIX/Linux computer discovery, the GetOSVersion.sh script is run with sudo elevation if a sudo-enabled user is selected for Discovery. This update prevents the GetOSVersion.sh script from being run with sudo elevation and does not have to be authorized in the /etc/sudoers folder.

• Scripts executed by the ExecuteScript method in Management Packs always run from the /tmp folder. With this update, the temporary folder for scripts is now configurable. To use another folder, update the symbolic link to link to a temporary folder of your choice:

  /etc/opt/microsoft/scx/conf/tmpdir

• UNIX or Linux computers together with sshd versions that implement the Key Exchange Algorithms described in RFC 4419, such as Ubuntu 15.10, cannot be discovered with the Discovery Wizard.

• Network statistics collected on AIX servers are reset when another tool such as NetStat is also used.

• Physical disks are shown incorrectly as offline if an LVM snapshot is taken.

 

 

 

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
   • Audit Collection 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

Additionally, we will add the steps to update Linux management packs 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 role to the SQL 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 usually does not provide any feedback that it had success or failure. 

 

You can check the application log for the MsiInstaller events to show completion:

 

Log Name: Application
Source: MsiInstaller
Date: 8/31/2016 9:01:13 AM
Event ID: 1036
Description:
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 UR11 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:

 

 

 

Additional Management Servers:

 

I now move on to my additional management servers, applying the server update, then the console update and web console update where applicable.

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: 

 

 

The applicable updates show up under optional – so I tick the boxes and apply these updates.

 

 

After a reboot – go back and verify the update was a success by spot checking some file versions like we did above.

 

 

Updating ACS (Audit Collection Services)

You would only need to update ACS if you had installed this optional role.

On any Audit Collection Collector servers, you should run the update included:

 

 

 

A spot check of the files:

 

 

 

 

 

Updating Gateways:

 

I can use Windows Update or manual installation.

 

The update launches a UI and quickly finishes.

I was prompted for a reboot.

 

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:

 

 

***NOTE: You can delete any older UR update files from the \AgentManagement directories. The UR’s do not clean these up and they provide no purpose for being present any longer.

 

 

 

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 or clean install)

 

First – let’s run the script to update the OperationsManagerDW (Data Warehouse) database.  Open a SQL management studio query window, connect it to your Operations Manager DataWarehouse database, and then open the script file (UR_Datawarehouse.sql).  Make sure it is pointing to your OperationsManagerDW database, then execute the script.

You should run this script with each UR, even if you ran this on a previous UR.  The script body can change so as a best practice always re-run this.

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:   “Command(s) completes successfully”

 

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

You should run this script with each UR, even if you ran this on a previous UR.  The script body can change so as a best practice always re-run this.

 

 

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.  

I have had customers state this takes from a few minutes to as long as an hour. In MOST cases – you will need to shut down the SDK, Config, and Monitoring Agent (healthservice) on ALL your management servers in order for this to be able to run with success.

 

You will see the following (or similar) output: 

or

 

 

IF YOU GET AN ERROR – STOP!   Do not continue.  Try re-running the script several times until it completes without errors.  In a production environment with lots of activity, you will almost certainly have to shut down the services (sdk, config, and healthservice) on your management servers, to break their connection to the databases, to get a successful run.

Technical tidbit: Even if you previously ran this script in any previous UR deployment, you should run this again in this update, as the script body can change with updated UR’s.

 

3. Manually import the management packs

 

There are 55 management packs in this update!   Most of these we don’t need – so read carefully.

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/OMS, and language specific.  Only import the ones you need, and that are correct for your language.  I will remove all the MP’s for other languages (keeping only ENU), and I am left with the following:

 

What NOT to import:

The Advisor MP’s are only needed if you are using Microsoft Operations Management Suite cloud service, (Previously known as Advisor, and Operations Insights).

The APM MP’s are only needed if you are using the APM feature in SCOM.

Note the APM MP with a red X. This MP requires the IIS MP’s for Windows Server 2016 which are in Technical Preview at the time of this writing. Only import this if you are using APM *and* you need to monitor Windows Server 2016. If so, you will need to download and install the technical preview editions of that MP from https://www.microsoft.com/en-us/download/details.aspx?id=48256

The TFS MP bundle is 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.

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

I import all of these shown without issue.

 

 

 

4. Update Agents

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

One the Management servers where I used Windows Update to patch them, their agents did not show up in this list.  Only agents where I manually patched their management server showed up in this list.  FYI.   The experience is NOT the same when using Windows Update vs manual.  If yours don’t show up – you can try running the update for that management server again – manually.

 

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.

I manually re-ran the server MSP file manually on these management servers, from an elevated command prompt, and they all showed up.

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

 

 

The current Linux MP’s can be downloaded from:

https://www.microsoft.com/en-us/download/details.aspx?id=29696

 

7.5.1060.0 is current at this time for SCOM 2012 R2 UR11.

****Note – take GREAT care when downloading – that you select the correct download for SCOM 2012 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. 

 

 

NOTE:   Upon first import – you might see that “Linux Operating System Library” (Microsoft.Linux.Library.mp) file fails to import.  If this happens, simply make sure you have imported version 7.5.1060.0 of UNIX/Linux Core Library (Microsoft.Unix.Library.mp) FIRST, then you can import “Linux Operating System Library” (Microsoft.Linux.Library.mp) without issue.

 

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 – you need to restart the “Microsoft Monitoring Agent” service on any management servers which manage Linux systems.  I don’t know why – but my MP’s never drop/update in the \Program Files\Microsoft System Center 2012 R2\Operations Manager\Server\AgentManagement\UnixAgents\DownloadedKits folder until this service is restarted.

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.

Finally:

 

 

 

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 matching update version.

 

 

 

Review:

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

• Anonymous
  September 06, 2016
  Hi Kevin, Thanks, Excellent document. I reading you all the blogs, all blogs are amazing and very help full for me. Thanks again.
• Anonymous
  September 12, 2016
  Hi!As Always great post. I Always read your blogpost when it comes to updating Rollups. Just a thought. In this Rollup there is an update for a report server (or rather an updated rdl file). Its only stated in the "what is fixed" list and not in the actual upgrade step. Its easily missed. Maybe you could add this a step in your guide?
• Anonymous
  September 13, 2016
  The comment has been removed
• Anonymous
  September 27, 2016
  Hey Kevin, What version should the agents read in the console after the update? Currently mine still read 7.1.10184
  • Anonymous
    September 27, 2016
    We do not ever update agent version, nor have we ever. The blog post explains where to look for agent version in the patchlist view.
    • Anonymous
      November 21, 2016
      Hi Kevin,With respect to the agent versions I have always found that the agent version updates in the console. Even since SCOM using 2007 R2.Not sure if I am understanding what is being questioned here. So are you definitively saying that the console version number is never updated to the current version of the agent. I have always found this to be the case...Regards,Michael McGrathMcGrath IT Consultancy Services(Currently @ Credit Corp Group Pty Ltd)
      • Anonymous
        November 21, 2016
        Agent version under Agent managed has never changed with any UR in SCOM 2012. Those are major version numbers and only reflect SCOM 2012RTM, SCOM 2012SP1, or SCOM 2012R2 build versions.
        • Anonymous
          November 22, 2016
          Hi Kevin,Thank you for your timely response and verification, it is much appreciated. Funny that seems to have slipped by me for some reason in SCOM 2012. I know that checking version numbers when I managed SCOM 2007 R2, I seem to remember checking the agent version numbers as a way of verifying agents were current after I performed a particular CU. Kind regards,Michael McGrathMcGrath IT Consultancy Services(Currently @ Credit Corp Group Pty Ltd)
        • Anonymous
          November 22, 2016
          Hi Kevin,Thank you for your timely response and verification, it is much appreciated. Funny that seems to have slipped by me for some reason in SCOM 2012. I know that checking version numbers when I managed SCOM 2007 R2, I seem to remember checking the agent version numbers as a way of verifying agents were current after I performed a particular CU. Kind regards,Michael McGrathMcGrath IT Consultancy Services(Currently @ Credit Corp Group Pty Ltd)PS: As a long time standing SCOM administrator I appreciate the work and effort you put in Kevin thank you!!!
        • Anonymous
          November 22, 2016
          Hi Kevin,Firstly excellent post and thank you for the quick response, it is much appreciated. Funny that seems to have slipped by me for some reason in SCOM 2012. I know that checking version numbers when I managed SCOM 2007 R2, I seem to remember checking the agent version numbers as a way of verifying agents were current after I performed a particular CU. Kind regards,Michael McGrathMcGrath IT Consultancy Services(Currently @ Credit Corp Group Pty Ltd)PS: As a long time standing SCOM administrator I appreciate the work and effort you put in Kevin thank you!!!
• Anonymous
  September 29, 2016
  hi Kevin,we ran windows update on our SCOM management server after the rebooting both of our management server i notice that all my agent went on "pending" status so i right click on my agents and install the updates for agent ,just notice that i never did run the update on any of Management server from UR9 to UR11, all my agents are showing "Green in Status" ?? now can i follow the above steps to do update from UR9 to UR11? would i cause any issue? kindly help.Thanks
  • Anonymous
    September 29, 2016
    I'm not quite sure what you are asking.If you applied the UR11 updates via Windows Update there is no need to reinstall the updates, but you can reinstall them manually just to be sure. You can always check the DLL versions I document if you dont know, or look in Programs and Features for installed updates and history.
• Anonymous
  September 30, 2016
  Hi Kevin,I see non of the agents are placed in to "pending Management" after up-gradation to UR11. I have tried running Update Couple of times with elevated command prompt on the Management server.I can see all the files as mentioned in the blog are updated with latest version, folders like Server,Console. even I can see successful events in the events log.
  • Anonymous
    September 30, 2016
    I hear this complaint a lot, and every single investigation it was user error:1. Are the agents set to "Remotely Manageable" in the console?2. Are you running the update as a user with SCOM admin, Local Admin, SysAdmin over SQL, and Local Admin over SQL?3. Are you running the MSP based update file for the server, from an elevated command prompt?When all three of these are met, it always works. Every time we looked into it, a customer was missing a right, or the agents were not set to remotely manageable, or they weren't running it from an elevated cmd.
    • Anonymous
      October 12, 2016
      The comment has been removed
      • Anonymous
        November 25, 2016
        @Kevin: Did you find a solution for the agnets not show in pending management?
        • Anonymous
          May 31, 2017
          NO, again I faced the same problem for UR13 today
• Anonymous
  October 03, 2016
  Hello Kevin goodnight, recently created a SCOM homologation environment UR9 2012 R2 (same version of my production environment), I'm having difficulty using the agents already installed for the production environment. What are the best practices for use of homologation environment?The idea is to use all the machines that are already in production to homologate treshold and MPs to then rise in production with the necessary changes.Thank you
• Anonymous
  October 04, 2016
  Just a heads up if you have linux agents they will not appear in the pending view. To update them right click linux agent in admin view and follow the prompts. This is something I didn't know so hopefully of help to others.
• Anonymous
  October 07, 2016
  Kevin, I think this is the first time I've seen the update script being run on the OperationsManagerDW DB before the OperationsManager DB. Is there any particular reason for the change in order?
  • Anonymous
    October 07, 2016
    Checked the descriptions in TechNet and it looks like it doesn't really matter. URs 3,5,6 & 7 all mention updating the DW first.
• Anonymous
  October 11, 2016
  Almost every update is almost 100% the same - always wonder why it is so difficult for scom admins...
• Anonymous
  October 17, 2016
  If many people are reporting that running the SQL DW script takes a long time (or it's failing), why not stop all SCOM services on all Management Servers beforehand as a best practice?
  • Anonymous
    October 17, 2016
    I meant the script for the Operational DB, not the DW DB.
    • Anonymous
      October 17, 2016
      The comment has been removed
• Anonymous
  October 19, 2016
  Thank you Kevin , once again :-) Really good doc..
• Anonymous
  October 30, 2016
  Hi Kevin/All,Thanks for the detailed blog, I am updating SCOM in order to gain the functionality to connect my on-prem SCOM solution with OMS in Azure. I have run through the above and installed UR11 successfully. I used the windows update method and then ran the SQL scripts with no issues, though my Console now shows the update version number (7.1.10226.1239) what should read Operations Management Suite instead shows the old System Center Advisor. Has anyone come across an issue like this before?Thanks!
  • Anonymous
    October 30, 2016
    Did you import the new advisor management packs included in UR11?
• Anonymous
  November 08, 2016
  The comment has been removed
  • Anonymous
    November 08, 2016
    Just hit yes, or OK. Doesn't matter.
    • Anonymous
      November 08, 2016
      Thanks a lot for your quick reply.
• Anonymous
  November 23, 2016
  fantastic document - followed this guide through from the vanilla version without any issues!
• Anonymous
  November 29, 2016
  The comment has been removed
• Anonymous
  December 08, 2016
  Afternoon,Thanks for the great write up, used it and things went off without a hitch!I have a question though that I cannot seem to find a solid answer for so hopefully you or someone else reading here would be willing to assist with?Our DBAs are on a mission to lock down, as tightly as possible without breaking anything, DB access for SCOM/accounts and SCOM admins.I have been asked to provide a list of exactly which SCOM related accounts require what sort of ongoing access to both OperationsManager and DataWarehouse databases. I had asked that the environment be left as it was after initial install and subsequent UR updates but I am getting some constant push back, understandable to some degree. However, none of our SCOM server environments have internet access, we have very restrictive firewall rules already so I never viewed it as that critical.So, to keep the peace and to assist in this effort (and hopefully not break anything), could you guys provide me with any substantial details on SCOM account(s) rights/requirements to the databases?Thanks again for your time and assistance!Tony
• Anonymous
  January 05, 2017
  Hi Kevin, I installed SCOM 2012R2 RTM (7.1.10226.0) and followed the procedure to apply RU11. Successfully installed the Server, WebConsole & Console .msp (Kb3183990) & also successfully executing the SQL scripts against the two DB respectively. Restarted the server too.But when i view issue "Get-SCOMManagementServer | fl Version" the output still displays Version: 7.1.10266.0. When I view the Console version its show me Version 7.1.10226.1239. So, is my server actually updated to RU11?What could be wrong?
• Anonymous
  January 05, 2017
  @Cosmic - I might not understand - why are you using powershell to get the version? Did our documentation say to do that anywhere?
  • Anonymous
    January 05, 2017
    Sorry Kevin, but i thought the powershell should also reflect the changes. Thanks anyway for a good step by step.
    • Anonymous
      January 05, 2017
      Unfortunately I don't think it will. Most versions stored in SCOM are major version only. Which is why I call out spot checking DLL files. Its the best way I know to be sure.
• Anonymous
  January 26, 2017
  Where do I see if the Gateway Management server has the correct patch? Is it that on DLL file: 'NetworkDiscoveryModules.dll'? I updated today 26.01.2017 one of my gateway server and the dll last modified date is last year but the version is .1239. Is there ANY way to see the patch level from scom console for gateways? This thing really should be cleared and FIXED!
  • Anonymous
    January 26, 2017
    How to verify the GW UR level is documented above - yes it is that DLL file version. No there is no way to determine UR level of the MS roles or GW in the SCOM console. Which is why I document simple methods to check in each article I write.
• Anonymous
  January 26, 2017
  Hi Kevin,We have updated the UR11 by following the mentioned steps. Thank you,Excellent document. Can you please let us know the steps to update the reporting server.
  • Anonymous
    January 27, 2017
    If there was a step to update reporting, it would be in the article.
    • Anonymous
      January 27, 2017
      Thank you for the response. We are facing issue with Windows OS version 2008 R2 SP1 and they are not reporting to SCOM 2012 R2 UR11. Is there any compatibility version for this OS version in UR11?
      • Anonymous
        January 27, 2017
        No.
        • Anonymous
          February 01, 2017
          Hi Kevin, I need to manually install SCOM agent on few of the clients. So can you please let me know where can i get the updated agent.msi file to install them manualy (Including UR11).Now are installing SCOM 2012 R2 agent.msi on the client and then KB file on the client, So need one msi file which includes UR11.
          • Anonymous
            February 01, 2017
            There no such thing. We have never had a single file that included the agent and a cumulative update. You must install these as two steps.
• Anonymous
  February 13, 2017
  Hi Kevin,We have SCOM 2012 R2 UR11 installed on 3 management servers and we also have another environment in same domain with 1 SCOM 2012 R2 Management server.Now we need to add this 1 management server to existing other 3 management servers group. Currently this 1 MP is not part of any management group but connected to different database. Kindly help me with the steps to change the database and management group of this 1 MP. Thank you !!!
• Anonymous
  February 16, 2017
  Hi Kevin,you mentioned the topic "Alert subscriptions are not always fired for 3 state monitors" is fixed with UR11. This is sensational news for me, even if it comes to "on-call-services" in an IT-Environment!!!So you said the fix takes effect when you create a 3-state-monitor by yourself ("This update allows for configuration of a 3 state monitor to raise alerts...")My question: Does this fix also take effect on already existing monitors of installed Management Packs? Or only on new created monitors?Hope for a reply and Thanks in advance!Bernd