Update Rollup 11 for System Center 2012 R2 Virtual Machine Manager

Issues that are fixed in this update rollup

• When you try to run a large scale deployment of a service instance, VMM Placement may store many VMs unevenly on a single host.
  

• Virtual Machine Manager (VMM) Administrator Console crashes on all Windows 10-based client computers that have the Anniversary Update installed.
  

• VMM removes cluster disks from a virtual machine (VM) resource group if they are accessed as mount points.
  

• The CPU Average and Memory values that are shown in the VMM Console are not calculated based on the average of the last 10 minutes. Instead, VMM just considers the latest value.
  

• When you try to create a Port ACL rule outside of VMM and do not specify a protocol, the protocol does not use "ANY" as the default protocol. When you refresh the VM on which this Port ACL rule is attached, the VM refresh fails with an error stating that the specified protocol does not exist.
  

  Error (50269)
  Invalid Protocol selected for Port ACL: '*', select TCP/UDP/ANY.
  
  Recommended Action
  Check Port ACL List applied.

  
  

• In a scenario where you have a service instance part of multiple computer tiers, you receive the following error message when you try to view the Dependent Resources for the logical networks (by clicking View Dependent Resources):
  

  An unknown error occurred while executing the PowerShell Script:
  Exception calling “Add” with “2” argument(s): “Item has already been added.
  Key in dictionary: key_in_dictionary Key being added:
  key_being_added
  
  Try the operation again. If the issue persists, contact Microsoft Help and Support.
  
  ID: 27235

  
  

• During bare metal deployment of a host, you can specify a MAC address from the VMM Static MAC pool. If you specify the MAC address as zero (00:00:00:00:00:00), it should be automatically assigned from the pool. However, in a scenario where the vNIC is configured on the management pNIC (transient NIC), specifying the vNIC MAC address as zero leads to failure of the bare metal deployment process and triggers the following error:
  

  Error (21536)
  The MAC address <MAC Address> for the transient physical management adapter does not match the MAC address 00:00:00:00:00:00 for the virtual management adapter.
  
  Recommended Action
  Fix the MAC addresses specified for the transient physical and virtual management adapters and try the operation again.

  
  Note To work around this issue, use the host pNIC MAC as the MAC address for the management vNIC.
  

• When you try to create Generation 2 VMs from VM templates, the process is unsuccessful, and you receive the following error message:
  

  Error (13206)
  Virtual Machine Manager cannot locate the boot or system volume on virtual machine <VM name>. The resulting virtual machine might not start or operate properly.

  
  Note The symptom for this issue resembles that of an issue fixed in Update Rollup 10. However, the scenarios and causes differ as follows:
  
  

  • Issue fixed in Update Rollup 10: VMM is not waiting for the volumes to be mounted, and it does not find the bootable volume.

  • Issue fixed in Update Rollup 11: Mount of volumes is completed without any issues. However, the volumes returned after mount are not bootable.

  
  
  Note The error message mentioned in this issue is caused by multiple issues (with multiple root causes), and there is one issue with the following scenario that's not yet fixed in Update Rollup 11.
  
  Scenario:
  
  If you create a Sysprep-ed VHDX by using the convert-windowsimage.ps1 script, and then you create a template by using the VHDX, you may receive this error message when you deploy a Generation 2 VM through this template.
  
  Note To work around this issue, create a VM with the VHDX without using any templates. You can then use VMM to create a template out of this VM, and you can use this template to deploy Generation 2 VMs without any issues.

Hotfix 1 for this update rollup

A hotfix is available on top of this update rollup. The hotfix adds a feature to support Windows Server 2016 as a guest OS. To learn more, see KB 3199246.

Known issues in the release version of System Center 2012 R2 Virtual Machine Manager

• The HPE Store virtual server appliance details for some hosts are missing
  
  After you expand the cluster from an 8-node cluster to a 12 or 16-node cluster, the HPE Store virtual server appliance (VSA) details for a few hosts will go missing in the Virtual Machine Manager (VMM) console. Performing a Storage Provider Refresh or Rescan does not help.
  
  Note The issue is not fixed in Update Rollup 11. To work around this issue, run the Read-SCVirtualMachine command on the affected hosts, or refresh the virtual machine from the VMM Console for the affected hosts. This makes sure that the VSA details are populated in Virtual Machine Manager.
  
  

