System Centre 2012 SP1 Rollup 2 for VMM


Microsoft released Update Rollup 2 for System Centre 2012 SP1 a few weeks back but with this release there was one missing component – VMM. Last week Microsoft updated RU2 to include the fixes for VMM 2012 (under the KBs KB2826405 & KB2826392).

It is worth noting that you MUST uninstall VMM RU1 before you install this RU2 release, this is due to a problem with the original Update Roll up 1 and the way the files were packaged.

If you download RU2 from the Microsoft update catalogue and have already manually installed it, you must uninstall RU2 then uninstall RU1 and reinstall RU2 again. If you use WSUS for your updating you won’t receive RU2 until you have manually uninstalled RU1.

Microsoft has released an apology for all this installing and uninstalling you have to do:

‘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.’

The updated fix and list of updates are available here >>

Error (0x0107, 0x0000) when trying to view a VM Console

I wanted to create a quick post about this just in case anyone else  ever has a  (0x0107, 0x0000) message when trying to view a VMs console session using VMM 2012.


This happens when you have a untrusted Hyper-V host in VMM 2012 such as a machine sitting in your DMZ (perimeter host). You will be able to see the Hyper-V host, the VMs and manage the VM properties but not connect to the console.  When you try to connect to the VM you will be asked to authenticate against the host and then you will see a warning about an un trusted certificate and once you click OK you will receive the (0x0107, 0x0000) message.


To resolve this issue you need to import the certificate from the Hyper-V host onto the machine where you are running the VMM console.

Logon to your Hyper-V Server and create a new MMC Console. Select the Certificates Snap-In to add use the ‘Services Account’


Locate the ‘Windows Remote Management (WS-Management)’ service account and complete the wizard with the rest of the defaults.



If like me your Hyper-V host is running Windows Serer Core mode instead of using certutil.exe you can use a snap-in on another machine (you will be asked to authenticate against) to remotely manage your certificates.

Once you have the console setup you need to find your server certificate which will be located under ‘WinRM\Trusted Root Certificate Authorities’. Right click on the certificate and follow the export wizard.


On your VMM console machine you need to import the certificate you have just exported into the ‘Trusted Root Certificate Authorities’ of the computer account.


You should now be able to connect to the console of the VM. You will still need to enter your authentication details but you won’t be presented with the certificate warning.

SCVMM 2012 Pre-Requisites

There are a few pre-requisites before you are able to perform an in place upgrade to SCVMM 2012, these include:

Software Requirements

  • You must be running SCVMM 2008 R2 SP1 (upgrading without the service pack is not supported!)
  • You must be running Windows Server 2008 R2 for the VMM Management Server. This has to be the full GUI version (i.e. not core). Standard, Enterprise and Datacentre are all supported. Note there is currently no support for running SCVMM 2012 on Windows Server 2012 (Server ‘8’ Beta) I’m sure this will come soon.
  • The server must be a member of a domain and the computer account cannot exceed 15 characters. Also worth noting you cannot use the string ‘-SCVMM-‘ in the computer name but you can use ‘SCVMM’.
  • For your SQL server VMM 2012 does NOT support Express versions of SQL. The only supported SQL server versions are:
    • SQL Server 2008 R2 Datacentre (64-bit)
    • SQL Server 2008 R2 Enterprise (64-bit)
    • SQL Server 2008 R2 Standard (64-bit)
    • SQL Server 2008 Enterprise (64-bit)
    • SQL Server 2008 Standard (64-bit)
    • Notice the current lack of SQL Server 2012 support – I’m sure this will come soon.
    • A few other SQL requirements are:
      • You MUST use a case-insensitive instance of SQL server
      • The computer name must not exceed 15 characters.
      • Microsoft also highly recommends you install the SQL Server 2008 R2 Command Line Utilities – although they are not strictly a pre-requisite.
  • You must uninstall any previous versions of the Windows Automated Installation Kit (WAIK) and install the latest Windows 7 version.
  • You need the latest .NET 3.5.1 (this is included in SQL Server 2008 R2 and the VMM 2012 installer will enable it automatically if it’s not already.
  • Windows Remote Management (WinRM 2.0) this should be started it is set to automatic start-delayed on Windows Server 2008 R2 anyway. If is not started you will see an error during the pre-requisites check.

Hardware Requirements:

Less   than 150 hosts

More   than150 hosts






Pentium 4 – 2GHz (x64)

Duel Core – 2.8 GHz (x64) +

Duel Core – 2.8 GHz (x64) +

Duel Core – 3.6 GHz (x64) +






HDD (Without DB)





HDD (With local SQL DB)



Recommended the VMM management server   is on a dedicated server

If you are making VMM Management server highly   available it is recommended to use a separate highly available SQL server.

* If you are running the library server on the server more disk space will be required. Although it is recommended you run the library on highly available file server.


Other things to note:

  • Hosts running Microsoft Virtual Server 2005 R2 are no longer supported – I presume Microsoft is trying to push people into moving to Hyper-V!
  • Not all versions of ESX & VMWare vCenter Server are now supported, you must be running one of these versions:
    • VMWare vCenter Server 4.1
    • ESXi 4.1 & ESX 4.1
    • ESXi 3.5 & ESX 3.5

If you upgrade with VMWare hosts (and VMWare VMs) that are not supported they will automatically be removed from the VMM database.

  • Performance & Resource Optimization (PRO)
    • PRO configurations will not be maintained during the upgrade process. This is because during the install the connection to Operations Manager will be removed and you will need to manually recreate it after the upgrade is complete.
  • Library Server
    • SCVMM 2012 does not support a library server being hosted on a Windows Server 2003 server you will need t. migrate these to another server (or upgrade from 2003) before you upgrade. If you continue with a 2003 library server they only thing you will be able to do in the VMM 2012 console is to remove it.
  • Service Accounts
    • Microsoft recommends that you store encryption keys for VMM2012 in AD DS (Distributed Key Management) this is a requirement if you are going to be making your VMM Management server highly available. This is a change in 2012 as Distributed Key Management was not available in VMM 2008 R2.

Using Distributed Key Management is also an advantage if you ever have to re-install VMM 2012 on a different computer in the future. In VMM 2008 (R2) you would not be able to preserve encrypted data as the keys are local to the server. This is also true if you are installing VMM 2012 on a different computer (and not doing an in-place upgrade)

  • For the service account you can either use the local system account or a domain user account – again if you are making this highly available you have to use a domain user account.

During the upgrade process:

If the VMM 2012 installer detects a problem during the install it will automatically roll back and you will be left with your original VMM 2008 R2 SP1 configuration.

Post upgrade:

Some of the service names have changed in VMM 2012 so if you have any service monitoring you will need to update it with the new names. The changes are:

Version Display Name Service Name
VMM 2008 R2 SP1 Virtual   Machine Manager VMMService
Virtual   Machine Management Agent VMMAgent
VMM 2012 System   Center Virtual Machine Manager SCVMMService
System   Center Virtual Machine Manager Agent SCVMMAgent

Once all that is in place you are ready to proceed with the install!! This is where it gets exciting!