Please note this update released after RU 5
Microsoft has release Update Rollup 5 for System Center 2012 R2 Virtual Machine Manager Description of the security update for Update Rollup 5 for System Center 2012 R2 Virtual Machine Manager
If you manually download the update packages from the Microsoft Update Catalog and install them by double-clicking the packages, you have to install the Virtual Machine Manager Server package as an elevated user.
You can install the Virtual Machine Manager Administrator Console package by double-clicking the package as a non-elevated user.
If you also have the Administrator Console installed on the VMM server, install the updates in the following order:
- Update Rollup 5 for Virtual Machine Manager Server
- Update Rollup 5 for the Administrator Console
Between these two installations, Virtual Machine Manager Server might create a critical error log under the VMMLogs directory. This issue occurs because the Administrator Console shares some DLLs with Virtual Machine Manager Server, and a version conflict could lead to the logging of the critical failure. To resolve this issue, install both updates on the Virtual Machine Manager Server that you use to start the Virtual Machine Manager Service.
Let’s take a look on how we identify the versions installed.
First the administrative console, you can see the current version by selecting about in the console:
After the RU4 update for the console has been installed you should see version 3.2.7895.0:
Before updating my console showed version 3.2.7768.0 for CU4:
You can also see the installed update by looking in installed Updates with RU5 you should see
Update Rollup5 for Microsoft System Center Virtual Machine Manager Administrator Console (x**) (KB3023914):
You can find the current version for the VMM server by right clicking the server in the console and selection Properties:
After updating the server with RU4 you should see version 3.2.7895.0:
Before I updated my server, the version was 3.2.7768.0 for RU4:
The Server update is also visible in installed Updates, when RU4 is installed you should see
Update Rollup 5 for Microsoft System Center Virtual Manager Server (x64) (KB3023195):
The VMM agent version on your Hyper-V servers can be found by right clicking the Hyper-V server and select Properties.
If you have chosen to display the column Agent version you can see it directly on the host (Blue box):
After the VMM agent has been updated to RU5 you should see version 3.2.7895.0:
Before I updated the VMM Agent it showed 3.2.7768.0 for RU4:
You can use the Update Agent command to update your Hyper-V hosts:
The VMM Agent version can also be found in Programs and Features on the Hyper-V host, after update you should see version 3.2.7895.0:
And finally we should check the installation of Microsoft System Center Virtual Machine manager DHCP Server (x64) on the Hyper-V hosts, we can do this by a PowerShell command:
Get-WmiObject -Class win32_product -Filter ‘Name = “Microsoft System Center Virtual Machine Manager DHCP Server (x64)”‘
You can also here find the same information in Programs and Features on the Hyper-V host:
The MSI file for installing the updated version of the System Center Virtual Machine Manager DHCP Server (x64) component can be found on your VMM server after updating the server to RU4
C:Program FilesMicrosoft System Center 2012 R2Virtual Machine ManagerSwExtn (depending on were you installed VMM but this is default):
But RU5 doesn’t seem to include an updated version of Microsoft System Center Virtual Machine manager DHCP Server (x64) and according to the documentation you should no longer need this manual update:
Currently, users have to manually update the DHCP extension after update rollup installation on all hosts. This is now automated. After the DHCP extension is replaced in the Virtual Machine Manager server’s installation folder to the latest version, Virtual Machine Manager automatically checks the DHCP extension against all hosts. If the host has an older version of DHCP extensions, the agent version status will be displayed as “DHCP extension needs to be updated in host properties on the Status page.” The user calls the update agent and updates the DHCP extension on the Hyper-V host in the same way that the user did this for the Virtual Machine Manager agent. Also, if the VSwitch is a logical switch, the status will be shown in “logical switch compliance.” The user can remediate the logical switch. This will also update the DHCP extension on the host.