System Center 2012 SP1 – Virtual Machine Manager Known Issues & Workarounds
Microsoft finally released System Center 2012 SP1 for MSDN and TechNet subscribers. Now if you are lucky enough to have such a subscription you can download and evaluate System Center 2012 SP1 and especially Virtual Machine Manager. Microsoft also released a list of know issues on TechNet. So if you run into any troubles make sure you check the Release Notes for Virtual Machine Manager in System Center 2012 SP1 first.
Service deployment fails and the guest agent on virtual machines does not work as expected
Description: Service deployment fails, and the guest agent on virtual machines created by the service instance is uninstalled or corrupted.
Workaround: If this occurs, install the agent manually as follows:
- Install the Visual C++ Redistributable package on the virtual machine host. The installation file is located at:
64-bit computer: <VMM installation folder>\agents\amd64\vcredist_x64.exe
32-bit computer: <VMM installation folder>\agents\i386\vcredist_x86.exe
- Install the agent on the virtual machine. The installation file is located at:
64-bit computer: < VMM installation folder >\agents\Guest\amd64\vmmGuestAgent.msi
32-bit computer: <VMM installation folder>\agents\Guest\amd64\vmmGuestAgent.msi
High availability with NPIV is not supported
Description: High availability with N_Port ID Virtualization (NPIV) is not supported. VMM is compatible with virtual (synthetic) fibre channels that are configured for virtual machines in Hyper-V.
Windows PowerShell help might not open as expected on computers running localized operating systems
Description: Windows PowerShell help for System Center 2012 SP1 is available in English only. When you run the Update-Help command, the help is downloaded and placed in a folder specifically for the English version of the help (ENU). However, when you run Get-Help command, the computer attempts to retrieve help from the folder corresponding to the language of the operating system. If the operating system language is not English, the attempt fails.
Workaround: To fix this issue, install the update described in Microsoft article 2770917: Windows 8 and Windows Server 2012 cumulative update: November 2012, on computers that require Windows PowerShell help for System Center 2012 SP1.
Deploying virtual machines to hosts on perimeter networks might fail
Description: When creating a virtual machine, if you configure VMM to use BITS (Background Intelligent Transfer Service) in unencrypted mode to initiate a file transfer from the VMM server or library server to a destination host located in a perimeter network, the transfer might fail. This happens because by default, on the firewall, VMM opens only the port used for encrypted traffic (443).
Workaround: On the perimeter firewall, manually open the WSMan TCP port (5985 by default).
Registering a storage file share on a library server might cause an error
Description: If you register a storage file share on a library server that contains a library share with the same name as the storage file share, and then you remove the library share or unregister the storage file share, VMM might stop working unexpectedly.
Workaround: To avoid this issue do the following:
- Outside the VMM console, go to the storage provider on which the storage file share exists, and stop sharing it.
- In the VMM console, refresh the storage provider. Then specify a unique name for the file storage share, and register it again.
Failing over and migrating a replicated virtual machine on a cluster node might result in an unstable configuration
Description: In the following scenario, failing over and migrating a virtual machine might not work as expected:
- A primary virtual machine on a cluster node is replicated to a secondary virtual machine on a cluster node or stand-alone host.
- A failover is initiated from the primary virtual machine to the secondary.
- Within a day, the primary virtual machine is migrated to a different node in the cluster.
If this occurs, the primary and secondary virtual machines might not appear correctly in the cluster node, or on the stand-alone server. In addition, deleting one of the virtual machines might delete the other.
Workaround: To avoid deleting the virtual machine, do the following:
- Remove and then re-add the cluster. This will clean up the VMM database for the secondary virtual machine.
- Refresh the virtual machines on the hosts, to ensure that the primary virtual machine appears correctly in the cluster node.
Modifying Tenant Administrator permissions affects permissions for self-service user roles
Description: When any property of the Tenant Administrator user role is modified or added, share and receive permissions assigned to Self-Service user roles that were created by a Tenant Administrator will be removed unexpectedly. Other permissions assigned to these Self-Service user roles will not be affected, and will behave as expected.
Workaround: After modifying Tenant Administrator role properties, ensure that permissions assigned to Self-Service user roles created by the Tenant Administrator are defined as expected. If permissions have been removed inadvertently, add them back in.
Member level permissions for network quotas are not applied for the Tenant Administrator role
Description: When you create a Tenant Administrator role with permissions to create virtual machine networks, and set a member-level virtual machine network quota, the quota is not applied, and users can exceed the limit set.
Workaround: Set a limit using the role-level quota value that is enforced.
Cancelling and restarting when creating a new virtual machine might fail
Description: Cancelling and restarting the wizard when creating a new virtual machine might fail if the computer name specified for the virtual machine is automatically generated, based on a template naming pattern.
Workaround: Do not cancel and restart the wizard when creating a virtual machine from a template that uses a pattern for the Computer Name property.
BlogEngine service deployment fails
Description: Attempting to deploy the BlogEngine service fails, and error 22631 is issued.
Workaround: Ensure that the configuration file (.vhd or .vhdx) used for deploying the service has 9.5 GB or more of free disk space.
Virtual machine cannot be connected to a private or internal network
Description: A virtual machine cannot be connected to a private or internal network.