sureshasai
Enthusiast
Enthusiast

How to clear\Delete the existing VDI pools perfectly in horizon, Vcenter and ADSI Edit (Adom database)

Jump to solution

Hi ,

Whenever I create a new pool on the horizon it says pool name already exists. Guide me How to clear\Delete the existing VDI pools perfectly in horizon, Vcenter and ADSI Edit (Adom database) 

Thanks,

0 Kudos
1 Solution

Accepted Solutions
alsmk2
Hot Shot
Hot Shot

Do you have pools listed in the View admin gui as "deleting"? If so, just follow the instructions below:

https://jacob.gardiner-moon.co.uk/2016/08/15/removing-vmware-horizon-view-desktop-pools-stuck-in-del...

View solution in original post

4 Replies
alsmk2
Hot Shot
Hot Shot

Do you have pools listed in the View admin gui as "deleting"? If so, just follow the instructions below:

https://jacob.gardiner-moon.co.uk/2016/08/15/removing-vmware-horizon-view-desktop-pools-stuck-in-del...

View solution in original post

Gaurav_Baghla
VMware Employee
VMware Employee

You can use the DBCHk options and do not have to do this manual Cleanup Anymore

VMware Knowledge Base

Start with  --ScanMachines .

Regards Gaurav Baghla Opinions are my own and not the views of my employer. https://twitter.com/garry_14
0 Kudos
sjesse
Leadership
Leadership

This isn't completely true, I've had instant clone pools break and viewdbchk does not fix them.

0 Kudos
alsmk2
Hot Shot
Hot Shot

We've also still had a need to go back to the manual method since moving to 7.3.1.

Viewdbchk is still the first port of call, but there have been times where it has sent things absolutely crazy. For example, I deleted a pool which got stuck on the last VM, so ran the script as normal. Instead of clearing the pool, all the previously recreated desktops were suddenly recreated and went through the reprovisioining process. Re-running the script once the provisioning had finished had no impact. I couldn't manage the pool as it was still stuck in deleting. I had to manually delete around 100 desktops from vsphere whilst composer was disabled, then tidy up the db, and then run the viewdbchk script again.

Before 7.3 it was the only thing we needed to tidy up errors. Now, we're a little more cautious for reasons such as the above.

0 Kudos