This article describes the issues that are fixed in Update Rollup 5 for Microsoft System Center 2012 Virtual Machine Manager Service Pack 1 (SP1). Additionally, this article contains the installation instructions for Update Rollup 5 for System Center 2012 Virtual Machine Manager SP1.
Issues that are fixed in this update rollup
A configuration error occurs if Virtual Machine Manager (VMM) is configured to use a dynamic disk as the virtual machine pass-through disk.
During a virtual machine live storage migration, the connection for the virtual machine is invalid if the network switch on the destination host is changed.
Virtual hard disk (*.vhdx) files are not found on an NAS library share.
An exception error at Engine_Adhc_Operations!Microsoft.VirtualManager.Engine.Adhc.HostRefresher.GatherVirtualNetworkInformation occurs, and the SCVMM service crashes, if the SCVMM service is disabled on a teamed network adapter.
VMM Server crashes if the “Create VM template from VM” job is canceled and then restarted.
The VMM console does not show the details of an uplink profile when the uplink profile is added to a logical switch. This issue occurs if the name of the uplink profile contains the following string:
When an NAS provider is discovered, the credentials do not include the domain name.
Cloud associations for virtual machines are randomly lost in VMM.
Virtual machines in VMware that are connected by using a Cisco N1000V dvSwitch are not available in VMM. Therefore, you cannot manage the virtual machine in VMM.
The following error is generated when data is updated:”System.Data.SqlClient.SqlException (0x80131904): The server principal “” is not able to access the database “DBA” under the current security context.”
For more Info., you can check below link