Kevin Holman's System Center Blog

Posts in this blog are provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified in the Terms of UseAre you interested in having a dedicated engineer that will be your Mic

How to apply System Center 2012 SP1 Update Rollup 2 (UR2) to other System Center components

How to apply System Center 2012 SP1 Update Rollup 2 (UR2) to other System Center components

  • Comments 2
  • Likes

 

I recently did a deep dive on how to apply UR2 to System Center 2012 SP1 Operations Manager.  http://blogs.technet.com/b/kevinholman/archive/2013/04/11/applying-update-rollup-2-ur2-to-opsmgr-2012-sp1.aspx

 

The following article covers some of the other System Center 2012 SP1 components, such as Orchestrator, App Controller, and Service Manager.

The KB article and download links are located at: http://support.microsoft.com/kb/2802159

 

Orchestrator 2012 SP1:

The simplest way to apply these updates to Orchestrator RunBook Servers and Runbook Designers would be using Windows Update, which can be controlled via WSUS or ConfigMgr since these are on the catalog. 

image

 

 

Alternatively, you can download these and manually apply them.  The catalog location for the Orchestrator UR2 update is:  http://catalog.update.microsoft.com/v7/site/Search.aspx?q=2828193

image

 

The manual application is simple – download the CAB files, extract the MSP files, and then copy them to all your RunBook Servers, and any machine with the RunBook Designer installed.  These MSP’s need to be applied via an *elevated* command prompt:

image

No success feedback is given.  Check your application event log or do a quick file spot check:

image

 

 

App Controller 2012 SP1:

 

The simplest way to apply these updates to an App Controller server would be using Windows Update, which can be controlled via WSUS or ConfigMgr since these are on the catalog. 

 

image

 

Alternatively, you can download these and manually apply them.  The catalog location for the App Controller UR2 update is:  http://catalog.update.microsoft.com/v7/site/Search.aspx?q=2815569

image

 

The manual application is simple – download the CAB files, extract the MSP files, and then copy them to all your App Controller Server.  These MSP’s need to be applied via an *elevated* command prompt:

image

 

No success feedback is given.  Check your application event log or do a quick file spot check:

image

 

 

 

 

Service Manager 2012 SP1:

The UR2 updates for Service Manager 2012 SP1 are not part of Windows Update.  These are a separate download available here:

http://www.microsoft.com/en-us/download/details.aspx?id=38409

There are two files, one is x64 and the other x86.  The x86 update would only be deployed if you were running 32 bit consoles somewhere, as the servers themselves are only 64bit.

I copy the x64 update file down to my SCSM Management server, and my Data Warehouse Management server.  I will execute the update from an *elevated* command prompt:

image

This kicks off a self-extracting update with a UI.  Agree to the license agreement and click “Install”

image

This will go through several steps, installing files, stopping and starting the SCSM services, configuring the database, then finalization.  When complete, you will see a final dialogue:

 

image

 

You can do a quick file spot check to verify:

image

When complete – I move on to my Data Warehouse Management Server, and repeat.

Lastly – I need to update any consoles I have deployed on user desktops or terminal servers in my environment.

 

Virtual Machine Manager 2012 SP1:

There is a known issue with VMM 2012 SP1 UR1 to UR2 update.  If you have NOT applied UR1 to VMM 2012 SP1, then simply install UR2.  If you HAVE applied UR1 and are running VMM 2012 SP1 UR1 – you must FIRST uninstall UR1 in order to install UR2.  This is covered in the KB article:  http://support.microsoft.com/kb/2802159

 

To install Update Rollup 2 for Virtual Machine Manager, you have to uninstall Update Rollup 1 for Virtual Machine Manager from your system.

  • If you download Update Rollup 2 for Virtual Machine Manager from Microsoft Update Catalog and install Update Rollup 2 without uninstalling Update Rollup 1, you should uninstall Update Rollup 2 for Virtual Machine Manager and then uninstall Update Rollup 1 for Virtual Machine Manager by using the Programs and Features item in Control Panel.
  • If you use Windows Server Update Services (WSUS) to update Virtual Machine Manager and you have already installed Update Rollup 1 for Virtual Machine Manager, then you will not receive the Update Rollup 2 notification until Update Rollup 1 is uninstalled.

When Update Rollup 2 is applied to a system that is running Virtual Machine Manager with Update Rollup 1 installed, the installer does not update files correctly. This issue is caused by the way Update Rollup 1 was packaged. The fixes in Update Rollup 1 are correct. It is the packaging of Update Rollup 1 that causes this issue. If you do not have to have Update Rollup 2, then you should continue to operate with Update Rollup 1. However, if you choose not to install Update Rollup 2 and a later update rollup is released that you have to implement, you will still have to remove Update Rollup 1 first before you install a later update rollup.
We apologize for any inconvenience this causes your organization. We have performed cause analysis on the issue and have established processes to prevent future recurrences of this situation.
Comments
  • Hi Kevin,

    With Service Manager UR2, does it apply to the web portal server as well? I tried to run it on the web portal server and it installed successful.

    Thanks

    Tao

  • I constantly get the error "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 a different version of the program. Verify that the program to be upgraded exists on your computer and that you have the correct version." I am on Windows Server 2012 R2 and Systems Center 2012 R2. Same error on Orchestrator 2012 R2. I did run it with elevated command prompt.

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment
Search Blogs