Update Rollup 2 (UR2) for Virtual Machine Manager 2012 SP1 require some extra attention

Microsoft released UR2 for System Center 2012Sp1 a while and as you know you can download the updates rollups from the Microsoft Update Catalog, or you can configure WSUS/SCCM to handle the update.

Usually the process to update the components is very easy but it appears that the previous update (UR1) for SCVMM2012SP1 component has a issue that blocks a “normal” update with UR2.

Below is the statement from the System Center team or you can read the whole blog post:

Important actions for Update Rollup 2 for System Center 2012 SP1- Virtual Machine Manager

In order to install Update Rollup 2 package for System Center 2012 SP1-  Virtual Machine Manager, you will need to uninstall Update Rollup 1 for System Center SP1 – Virtual Machine Manager package from your system. 

- If you download Update Rollup 2 package for System Center 2012 SP1 Virtual Machine Manager from Microsoft Update Catalog and install Update Rollup 2 without un-installing Update Rollup 1  you should un-install Update Rollup 2 package for Virtual Machine Manager and then un-install Update Rollup 1 for System Center 2012 SP1 – Virtual Machine Manager via control panel. 

- If you are using WSUS to update System Center 2012 SP1 – Virtual Machine Manager and you have already installed Update Rollup 1 for System Center 2012 SP1 – Virtual Machine Manager then you will not receive Update Rollup 2 notification until Update Rollup 1 is uninstalled.

Why is this necessary?

When Update Rollup 2 is applied to a system which is running System Center 2012 SP1 Virtual Machine Manager with UR1, the installer does not patch files correctly. This is caused by the way UR 1 was packaged. As such the product fixes in UR1 are correct; it is the packaging of UR1 that causes this issue. If you do not need UR2, then you should continue to operate with UR1.   However, if you choose to stay on Update Rollup 1 for System Center 2012 SP1 Virtual Machine Manager and a later Update Rollup is released that you need to implement you will still need to remove Update Rollup 1 first.

We apologize for any inconvenience this causes your organization.  We have performed root cause analysis on the issue and have processes in place to prevent future recurrences of this situation. 

Microsoft Virtual Machine Converter

If you haven’t heard, Microsoft is developing a new tool that provides a Microsoft-supported, freely available, stand-alone solution for converting VMware virtual machines and disks to Hyper-V-based virtual machines and virtual hard drives (VHDs). The tool is not released yet but you can download and test the RC version.

More information about the tool

Download the Microsoft Virtual Machine Converter (MVMC)

System Center Virtual Machine Manager Beta 2 Released (SCVMM)

Today Microsoft released the updated beta version of Virtual Machine Manager (beta 2). As they promised, there is a lot of new functionality, here is some of the new features:

 

  • Completely new, easy-to-use and intuitive UI based on the System Center look-and-feel (same as System Center Operations Manager 2007, Service Desk and System Center Essentials)
  • Physical-to-Virtual (P2V) Conversions (Windows Server® 2000 or Windows Server 2003 are supported)
  • Virtual-to-Virtual (V2V) Conversions – Using the Windows PowerShell® interface, converts a VMWare disk or a whole VM to the analogous VS vhd\vm representation
  • 64-bit VMM server support
  • Every VMM component is now remotely installable, including the VMM server, library server, delegated provisioning portal, administrative console and data store
  • Full Windows PowerShell support with documentation – automate away!
  • Better overall performance and scalability

 

You can download the SCVMM Beta 2 from Microsoft Connect