• The VMM Guest Agent does not run on virtual machines
  
  When you try to maintain a service instance, VMM Guest Agent does not run on the virtual machines, and this causes the VMM Agent service to crash. Additionally, you receive the following error messages:
  

  Warning (22685)
  VMM failed to configure guest for one or more virtual machines in the upgrade domain 0 in the service tier <name>
  
  Recommended Action
  Inspect errors on virtual machine and then retry the operation.
  
  Error (22655)
  VMM is unable to retrieve status from computer <name>.
  
  Recommended Action
  Check if the computer is running and the VM guest agent is in a healthy state.

  
  This issue occurs because of a cryptographic exemption that's caused when the VMM guest agent tries to decrypt data (protected by DPAPI) but cannot find the key that's used for encryption.
  
  Note The issue is not fixed in Update Rollup 11. To work around this issue on the virtual machines you are trying to service, rename the "C:\\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager Guest Agent R2\bin\Settings\DownloadManagerMap.dat" file as "DownloadManagerMap.dat.old," and then restart the service.

Known issues from previous update rollups

• Reinstallation of Update Rollup 8 for System Center 2012 R2 Virtual Machine Manager or a later update
  
  The reinstallation of Update Rollup 8 or a later update rollup fails, and you receive the following error message:
  

  time:InnerException.Type: System.Data.SqlClient.SqlException, InnerException.Message: Violation of PRIMARY KEY constraint 'PK_tbl_WLC_ServiceTemplate'. Cannot insert duplicate key in object 'dbo.tbl_WLC_ServiceTemplate'. The duplicate key value is (5fddb85c-4ae5-4c8b-be83-9b2961a316dd).

  
  Note This issue is not fixed in Update Rollup 11. To successfully reinstall Update Rollup 8 or a later update rollup, follow these steps:
  
  

  1. Uninstall the product, and retain the update rollup database.

  2. Run the PreR2ReInstall script on the retained database.

  3. Install the release version of System Center 2012 R2 Virtual Machine Manager by making the program point to the retained database.
     
     Note The installation finishes, but the VMM service may not start.

  4. Install the update rollup, and then run the PostInstall script.

  5. Start the VMM service if it does not start automatically.

  
  For more information, see the following article in the Microsoft Knowledge Base:
  

  3132774 How to retain the database when you reinstall Virtual Machine Manager

• Adding a new node to a Highly Available VMM (HAVMM) Cluster
  
  When you add a new node to an HAVMM cluster and install Update Rollup 8 or a later rollup on the new node, you receive the following exception:
  

  time:InnerException.Type: System.Data.SqlClient.SqlException, InnerException.Message: Violation of PRIMARY KEY constraint 'PK_tbl_WLC_ServiceTemplate'. Cannot insert duplicate key in object 'dbo.tbl_WLC_ServiceTemplate'. The duplicate key value is (5fddb85c-4ae5-4c8b-be83-9b2961a316dd).

  
  This issue is not fixed in Update Rollup 11. To fix this exception, follow these steps:
  
  

  1. Add the second node to the cluster.

  2. Stop the System Center Virtual Machine Manager service on the node where VMM is installed.

  3. Run the PreR2ReInstall script on the database.

  4. Install the release version of System Center 2012 R2 Virtual Machine Manager on the second node, pointing to the existing database.

  5. Install the update rollup on the second node, and then run the PostInstall script.

  6. Start the VMM service on the active node.

  
  
  For more information, see the following article in the Microsoft Knowledge Base:
  

  3132774 How to retain the database when you reinstall Virtual Machine Manage

For information about how to download Microsoft support files, click the following article number to view the article in the Microsoft Knowledge Base:

119591 How to obtain Microsoft support files from online services Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help prevent any unauthorized changes to the file.

How to obtain and install Update Rollup 11 for System Center 2012 R2 Virtual Machine Manager