The following is the results of my lab environment’s upgrade from Virtual Machine Manager 2012 SP1 to Virtual Machine Manager 2012 R2. Please pardon any typos and the lack of polish on this blog post – my goal is to get the information out quickly based upon what I’ve seen so far.

The first step was to acquire the ISO which is shown below from my file share. It’s 1.24 GB in size, and is labeled as “mu_system_center_2012_r2_virtual_machine_manager_x86_and_x64_dvd_2913737.iso”.

image

The VMM 2012 R2 installation screen is shown below:

image

During the attempted upgrade it was apparent there is no upgrade option (also backed up by looks http://www.systemcentercentral.com/some-tips-on-upgrading-system-center-2012-sp1-to-r2-preview/) …

image 

VMM also does not support in-place upgrade. You have to uninstall VMM and retain the database. (remove the existing VMM components through control panel/add remove programs).

image

Retain the database as you will want that later during the re-installation with VMM 2012 R2.

image

Successful component removal is shown below.

image

On the getting started screen provide the name, organization and product key.

image

You next need to accept the license agreement.

image 

Next choose either to or not to participate in the CEIP.

image

And either accept the default path or change it to the path that you prefer for your environment.

image

There is a pre-requisite to download and install the Windows Assessment and Deployment Kit which causes a critical failure.

image

When I attempted to download and deploy the missing prerequisite it reminded me that this was already installed and needed to be uninstalled first.

image

Back to the control panel add/remove programs and uninstall the existing deployment kit.

image

image

Install after removing the older version the new version can be installed as shown below.

image

image

image 

image

This took a while to complete (longer than most of the rest of the VMM installation process), but the completion is shown below.

image

Now it’s back to the VMM installation now that the one missing pre-requisite has been dealt with.

image

So, it’s time to reboot! After reboot and re-run the installation. It reminded me that I should have more memory by this system has dynamic memory configured to go beyond the four GB level so I continued past this warning.

image

Go find the database that you had before the installation of 2012 R2 (the default name for the database name would be "VirtualManagerDB”).

image

And it lets me know that this database is from an older version and asks me to upgrade it!

image

Next I needed to configure the service account and distributed key management.

image

And specify which library server to use (I retained my existing one as shown below).

image

The installation generated an upgrade compatibility report warning me of potential issues. So I’ll need to re-attach to my Operations Manager environment and check the upgrade documentation at http://go.microsoft.com/fwlink/?LinkdID=214130.

image

The installation summary is shown below.

image

Upon clicking installation the start of the re-installation began as shown below.

image

Successful completion is shown below.

image 

And here we go!

image

The upgrade was successful, as evidenced by the new Generation 1 and Generation 2 options shown below!

image

And my existing hosts continued to report correctly into VMM.

image

Summary: There does not appear to be an upgrade for VMM 2012 SP1 to VMM 2012 R2. The migration required uninstalling VMM 2012 SP1 (retaining the database) and installing VMM 2012 R2 which successfully upgraded the database. Overall this was pretty painless and I’m interested in seeing what new features are available here (and preparing to upgrade my hosts to Windows 2012 R2!)