Update Rollup 1 for Virtual Machine Manager 2012 R2 was just released.
There are some annoyances that are fixed in here, so I know lots of folks that will be installing this.
However, one warning – take note of the release notes:
http://support.microsoft.com/kb/2904712
There is a SQL script in there that you must run on your VMM database as a step in the process of applying the Update Rollup.
I anticipate that many folks will get caught by this one, it is just as slick at the error for UR1 of SCVMM 2012 SP1 where it had to be manually uninstalled or else UR2 or later would not apply properly (but it would look like they do).
Considering that SCVMM pushes SQL DAC packs to database servers to build out Services, I am actually really surprised at the need for the additional SQL script. It seems like these folks should know how to do this without requiring that extra step that can so easily be missed – especially by shops that no longer take the time to read the release notes for each and every update.
So, be aware and get that script.
[update 1/30/14]
My SCVMM Server automatically updated via Windows Update two days ago.
How did I find out? I tried to deploy a VM from a Service Template and it failed with the error detail that the Host Agent on the target hypervisor was out of date.
Nothing else.
So, I then turned around and ran the SQL script on the VMM 2012 R2 database.
I had no time to learn what the symptom might be from not applying the SQL script. There has to be one. Some way to know.
