Article ID: 2822797 - View products that this article applies to.
In the Virtual Machine Manager admin console, VMs report Unsupported Cluster Configuration. The job view error is below:
One or more available cluster volumes associated with host %VMHostName; is not associated with a path in the default placement path list and will not be considered for placement. Refresh the cluster to ensure that all available cluster storage has an associated default placement path.
This can occur if there are duplicate Volume Serial Numbers (VSNs) on the host. Virtual Machine Manager uses VSNs to track which disk it is working with.
To identify if disks are using the same VSN, execute the single line below at an elevated PowerShell prompt:
This will create an output file at c:\temp\VSNs.txt that will contain data similar to the following:
If there are duplicate numbers in the SerialNumber column, you must change one of the VSNs. To do this, download VolumeID from Sysinternals
(http://technet.microsoft.com/en-us/sysinternals/bb897436.aspx). This tool allows you to change the VSN to another number, but it does require that the drive be assigned a letter. Once the VSNs have been changed you must reboot the server for Windows to recognize the new values.
If the disks are in a Failover Cluster CSV, they will not have drive letters. To correct these volumes using VolumeID, they must be taken out of the CSV long enough to be given a drive letter in Disk Management. Then you can change the VSN with VolumeID and place them back in the CSV. A reboot is required after changing VSNs.
VSN’s are not commonly used or known about. To see the VSN of your C: drive, you can run the VOL command from a CMD prompt. An example of this is below:
(http://go.microsoft.com/fwlink/?LinkId=151500)for other considerations.
Article ID: 2822797 - Last Review: March 19, 2013 - Revision: 2.0