scvmm

Tips for installing System Center Virtual Machine Manager 2012 R2 Update Rollup (UR5)

Here are some tips for installing System Center 2012 R2 Virtual Machine Manager Update Rollup (UR5):

      • UR5 is available from Microsoft Update or by manual download. If you are not installing UR5 through Microsoft Update (e.g. you’re downloading the update and then installing it), you must install using elevated privileges. If you do not do this the update may fail silently.
      • During the UR5 installion the System Center Virtual Machine Manager & Agent will be stopped
      • 3
      • After the SCVMM UR5 server component, reboot the VMM server before installing the UR5 console
      • Before Update Rollup 5, you had to manually update the System Center Virtual Machine Manager DHCP Server (x64) component. As of Update Rollup 5, this is no longer required. When updating the agent on the server the DHCP server components is updated too.
      • Agents DHCP
      • The new SCVMM UR5 agent build version is: 3.2.7895.0
      • The Microsoft System Center Virtual Machine Manager DHCP Server (x64) build version is still 3.2.7768.0
      • Make sure to update the agent on all the infrastructure servers such as the Update Server and library server. In VMM click on Fabric- Server for a complete overview
      • Updateagent
      • Refresh the cluster after updating the agents
      • When starting the VMM console the following error appears:
      • pipeline error
      • This error is permission related. To solve this error add the “Authenticated Users” group to the AddInPipeline directory and assign read and execute rights. The installation of VMM can be found under: <Driveletter>:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\bin\AddInPipeline.
      • Update 24-02-2015: Microsoft released a hotfix for UR5 that addresses replica and smb shares issues. The link to the KB can be found here, link.

For all the details on SCVMM 2012 R2 UR5, see the following:

  • KB3023195 – Description of the security update for Update Rollup 5 for System Center 2012 R2 Virtual Machine Manager, link

Installing Update Rollup (UR) 3 for System Center 2012 R2 Virtual Machine Manager

Update rollup (UR) 3 for System Center 2012 R2 Virtual Machine Manager is released this week. This update includes a Linux guest agent upgrade to support the following new operating systems:

  • Ubuntu Linux 14.04 (32-bit)
  • Ubuntu Linux 14.04 (64-bit)

This update also includes the following:

  • Host DHCP extension driver upgrade
  • Several performance improvements??????
  • Several Management Pack package improvements

And a huge list of issues that are fixed. More information can be found in the Microsoft KB article found here, link.

The update can be installed by using Windows Update, WSUS or manual downloading the files and execute them. After the installation of Update rollup 3 execute the SQL Script against the SCVMM database. The SQL script is listed in the Microsoft KB. Don’t forget to update the VMM agents on all the infrastructure server.

2014-08-01_14h21_25

The update of the VMM agents doesn’t require a reboot. The Update Rollup 3 agent version is 3.2.7672.0.

Host DHCP extension driver upgrade

Update Rollup 3 includes an VMM DHCP server extension update for the Hyper-V host.  When using Hyper-V Network Virtualization networks with dynamic IP address allocation, the VM may not get an IP address for a few minutes after the reboot. The new DHCP extension fix this problem. To check the DHCP Extension driver version use the following PowerShell command on the Hyper-V host:

Get-WmiObject -Class win32_product -Filter ‘Name = “Microsoft System Center Virtual Machine Manager DHCP Server(x64)”‘

The new Microsoft System Center Virtual Machine Manager DHCP Server (x64) version is 3.2.7672.0. More information about the installation can be found here.

For more tips see my earlier blog post “Tips for deploying SCVMM 2012 R2 Rollup 2”, Link.

Remove an orphaned VM from SCVMM

During a migration of a VM from a different cluster the job failed in SCVMM.

image

The status of the VM in SCVMM Virtual Machine State is still “Starting”. 

image

In SCVMM I was unable to stop, repair or delete the VM. When looking on the Hyper-V host, the VM didn’t exist in Failover Cluster Manager or Hyper-V manager. After some troubleshooting I was able to use the following PowerShell command to remove the orphaned VM in SCVMM:

Import-Module VirtualMachineManager

Get-VM -VMMServer VMMSERVER –Name “VMNAME" | Remove-VM -Force

Replace the VMMSERVER and VMName  in the PowerShell syntax with your own names