Update Rollup 6 for System Center 2012 R2

Updae Rollup 6 for System center 2012 R2 released. I am happy to see that System Center team is focused and really fixing up the issues faster.

Specific to SCVMM 2012 R2 – Rollup 6, 46 bugs are fixed with this rollup.  Also few new features also got added with this rollup.


  • Issue 1

    An 801 error occurs when VMM objects are removed. VMM sometimes encounters an issue in which a VMM object such as a virtual machine cannot be removed either from the UI or Windows Powershell because some of its child objects are missing in the database. This frequently causes users to search for remedial scripts to remove the affected objects. In Update Rollup 6, VMM has improved three Powershell cmdlets to minimize 801-related errors. These cmdlets areRemove-SCServiceTemplate, Remove-SCLibraryServer, and Remove-SCLibraryShare. Users do not have to use the –Force flag together with these cmdlets in order to avoid 801 errors. The cmdlets provide the ability to resolve dependencies that lead to 801 errors.

  • Issue 2

    The VMM service crashes and generates an access violation error in System.Xml when it respons to an Integration Services event.

  • Issue 3

    Critical Exception in the WCF error handler — ObjectDisposedException — Microsoft.VirtualManager.Engine.Remoting.ClientConnection.HandleError. When VMM shuts down the WCF service host, it is calling Abort which can cause any unprocessed messages to be ungracefully terminated, and this can result in ObjectDisposedExceptions being thrown. VMM’s top-level WCF error handler sees these exceptions before the process has terminated and reports them as critical exceptions. So here VMM reports harmless errors as critical errors possibly adding to the user confusion.

  • Issue 4

    Option for MAC Address greyed out in UI when vnic is not connected. This prevents users from marking the nic as static. After you upgrade to VMM in System Center 2012 R2, customer cannot choose the option of Static Mac Address in the VM templates he creates, if the VM is not connected to a network. The MAC Address and IP options are greyed out when the VM is “not connected”. Therefore, he cannot assign a static MAC Address to the VM before the deployment.

  • Issue 5

    VM customization can fail with critical exception when Hyper-V does not return a floppy drive object. During customization of a VM there is a chance that Hyper-V will return the Floppy Drive object as null and VMM trying to add one, but adding Floppy Drive is not implemented at Hyper-V which will throw an exception causing job failure and leaves the VM in creation failed state but user can repair the VM to be functional, This ‘may’ occur if the Floppy Drive Config (on remote share) is not available to Hyper-V or Hyper-V is busy/stressed.

  • Issue 6

    Cannot deploy VMs with static IP when multiple IP Pools for one VM Subnet are configured. Customer tries to create a VM by using a Template which has static IP settings. If there are multiple IP pools in a Subnet and customer provides an IP address from a different pool than the default one (ie., auto populated pool shown in the UI), then the VM wizard finishes without any errors but the VM creation fails with “IP Address Out of range” error.

  • Issue 7

    VmmService crash occurs during handling of removed VM Subnets on IP change events sent by Hyper-v. In a NVGRE setup, if there is an event sent by Hyper-V for IP Change but the VM Subnet no longer exists in VMM, it causes a VMM service crash.

  • Issue 8

    VMS are reported missing as the VmMovedRefresherEvent is not received. When a VM move event occurs while a host is not in Eventing mode and the VM is in migration state and when the event refresher hooks up there might be a window where no one is listening and the update operation right before listening mode does not receive the change.
    Therefore VMM will not receive these changes until next Full Refresher which can be as worst as 24 hours.

  • Issue 9

    Require explicit flags to indicate missing or Service VM removal during Remove-Host to the user. Currently VMM does not check for the existence of VMs on host while removing host from VMM. A host can contain Service VMs, VMs deployed on cloud or having custom properties that are defined for it, If user accidentally remove such host then all these associations will be broken. This fix will avoid such scenarios by prompting users for a confirmation message before such hosts are actually removed from VMM.

  • Issue 10

    If you have a Logical Network that has multiple network sites, and the network sites are visible to the host network adapter, PAs from those different network sites will be allocated and the routing information must be set also. (Network sites are sometimes called “logical network definitions.”) In a multiple host scenario with vm1 on host1 being connected to PA1, there is a case if a VM2 is connected to a hnv LN and has a PA1 for NetwkSite1 and then it is disconnected and reconnected later on and has a PA2 for NetwkSite2 (randomly or because of PA exhaustion), then for some time, we might not populate the PA routing information between NetwkSite1 and NetwkSite2. This occurs because of the way the internal route representation is keyed for insertion in a hash table.

  • Issue 11

    When a host is refreshed it establishes a WinRM network connection (to each host refreshed) that constantly streams data

  • Issue 12

    When multiple host virtual network adapters are created, random failures are observed. When customers create multiple virtual network adapters in one shot as part of a logical switch, one or more virtual network adapter IP configuration may fail.

  • Issue 13

    User hits a duplicate key insertion in HostWSManGetter.UpdateRASDCache when doing a host update.

  • Issue 14

    When the user tries to clone a VM with checkpoints, after the cloning operation is complete, VMM wrongly recognizes the newly created clone VM as original VM, and incorrectly infers that the VM has migrated and tries to handle this change. Therefore, an additional VM on another host with ‘missing’ state is created. VMM thinks VM is using a different host and this VM is not visible to TFS until next VM update.

  • Issue 15

    When VSEM provider is upgraded, the provider’s capability to receive notifications is not indicated to the notification engine

  • Issue 16

    Networking placement crashes during dynamic host optimization. Some placement operations were supposed to be run as task. When it is executed in refresher task, context is null which leads to placement crash.

  • Issue 17

    When Delegated Administrators start the VMM console it takes 4+ minutes to open the VMM console. In large environments VMM console start is delayed for Delegated Administrators when it is compared to Administrators.

  • Issue 18

    Storage provider update fails after replacing disk on sofs.

  • Issue 19

    VMM cannot update replica/primary VM without ASR, also Migration of Recovery VM in IR Pending state does not perform live migration

  • Issue 20

    When a VM is deleted, the chechpoints are merged before being deleted. When the user tries to delete a VM with checkpoints, it takes a long time for deletion (sometimes up to an hour) to finish.

  • Issue 21

    A Run DO operation sometimes receives critical exception : DBCorruptionException

  • Issue 22

    Some users use large VIPAddress Sets instead of IP Ranges to make it easier to add/remove individual IPs. VMM Management Pack schema currently limits this field to 256 chars (default). However, the users may have values ~500 characters long. And therefore Discovery was breaking VMM-OM integration because of an unexpected exception from SCOM.

  • Issue 23

    Target RG and target LUNs are not associated after enableRG task if the RG/LUNs are precreated.

  • Issue 24

    Have to update MAC Address entries for an F5 Gateway device when it fails and is replaced. If an F5 Device is RMA’d and replaced with a new device with a new MAC address, VMM does not have a way to update the MAC address for the new device.

  • Issue 25

    Let user stamping on replica VM to let you stamp user identity. Users have to update UserRole and Owner attributes on their ReplicaVMs but currently any operation on the Replica VM is blocked. So, they cannot update these two parameters on Replica VMs.

  • Issue 26

    Registerred SMB share is not displaying as target path option when you deploy a new HA VM to a cluster.

  • Issue 27

    Critical Exception in the Storage Refresher when discovering the replication service — ArgumentNullException — SetCustomOptions.

  • Issue 28

    During the Host refresher VMM queries the team Information (switch team Or LBFO team). Whereas querying switch teams VMM hits the WSMan exception which causes the vswitch to disappear from the console.

  • Issue 29

    HTTPS protocol is not supported in Probe, then VMM cannot created monitor rule to monitor HTTPS site. VMM supports HTTP and HTTPs in the LB port configuration section but HTTPS is not supported in the LB probe protocol section.

  • Issue 30

    Resource owner (SSU User) not authorized to access ‘GrantedTo’ list of a resource and therefore not able to see who all have acess to the resource. When the user granting access is also a self-service user, then they cannot see the changes they have made until they restart the console. An admin user can see the change, but for a self-service user, the GrantedToList continues to return cached results, until they restart the console.

  • Issue 31

    Unable to move parent disks that have the built-in migration process of VMM. User has several hundreds of VMs, with all diff disks pointing to a single parent. Moving all these VMs to a new storage solution is being blocked by VMM. In case of diffdisks, if any ancestor disk in the hierarchy (parent/child relation) is shared by another diff disk, then the storage migration of diff disk is blocked by VMM, but same is enabled through Hyper-V Manager.

  • Issue 32

    Field expectedDSColumn throws critical exception while tracing the message for columns mismatch causing Server crash when it runs get-scvmhost. After Server DB is updated to Threshold, R2 server cannot work with it in certain cases. This codepath is used by some networking objects and ADHC objects.

  • Issue 33

    When scaling out an existing service template, duplicate Hyper-V VMs with the same name are created on VMM in System Center 2012 R2 Update Rollup 5.

  • Issue 34

    SCSR, WDS, and DPM servicing fails in VMM with error “22029: VMM could not create a process for the script command cmd.exe”

  • Issue 35

    Live migration of the VM fails, when we use clustered storage space as CSV and the VM’s storage is located on CSV. Hyper-V Cluster Live Migration does not work any longer after VMM 2012 R2 UR5.

  • Issue 36

    Base disk placement should rotate between valid placement shares.

  • Issue 37

    The VMM Console may use an existing Release string during service template copy. Sometimes, users cannot copy a service template by using “Copy” command for a service template. Reason is that Administrator console generates an already existing string for the release.

  • Issue 38

    The Capacity Overview Tile is missing in VMM in System Center 2012 R2. In VMM in System Center 2012 SP1, under the VMs and services pane, when you select a host and then click overview on the top menu, the console provides Summary and Capacity information about the selected host. The details about Processor cores, memory (GB) and Storage (GB) became unavailable in System Center 2012 R2.

  • Issue 39

    VMM Service Crashing because of duplicate VSID. In rare cases (synchronization/race-condition and random number collision), different HNV VM Subnets can obtain the same VMSubnetIdentifier (a.k.a VSID). This leads to unexpected behavior when you use these HNV VM subnets. For example, for VMs connected to this subnet, the VMs may not obtain the expected connectivity and will be unable to talk to VMs on the same subnet. Or when their IP address changes it will cause VMM Service crash.

  • Issue 40

    Deploying a VM behind a Load Balancer causes a Critical Excepion on Placement:

  • Issue 41

    Start Page that was introduced in Update Rollup 5, is removed in Update Rollup 6.

  • Issue 42

    A virtual machine is not associated with a replication group and could not be moved to a location that is protected by replication group.

  • Issue 43

    Guest IP on HNV Network is not marked as Dynamic/DedicatedGuestIP even if settings are enabled for it. CA Failover broken. For any IP address added/moved in a VM connected to NVGRE Network (HNV Guest Cluster/Guest IP Failover scenario), the IP address is *not* marked as dynamic (type = DedicatedGuestIP in VMM) even if the VM has the settings EnableGuestIPNetworkVirtualizationUpdates=true. When the first time that the IP address is added/moved it will work, but later failovers of the IP (moving from one VM to other) will not be detected automatically. Therefore the IP address will not be reachable and the VM will lose connectivity.

  • Issue 44

    Older embedded storage provider from Hitachi integration broken with UR5. The storage provider cannot be refreshed. This prevents management of the provider.

  • Issue 45

    The VMM client crashes when you set power optimization time range.

  • Issue 46

    A race condition exists in the disposal of the WnvEventEntrySubscriptionObserver when the connection of the host fails.