Just last night, Microsoft released Cumulative Update 3 (UR3) for System Center 2012. This release contains a smaller number of fixes and is targeted mainly at Operations Manager (SCOM/OpsMgr), Data Protection Manager (DPM) and Service Manager (SCSM) you can find a
description of it
here.
The SCOM 2012 specific issues that this hotfix resolves are as follows:
- When you run a Windows PowerShell cmdlet, you receive the following error message:
Get-BPAModel is not recognized as the name of a cmdlet
- When you try to change a URL in the "web application availability monitoring" template instance, the change is not applied.
This
post will walkthrough the steps required to deploy the Update Rollup 3 hotfix to your
SCOM / OpsMgr 2012 deployment. As in the past, this post is an updated version of my
previous post on deploying Update Rollup 2 (CU2) to SCOM / OpsMgr 2012.
Update February 2013 - If you want to be in with a chance of winning a copy of our Mastering System Center 2012 Operations Manager book, then check out the link below to see what you need to do:
Win a Copy of Mastering SCOM 2012 by Evaluating System Center
The process to deploy the update is quite simple. Similar to Update Rollup 2, there is
no need to run any SQL queries against the SCOM databases as part of the update
- as was the case with the SCOM 2007 R2 CU's. You can choose to deploy this update either manually or by using Microsoft Update. This post will outline the manual installation process.
Some of the information below is
taken directly from
KB2756127 on the Microsoft
Support website.
To begin, here are some known issues to be aware of
when deploying this update rollup:
- After you install the update rollup package on all roles on the System Center Operations manager 2012 server, except on the Agent and Gateway roles, the updates do not appear in the Add or Remove Programs item in Control Panel.
- After you install the update rollup package, the version number of the console is not changed. After you install Update Rollup 2 for System Center Operations Manager 2012, the version number of the console is 7.0.8560.0 as expected
- After you uninstall the update rollup package, a System.Management.Automation.ActionPreferenceStop exception occurs in the Discover Agent Versions script, and the script fails. To resolve this issue, change the InstallDirectory value in the "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\System Center Operations" registry subkey to C:\Program Files\System Center 2012\Operations Manager\PowerShell.
- After you install the update rollup package on a web console, you receive the following error message in Windows Internet Explorer:
Server Error in '/OperationsManager' Application.
To resolve this issue, close and then restart Windows Internet Explorer.
Installation Notes
- Update Rollup 3 is available in a number of languages but some components are language neutral, and the updates for these components are not localized.
- You must run these updates as an
administrator.
- You have to close the console before you apply
the console update to avoid having to restart the computer.
- You must restart and clear the browser cache to
start a new instance of Microsoft Silverlight.
- This update rollup should not be installed
immediately after you install the server. Otherwise, you could encounter an
issue in which the Health Service state remains uninitialized.
- If User Account Control is enabled, the .msp
update files must be run from an elevated Command Prompt window.
- System Administrator rights on the database
instances for the Operational Database and Data warehouse are required in order
to run updates on these databases.
As described in
KB911722, the web console
fixes will work after you add the following line to the
%windir%\Windows\Microsoft.NET\Framework64\v2.0.50727\CONFIG web.config
file:
<machineKey
validationKey="AutoGenerate,IsolateApps"
decryptionKey="AutoGenerate,IsolateApps" validation="3DES"
decryption="3DES"/>Note This line should be added under
<system.web>
Note: As with all updates, it goes without saying that you
should first make a full backup of your SCOM 2012 environment before proceeding
with these steps.
The supported installation order of
CU3 is as follows:
Server Infrastructure Deployment Order
Overview:
- Management server or server
- Gateway servers
- Reporting servers
- Web console server role computer
- Operations console role computers
Note: If Connected MG/Tiering is enabled, the top tier
should be patched first.
Update Management
Packs Overview:
- Manually import CU3 management packs
Agent
Deployment Overview:
- Apply the agent update to manually installed agents, or push installation
from the Pending view in the Operations console.
Note: This update rollup can be installed on agents either
before or after server
infrastructure.
Installation
The previous two rollups for SCOM 2012 (CU1 and CU2), were relatively small in size (75MB) however, this particular update is much larger and can be over 400MB if you need to deploy it to all of the different SCOM roles in your environment. It's still significantly smaller than previous SCOM 2007 R2 updates which were closer to 1.5GB in size!
Click on the link below to access the Microsoft Update Catalog (as shown in the screenshot) and download
the CU3 packages for each SCOM role that you have deployed (e.g. Agent, Management Server, Web Console, Console etc.) to a location on your SCOM 2012 Management Server:
Once you've downloaded the relevant updates to your SCOM management server, you should see a number of folders similar to the screenshot below depending on which roles you've chosen to download updates for.
Fisrt thing to do now is to double click on the "Update Rollup 3 for System Center 2012 - Operations Manager Server (2750631)" folder and then extract the contents of the .cab file contained inside of it as shown below
Update 12th October - A number of people have been having issues trying to locate the English version of the .cab file to manually deploy to the Console, Web Console and Reporting server roles. Here's the ones that worked for me:
Console -
all-kb2750631-amd64-console_755b85ba494fa5c83ca31cf40d38be5d6d0551ef.cab
Web Console -
all-kb2750631-amd64 webconsole_2ef77d6ea1080b83c10351001dc13bf7e6977b7a.cab
Reporting -
all-kb2750631-amd64-reporting_8043cc39d79514d1e633b645063100c136cf1f92.cab
You should now see the
KB2750631-AMD64-Server.msp file and this is the one that we will use to update the SCOM Management Server role.
Now, open up a Command Prompt with Administrative permissions and browse to the location on your SCOM 2012 Management Server that you extracted the Update Rollup 3 package to. Once here, you will need to execute the following command for each update package:
msiexec.exe /update <PackageName>
For example, if you are installing the extracted KB2750631-AMD64-Server.msp package, then type the following command and hit Enter:
msiexec.exe /update KB2750631-AMD64-Server.msp
You should now see the following dialog boxes open up indicating that the upgrade is in progress
After the update has been applied, you won't see any confirmation confirming it's finished, the above dialog box will just close out. Don't be alarmed that it's crashed or that you need to re-run the update again, this is just normal behaviour!
Once you've installed the server update package, you can then go ahead and follow the same steps from above to install the other update packages that are relevant to the SCOM server roles that you have deployed. In my environment, I have the SCOM Console and SCOM Web Console installed on the Management Server so after the server update package, I need to then extract those files, browse to their location from an administrative command prompt and then execute the following commands:
msiexec.exe /update KB2750631-AMD64-Console.msp
msiexec.exe /update KB2750631-AMD64-WebConsole.msp
Once these commands have finished installing, I'll then run the relevant commands on my SQL server that's running the SCOM Reporting role and my Gateway servers.
When you've updated your Management Server, browse to the SCOM 2012 installation folder - normally located at C:\Program Files\System Center Operations Manager 2012\Server. Once here, add a column view for 'File Version' and then sort the column by file version and you should see four files with a new version level of
7.0.8560.1036 as the screen below shows
If you don't see the product version updated as above to your files, then your server hasn't updated properly and you will need to revisit the installation to see if you've missed something.
Once you are happy that your first SCOM 2012 Management Server has been updated, then you can then move onto installing the new management packs that come with the CU3 hotfix.
Note: You only need to import the updated management packs once. You will not have to carry out this process for every SCOM server role that you upgrade.
After the Server update package (
KB2750631-AMD64-Server.msp) has been installed, you can now browse to the following location and locate the three new updated management packs that need to be imported into your SCOM 2012 environment (shown in the screenshot below):
C:\Program Files\System Center 2012\Operations Manager\Server\Management Packs for Update Rollups
To import these management packs, simply open up the SCOM Console and click on the Administration button in the wunderbar from the bottom left hand side of the screen. From there, expand the Administration view, right mouse click on Management Packs and then select Import Management Packs from the resultant menu
From the Import Management Packs window, click on the Add button, choose the Add From Disk option and then click on No when prompted to go online to download any dependencies
Now browse to the
"C:\Program Files\System Center 2012\Operations Manager\Server\Management Packs for Update Rollups " folder and select the three new management packs to import as shown below
If you have previously upgraded to Cumulative Update 1 (UR1), then you will notice that the version of the Data Warehouse Library management pack is the same version number for CU3 and this will not be imported. If you haven't upgraded to CU1, then the import will upgrade all three new management packs at this point.
Hit the Install button and if required, click on Yes from the security warning to confirm you are happy to continue
Once the import is completed, you should see a successful status beside either
two or three management packs (as mentioned above, the number of management
packs imported here depends on whether or not you've previously upgraded to CU1)
confirming you have imported them without issue
With the management packs imported, that finishes off the upgrade of the Management Server role and if you haven't upgraded the other SCOM server roles yet, then now's the time to do it.
Agent Infrastructure
Although the agent installation upgrade can be carried out at any time, I prefer to wait until I have upgraded my SCOM 2012 server infrastructure first before working on the agents.
To upgrade the agents using the SCOM 2012 Console, simply browse to the Administration tab again in the wunderbar, expand the Administration view, expand Device Management and then click on the Pending Management view to see all of the agents awaiting upgrade. Highlight the ones you want to upgrade, then click on the Approve link from the Tasks pane on the right hand side to update all of your push based agents
For any agents that have been manually installed, then you will manually need to
copy the .MSP file for the agent to each server and manually carry out each
upgrade.
Finally, the hotfix documentation available to me at the time doesn't mention anything about upgrading your Unix/Linux agents so for now it looks like the update is only applicable to Windows based systems. I'll update this post if that changes over the coming days.
