This other day, I got to work on a simple but interesting issue. This user had a power outage in his datacenter and all his servers went down. This caused various tasks initiated by the View Connection Server to fail which in turn led to orphaned VMs.
We tried removing the stale entries as per the below KB article, but we were still not able to create new VMs with the same name.
Manually deleting linked clones or stale virtual desktop entries from VMware View Manager
I was finally able to fix it, after I cleared the stale/orphaned VM entry from all the below locations.
1. View Connection Server Adam database - Refer above VMware kb
2. View Composer database - Refer above VMware kb
3. Virtual Center inventory - Manually delete the VM
4. Virtual Center Datastore - delete the VM folder
5. Active Directory
If this article is of some help, please leave a comment.
A stale article, if you dip it in a good, warm, sunny
ReplyDeletesmile, will go off better than a fresh one that you've scowled upon. see the link below for more
info.
#stale
www.ufgop.org
Your house is valueble for me. Thanks!… best online casino
ReplyDelete