Quantcast
Channel: Virtual Machine Manager – General forum
Viewing all articles
Browse latest Browse all 2770

VDI Created VMs VM fails to show up in the System Center 2012 Virtual Machine Manager

$
0
0

A couple of days ago I ran into an issue where VDI Created VMs VM fail to show up in the System Center 2012 Virtual Machine Manager. I found   KB2974441 (Text below) on the MS Support site yesterday...  I wanted to double check the KB so I went back to the MS support site, just to find that the KB is no longer listed.

I did what KV2974441 suggested. Removed the #Cluster-Invariant# GUID from the VMs and Refreshed the Host that contains the VM) but the machines are not showing on SCVMM

Any suggestions.

KB2974441

After you create Virtual Desktop Infrastructure (VDI) based virtual machines (VM) in new Collections by using Remote Desktop Services (RDS), the VM intermittently fails to show up in the System Center 2012 Virtual Machine Manager (VMM 2012) console.

This is a known issue in System Center 2012 Virtual Machine Manager, System Center 2012 Virtual Machine Manager Service Pack 1 (SP1), and System Center 2012 R2 Virtual Machine Manager. 

Resolution

To resolve this issue follow the steps below.

  • Remove the #Cluster-Invariant# GUID from the VMs that do not appear in the SCVMM 2012 console: This can be found by in Hyper-V Manager -> VM Settings -> Management -> Name.
  • Refresh the Host that contains the VM: This can be done by going to the VMM console -> Right-click Host Properties -> Refresh Virtual Machines.

More information

VMM adds a #CLUSTER-INVARIANT#:{<guid> } entry to the description of the VM in Hyper-V. This GUID is the VM ID SCVMM uses to track the VM. If the RDS"source" VM is managed by SCVMM, #CLUSTER-INVARIANT#:{<guid> } entry is added to the “source” VM. When a NEW Collection is created through RDS, the #CLUSTER-INVARIANT#:{<guid> } entry of the "source" VM is passed to the VDI VM during the RDS deployment process. Therefore, it causes a duplicate #CLUSTER-INVARIANT#:{<guid> } entry. Intermittently, the GUID is not overwritten with a new GUID when SCVMM discovers the newly deployed VDI VM. The duplicate #CLUSTER-INVARIANT#:{<guid> } entry causes SCVMM to skip the refresh of the VDI VM because another VM contains the same #CLUSTER-INVARIANT#:{<guid> }




Viewing all articles
Browse latest Browse all 2770

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>