VMM Version Numbers

To identify the version of VMM you are running find the about information as per the screenshot below:

vmm

This will pull up version information including Service Pack and Version number:

vmm2

The Version number can be converted to a KB article (Update Rollup) by using this site: List of Build Numbers for System Center Virtual Machine Manager (VMM)

 

2008 R2 SP1

 

Build Number Knowledge Base Article ID Comment
2.0.4276.0 n/a System Center Virtual Machine Manager 2008 R2 Service Pack 1 RTM
2.0.4571.0 2562466 Update Rollup 1 for System Center Virtual Machine Manager 2008 R2 Service Pack 1
2.0.4600.0 2691812 Update Rollup 2 for System Center Virtual Machine Manager 2008 R2 Service Pack 1

 


2012

 

Build Number Knowledge Base Article ID Comment
3.0.5007.0 n/a System Center 2012 Virtual Machine Manager RC
3.0.6005.0  n/a System Center 2012 Virtual Machine Manager RTM
3.0.6019.0 2686249 Update Rollup 1 for System Center 2012 Virtual Machine Manager
3.0.6040.0 2706783 Update Rollup 2 for System Center 2012 Virtual Machine Manager
3.0.6055.0 2785681 Update Rollup 4 for System Center 2012 Virtual Machine Manager
3.0.6057.0 2822776 Update Rollup 5 for System Center 2012 Virtual Machine Manager
3.0.6060.0  2861038 Update Rollup 6 for System Center 2012 Virtual Machine Manager
3.0.6062.0 2888943 Update Rollup 7 for System Center 2012 Virtual Machine Manager

 

2012 SP1

 

Build Number Knowledge Base Article ID  Release Date Comment
3.1.1042.0 n/a System Center 2012 Virtual Machine Manager Service Pack 1 CTP1
3.1.3010.0 n/a System Center 2012 Virtual Machine Manager Service Pack 1 CTP2
3.1.3612.0 n/a System Center 2012 Virtual Machine Manager Service Pack 1 Beta
3.1.5016.0 n/a System Center 2012 Virtual Machine Manager Service Pack 1 RC
3.1.6011.0 n/a System Center 2012 Virtual Machine Manager Service Pack 1 RTM
3.1.6018.0 2785682 Update Rollup 1 for System Center 2012 Virtual Machine Manager Service Pack 1
3.1.6020.0 2802159 Update Rollup 2 for System Center 2012 Virtual Machine Manager Service Pack 1
3.1.6027.0 2836751 Update Rollup 3 for System Center 2012 Virtual Machine Manager Service Pack 1
3.1.6032.0 2879276 Update Rollup 4 for System Center 2012 Virtual Machine Manager Service Pack 1
3.1.6038.0  2904727  Update Rollup 5 for System Center 2012 Virtual Machine Manager Service Pack 1
3.1.6046.0 2932860 Update Rollup 6 for System Center 2012 Virtual Machine Manager Service Pack 1
3.1.6084.0 2965089  2014-07-29 Update Rollup 7 for System Center 2012 Virtual Machine Manager Service Pack 1

2012 R2

 

Build Number Knowledge Base Article ID Comment
3.1.7200.0 n/a System Center 2012 R2 Virtual Machine Manager Preview
3.2.7510.0  n/a System Center 2012 R2 Virtual Machine Manager RTM
3.2.7620.0 2904712 Update Rollup 1 for System Center 2012 R2 Virtual Machine Manager
3.2.7634.0 2932926 Update Rollup 2 for System Center 2012 R2 Virtual Machine Manager
3.2.7672.0 2965414  Update rollup 3 for System Center 2012 R2 Virtual Machine Manager
3.2.7768.0 2992024 Update Rollup 4 for System Center 2012 R2 Virtual Machine Manager
3.2.7828.0 3011473 Update Rollup 5 Preview for System Center 2012 R2 Virtual Machine Manager
Advertisements

SCVMM 2012 SP1 – Bare Metal Build Error 803d0008 A quota was exceeded

During a VMM bare-metal build error 803d0008 was showing up on the host console. The error occurred when the Host was attempting to send the discovered data back to the VMM server.

error2

The logs showed the following:

error1

 

Right at the bottom the error that stood out was “The numbers of bytes written exceeded the specified quota of 65536 bytes)

It looked as if there was perhaps to much information discovered and VMM was not able to deal with additional data over the 65536 byte limit.

This was a rebuild of an existing host, I had recently performed bare-metal builds successfully the day before.

The host happened to have a large number of LUNs presented to it from the SAN (23 to be exact).

The solution for me was to un-present the LUNs.

 

SCVMM 2012 & r2

I noticed a client was getting these errors when live migrating VMs between cluster nodes:
Error 23801 “No available connection to the selected VM Network can be found”
Error 23811 “Ports are not available for VM Subnet”
These errors would occur despite there being a VM Network available on both nodes. The Live migration would work, but these errors were frustrating.

This can occur when there are additional NICs on the host that have the “Available for Placement” box selected, even if those NICs are disabled. The solution is to untick this box for each host.

Live Migrations Fail between SCVMM 2012 SP1 hosts

While performing some cleanups for a client I noticed a problem where certain live migrations were failing.

I knew I had been performing updates on various hosts to bring them in alignment. Upon closer inspection I could see that the Virtualization Software Version was changing on hosts that had been updated:

Virtualization Software Version Mismatch Clean zoom

 

In the above snip you can see the host in Maintenance mode has a different version of the virtualization software. The version field is talking about the Hyper-V version, rather than the VMM agent version.

As usual, when something fails in SCVMM often the next step is to try it in failover cluster manager, results below:

FailoverClusteringMigrationError

Unfortunately because I had been updating the hosts while they had running VMs on them (and then placing them into maintenance mode once they were ready to reboot) I was left with one host that would not allow live migrations.

The solution?

I had to use Quick Migration to move the VM’s, while this is not technically live, it was quick enough to get the job done.

Lessons learned? Place servers into maintenance mode before you start patching! and keep all your hosts at the same level.

 

Also it is worth pointing out that there have been some particularly damaging patches released by MS recently, rather than explain it myself I will point you to Aidan Finn’s blog where he talks about the problematic patches.