Instant Clone Desktop stuck in DELETING Status

[Super6VCA]

Hi all,

I have an instant clone pool that has a desktop that is stuck in deleting status in the admin console.  The destop in the VI Client is still there and i can console in.  I can shut down and restart with no affect at all.  Admin console still says deleting.  Tried to remove and recover and no luck.  Still the same.  I also tried to restart teh management services on the host that it resides on with no luck also.  It appears that all other desktops are working just fine in that same pool.  Any idea how to get this vm back to working status??  Any comments are welcome.  Thanks

Horizon view 7.0.1 using the 7.0.2 client (per VMware tech)

[wakeman811]

Try going through this kb to remove vm's that are stuck in deleting

Provisioning or recomposing a linked clone desktop pool fails

Since its an instant clone you should not have to do the composer db portion, but could be a good idea to check.

[pari2k3]

I believe restarting connection server service could resolve this issue.

[rseekell]

I had machines stuck today even after restarting the connection servers.  What I did to fix them was to shut down the desktop in vCenter, and then it deleted from both vCenter and Horizon View (7.0.3). 

[Instant0Darth0V]

I had this issue, but powering off the instant clone allowed the delete process to continue.

Also, if you are in a folder on vcenter that is being used by Instant Clone, then the whole deal cannot delete if you are deleting the instant clone pool. So get out of the folder also, else the pool will not delete.

[tgortva]

In our case, none of the instant cloned machines existed in vCenter or the DataStore.

Further investigation revealed that someone had deleted the Master Image and therefor, View had nothing to reference from.

After the Master Image was restored from the Datastore, the pool provisioning was disabled and the "Deleting (missing)" VM's were removed from ADSI on the connection server.

Re-enabled provisioning for the pool and the VM's no longer reappeared in Problem vCenter VM's.

[Super6VCA]

All snapshots (currrent and last) are still there and intact.  Nor sure if Viewdbchk is what i am going to need to investigate with.  problem with that is that i can't disable my pools too often.  

[jeffrobinson85]

Perry,

I would try and delete the VM's out of vCenter and then the ADAM database. I would disable provisioning on the pool before deleting the VM's. See if they rebuild correctly. You might need to use IcUnprotect.cmd to unprotect the instant clone in vCenter

Connecting to the View ADAM Database

VMware Knowledge Base

Removing the virtual machine from the ADAM database on the connection server

VMware Knowledge Base   

Instant-Clone Maintenance Utilities

Instant-Clone Maintenance Utilities

Let me know if this helps

Jeff

[pari2k3]

1. Delete desktops from VI Client

2. Delete desktop entries from ADAM database

3. New Desktop start provisioning once removed from ADAM database to maintain the Desktop pool size

How to delete entries from ADAM database

https://vmguru.com/2014/02/how-to-delete-an-orphaned-desktop-pool/