Update Rollup 10 for System Center 2012 R2 Virtual Machine Manager

Features that are added in this update rollup

Support for using VMM Hardware Profile Properties in Windows Azure Pack

• A new HWProfileId parameter is added to the Set-CloudVMRoleSizeProfile cmdlet to link the VMM Hardware Profile to the VMRoleSizeProfile cmdlet.
  
  Example cmdlet:
  
  Set-CloudVMRoleSizeProfile -VMRoleSizeProfile CloudVmRoleSizeProfile -HWProfileID HWProfileID
  
  
  Note The HWProfileId parameter cannot be specified during an Add operation. It can only be linked to an existing CloudVMRoleSizeProfile cmdlet.
  
  
• You can use the Get-CloudVMRoleSizeProfile cmdlet to obtain the HWProfileId parameter.

• SecureBootEnabled
• LimitCPUForMigration
• MemoryWeight
• CPUReserve
• HAVMPriority
• RelativeWeight (Priority)
• LimitCPUFunctionality
• ExpectedCPUUtilization
• NetworkUtilization
• DiskIO
• CPUType
• CPUMax
• NumaIsolationRequired
• CPUPerVirtualNumaNodeMaximum
• MemoryPerVirtualNumaNodeMaximumMB
• VirtualNumaNodesPerSocketMaximum
• CPUCount (Cores)
• Memory (related settings)
• DynamicMemoryEnabled
• DynamicMemoryMaximumMB
• DynamicMemoryBufferPercentage
• DynamicMemoryMinimumMB

Issues that are fixed in this update rollup

• When you try to change a service template that has a load balancer and a configurable VM network, the changes are not saved. Additionally, the Save dialog box may reappear.
  
  Note This issue occurs when you change the VM Network from an existing configurable setting to a different configurable setting.
  
  
• When you try to edit or view a service template that has a load balancer and a VM network in Designer view, one or more VM Networks that you had added previously disappear.
  
  
• When you try to perform Remediation on Hyper-V cluster nodes or put the nodes into maintenance mode, VMM occasionally cannot update the Hyper-V Network Virtualization (HNV) Policy on the Hyper-V cluster nodes. When this failure occurs, the affected Hyper-V hosts stay in the failed state permanently or until the System Center Virtual Machine Manager service is restarted. Typically, this issue affects only the nodes that exit Maintenance mode. The other nodes in the cluster continue to work as expected.
  
  The issue is fixed in this update rollup. However, to temporarily work around this issue, restart the System Center Virtual Machine Manager service, and then update all the VMs on the affected nodes after the nodes are in a failed state. This is the only known method to update the HNV policy and to make sure that the hosts obtain a Provider Address (PA).
  
  
• When a service is serviced, the Guest Agent fails and returns the following error message:
  
  Error (22758)
  The guest agent encountered an exception while running a script command. Win32ErrorCode: 2147942402 DetailedErrorMessage: The system cannot find the file specified.
  
  
• When you, as a tenant, try to deploy a VM or a VM Role by using a differencing disk through WAP, the VM or VM Role fails and generates disk quota errors. This issue may occur even though there is enough quota remaining. This issue occurs because of inconsistent usage calculations done by VMM for base and differencing disk scenarios. When this issue occurs, you receive one of the following error messages:
  
  
  • Error (23419)
    The operation results in a violation of the disk space quota for cloud * for the user role *.
    
    Recommended Action
    Ensure sufficient disk space quota for the user role specified and try the operation again. Please contact your system administrator with this error ID.
  • Error (22042)
    The service <name> was not successfully deployed. Review the event log to determine the cause and corrective actions.
    
    Recommended Action
    The deployment can be restarted by retrying the job.
  • Error (31304)
    VM Role resource <name> was not successfully deployed in the Cloud Service.
    
    Recommended Action
    VM Role can be repaired if the entity was created.
  For example, assume that you have three VM roles deployed by assigning every role to a 60-gigabyte (GB) operating system disk. The VM Role use Differencing Disks for the operating system disk, and the parent or base disk is a 60-GB hard disk.
  
  VM Role 01: Parent: 60 GB, Child: 43 GB
  VM Role 02: Parent: 60 GB, Child: 42 GB
  VM Role 03: Parent: 60 GB, Child: 42 GB
  
  
  When VMM tries to calculate the disk usage, it incorrectly adds the size of the base disk three times (instead of just one time) to obtain the current usage:
  
  
  3x60GB (180GB) + 43+42+42 (127GB) = 307 GB
  
  Ideally, the base disk should have been considered only one time (60+43+42+42 = 187GB). Therefore, if the tenant has a quota that is set to 300 GB, for example, deployments of new VMs and VM Roles fail and generate a quota violation.
  
  
• When you have two replication groups that have the same name on a storage array, and you try to refresh or rescan the array by using VMM, you receive the following exception:
  
  Error (20413)
  VMM encountered a critical exception and created an exception report at C:\ProgramData\VMMLogs\SCMM.guid\report.txt.
  
  Recommended Action
  See the report for more details and search user forums for well-known root causes for self-help.
  
  The handling of the exception is improved in this update. The refresh or rescan job now fails, and you receive the following error message to help you resolve the issue:
  
  Error (24403)
  Unable to import replication group "%Name;". VMM does not support more than one replication group with the same name.
  
  Recommended Action
  Remove the duplicate replication group and try the operation again.
  
  
  
• When you create a Gen 2 VM by using VMM, the VM creation fails, and you receive the following error message:
  
  Error (13206)
  Virtual Machine Manager cannot locate the boot or system volume on virtual machine <name>. The resulting virtual machine might not start or operate properly.
  
  
  
• When you add a VM template that is configured to use the AutoLogonCredential parameter to a WAP plan, the plan goes into an Active (Out of Sync) state. This state continues until the VM template is removed or manual permissions are granted in the VMM Console to enable the tenants user role to access the specified Run As Account. WAP cannot sync a plan if the plan includes a VM template that has the AutoLogonCredential parameter added. Also, running the Get-SCVMtemplate -ID <ID cmdlet does not return the VM template if the VM template has AutoLogon enabled and AutoLogonCredential added.

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 10. 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 having the program point to the retained database.
     
     Note The installation finishes but the VMM service might 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 update rollup on the new node, you may 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 10. 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

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

Download information

Microsoft Update

1. Click Start, and then click Control Panel.
2. In Control Panel, double-click Windows Update.
3. In the Windows Update window, click Check Online for updates from Microsoft Update.
4. Click Important updates are available.
5. Select the update rollup package, and then click OK.
6. Click Install updates to install the update package.

Manual download

Download the VMM Server update package now.

Download the Administrator Console update package now.

Download the Guest Agent update package now.

Files updated in this update rollup