Disable Discovery of Virtual Machine Resource Groups in Cluster MP

Both Cluster Management Pack and Virtual Machine Management Pack provide monitoring for Virtual Machine but from different perspective. In some situations the Cluster MP can be very noise as it is monitoring Resource Groups and Resources which could be down just because some virtual machines are shut down. Continue reading “Disable Discovery of Virtual Machine Resource Groups in Cluster MP”

Tips From the Field: Network Adapters are Missing in Network Connections


Recently I’ve had some VMs that went trough some failovers and after that I’ve noticed that the network adapters on some of these VMs were missing in Network Connections window. Running ipconfig I was able to see the adapters and their configuration. Also some of the VMs were part of cluster and the cluster roles couldn’t be moved to the nodes where the network adapters were missing in network connections. On those VMs I couldn’t open the admin share also. Continue reading “Tips From the Field: Network Adapters are Missing in Network Connections”

Error 23317 in VMM 2012 R2 When You Try to Apply Changes on VM That is Using Shared VHDX Disk

When you try to apply some change on a virtual machine with Shared VHDX disk in Virtual Machine Manager 2012 R2 you may receive the following error:


Error (23317)

The operation Change properties of virtual machines is not permitted on a virtual machine that has shared virtual hard disks.

Recommended Action

The operation Change properties of the virtual machine is not permitted on a virtual machine that has shared virtual hard disks.


Even that I was not changing anything related to the shared disks the task would fail. There is an easy fix for this and as many times it is called PowerShell. If you do not know PowerShell do not worry here are easy steps:

1. Open the Properties of the Virtual machine you want to change.

2. Make the change but do not apply.

3. In the left corner of the properties dialog box you will see View Script button. Press it.

4. A script will come up.

5. You need to take the part that is only related to your change. For example if I want to change only the classification of a network adapter I would have something like this:

$VirtualNetworkAdapter = Get-SCVirtualNetworkAdapter -Name “server1” -ID “6c733a79-4ef5-4df4-9b39-690b8ab0be46”
$VMNetwork = Get-SCVMNetwork -Name “VMetwork_Test” -ID “675245a2-c660-46d7-aee0-b8ece987e49b”
$VMSubnet = Get-SCVMSubnet  -Name “VMSubnet_Test” | where {$_.VMNetwork.ID -eq “623294a2-c660-46d7-aee0-b8ece987e49b”}
$PortClassification = Get-SCPortClassification | where {$_.Name -eq “Classification1”}

Set-SCVirtualNetworkAdapter -VirtualNetworkAdapter $VirtualNetworkAdapter -VMNetwork $VMNetwork -VMSubnet $VMSubnet -VLanEnabled $true -VLanID 77 -VirtualNetwork “vSwitch” -MACAddressType Dynamic -IPv4AddressType Static -IPv6AddressType Dynamic -PortClassification $PortClassification

Basically you take that part of the generated script that is only for your change. Remove any –VMMServer property reference and any –JobGroup Property reference.

6. Open VMM PowerShell. Paste the script and you are done. Your change is applied to VM with shared virtual disks.

Steps to Migrate Virtual Machines with Shared VDHX from One Cluster to Another

Imagine the following situation: You have two Windows Server 2012 R2 Hyper-V clusters – Cluster1 and Cluster2. Every cluster has two or more nodes. On Cluster1 you have two virtual machines VM1 and VM2. The virtual machines are in guest cluster and are using one or more Shared VHDX files. As you probably know virtual machines with shared vhdx files cannot be migrated with shared nothing live migration. Than how to move VM1 and VM2 from Cluster1 to Cluster 2? Here is a solution for you:

  1. Logon to VM2. Start Failover Cluster Console. Pause VM2 as node in the cluster and drain all roles.
  2. Shut down VM2.
  3. Logon to VM1. Shut down VM1.
  4. Remove cluster resources for VM1 and VM2 from Cluster1.
  5. Open Hyper-V console on the node of Cluster 1 where VM1 and VM2 are.
  6. From the VM settings of VM2 remove all shared VHDX disks. Apply.
  7. From the VM settings of VM1 remove the checkbox for shared VHDX on all drives where is checked. Apply
  8. From Hyper-V console move VM1 to one of the nodes of Cluster2.
  9. From Hyper-V console move VM2 to one of the nodes of Cluster2.
  10. Now VM1 and VM2 are on Cluster2.
  11. Open the Hyper-V console on the node of Cluster2 where VM2 is.
  12. Open VM settings for VM2. Attach all shared vhdx files as disks that you’ve removed in step 6 in the same order as before. Check the checkbox for shared VHDX on all of them. Apply
  13. Open VM settings for VM 1. Check the checkbox for shared VHDX for all disk that you’ve removed in step 7. Apply.
  14. Add VM1 and VM2 as cluster resources in Cluster2.
  15. Start VM1. Check if VM1 is healthy and all resources/roles are up in the Failover Cluster Console.
  16. Start VM2. Resume VM2 as node of the guest cluster. Migrate all roles and resources to make sure everything is ok.

These are all the steps you need. I hope they will help you.

Unsupported Cluster Configuration for Virtual Machines located on SMB Share in VMM 2012 SP1

The last issue I’ve stumbled upon with System Center is with VMM component.


  • You have SCVMM 2012 SP1 UR2 installed
  • You have Windows Server 2012 Hyper-V for hosts
  • You use SMB 3.0 share for storing virtual machines
  • Some or all of your virtual machines does not use FQDN path to their vhd/x files
  • You’ve added your File Server in VMM by FQDN or NetBIOS Name
  • You receive the following error: Error (13924) The highly available virtual machine (VMNAME) is not supported by VMM because the virtual machine uses non-clustered storage.
  • Some or all of your virtual machines show as Unsupported Cluster Configuration



  • You may also have missing appropriate NTFS permissions on the share
  • image


I’ve managed to resolve this issue by executing the following steps:

1. Make sure you’ve added your file server in VMM by FQDN. If it is not added by FQDN you have to add it.

2. Create new share. You can create it on the same server. Give the share appropriate permissions.

3. Locate the new share in VMM. Add it as storage location to your hosts/clusters.

4. After is added make sure it show green in the properties of the hosts/clusters.

5. Storage migrate all your virtual machines from the old share to new share. For the machines with status Unsupported Cluster Configuration you can change the status to Running by live migrating them trough the Failover Cluster console.

6. After storage migration of each virtual machine refresh it and make sure in the properties of the machine in Status tab all is green.

7. After successful migration of all virtual machines you can remove the old share from the hosts/clusters and delete it from the File Server.


I’ve also may had problems with the permissions on the old share but it is easier to create new share than fixing permissions on existing share with running virtual machines.

The information is provided ‘AS IS’ with no warranties and confers no rights. Keep in mind that your case may be similar and this solution may not work for you.

Software I’ve used:

  • Windows Server 2012 with latest updates
  • SCVMM 2012 SP1 UR2
  • File Server with SMB share