As mentioned on the last post, We have Rollup 3 for System Center 2012 SP1.
Lot many issues got fixed specific to SCVMM. Here is the list of issues which got fixed with this rollup.
You receive an invalid prefix length error and cannot set migration subnets if the prefix length is not between 4 and 30 characters for IPv4 or between 64 and 126 characters for IPv6.
Migration subnets for cluster and cluster nodes must be read-only.
Virtual Machine Manager (VMM) cannot take any action on Recovery Virtual Machine (VM) post-failover without reverse replication.
In some cases, a virtual machine on an SMB file share that is registered by using a NetBIOS name on a cluster will be in an unsupported cluster configuration state in VMM. This problem may occur even though the virtual machine is healthy and running. Additionally, the virtual machine status cannot be updated after that.
The virtual machine refresher does not correctly update the state of the virtual machine even after an unsupported cluster configuration issue is corrected.
In a bare-metal setup, the VMM service crashes when an out-of-range IP address is specified.
Every time DRA Initialize occurs in the VMM service, a database corruption exception is received.
You receive an “Unable to connect to the VMM DB” exception when you try to publish host and virtual machine network data to the SQL Server Reporting Service.
When you try import a Linux template from VMware in Virtual Machine Manager 2012 Service Pack 1, you receive error 22723.
The Get-SCVirtualMachine cmdlet does not return virtual machines by their IDs when the virtual machines contain clustered pass-through disks.
A user cannot set the domain name in Service Setting.
The VMM service crashes intermittently.
The VMM ID registry subkey value is set to a null value after Update Rollup 1 is applied.
This update fixes some UI text issues in the Virtual Machine Manager 2012 Service Pack 1 console for Disaster Recovery and for the HRM Azure Service.
This update fixes some reports that are not working with SQL Server 2012.
If a virtual machine has a static IP address, Test Failover does not set the IP address on the test virtual machine.
Virtual machine snapshot operations might fail if multiple snapshots are restored at the same time and have the same name.
The VMM server might crash when you create a virtual machine template from a virtual machine that has a previous failed task checkpoint data.
Logical unit numbers (LUNs) for EMC storage cannot be assigned to a cluster in VMM.
The VMM service crashes if a VMWare cluster or host is added by using a local root or administrator account.
Some log information is recorded multiple times in the guest log file.
This update fixes some performance issues in a bare-metal installation.
The placement of the Network Load Balancing (NLB) clusters in a network environment does not work for NLB load balancer and nested host groups.
The VMM service may stop while VMWare vSphere 4.1 is updated.
If Test Failover is initiated while VMM is restarting, the recovery side of VMM crashes.