Remove VM from Vmware View

We use VMware view Horizon at work. Sometimes when VDI computer does not connect to the back end VM, we reset the VM or unassign the VDI, however sometimes it does not work, so we remove the VM from VMware view, and reboot the VDI so that it connects to another VM .
I would like to know the impact of removing VM from VMware View. is it gone forever or still exist somewhere ?

Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

are you deleting the VM or merely removing it from the listing?
removing from the listing will likely leave the files in place.

try to confirm.  look at the config where the files are, remove the link and see whether the files remained.
jskfanAuthor Commented:
When you right-click on the VM, you will see Remove , I believe you also see "Delete". I am not in front of the console now.

So what is the impact of each of them ? does the got removed just from the list or something else gets removed in the background ?
Either way Removing it help the VDI reconnect successfully...I did not check if the VDI has chosen another VM
It is not clear to me where you are performing the task, the removal from the listing while all the data remains merely severs any stale references to the VDI being used.

understanding what your issue is would answer whether the removal from the listing is merely coincidental versus actual remedy.
Big Business Goals? Which KPIs Will Help You

The most successful MSPs rely on metrics – known as key performance indicators (KPIs) – for making informed decisions that help their businesses thrive, rather than just survive. This eBook provides an overview of the most important KPIs used by top MSPs.

If everything is working as it should, the proper way to remove a View desktop is to go to the View manager and remove it from there. That should remove it from the View databases and remove it from showing in the vSpehere client which means that the VMDK and support files will also get removed. If you try and remove it from the vSphere client, this may remove the VM itself, but it will still show in the View manager and be in the databases.

If you choose to remove it from the vSphere client first, then you might still be able to go into the View manager and attempt to remove it from there.  You may have to do it twice, but in many cases it will also disappear from there.  If it gets all bolloxed up then you need to remove the machine from the vSphere client which should also remove the files from storage and then manually remove the item from the databases. View has two databases: the ADAM DB and the Composer DB.  This article gives some good information about manually cleaning the databases:
jskfanAuthor Commented:
when you open one of the Pools and select Inventory, you right-click on one of the VMs and select "Remove"
If you choose remove and delete from disk there is nothing leftover.
However you will still need to remove the AD computer account otherwise your AD inventory will get pretty messy at some point.

Can you explain the root problem real quick? Maybe i find a solution for that.
When you talk about VDI not connecting to VM - what is really (not) happening?

VDI is just the pcoip_server (view agent) on the VM. It should connect.
You can also check the pcoip_session log for the disconnect reason. Or just post it here.

jskfanAuthor Commented:
I believe in our Environment they use VMware Composer. If the VM is deleted from VMware view I guess it can get re-created.
for instance if you set up the loop to 100 VMs, if one VM gets deleted , the composer will create a new one.
That 's what I have been told.
Correct ?
If you remove a pool, that removes all of the machines associated with that pool from showing in the vSpehere client, it removes them from storage and from the View manager, then the pool entry itself will be deleted from the View manager.

If you remove a desktop, View should recreate the desktop. If you use a "normal" installation of linked clones the recreated clone should have a name that is in the current naming scope of the pool. With persistent full desktops usually they get a number after the desktop name like PDT1, PDT2, etc. But because of how View handles these names do not get reused. So if you have PDT1-150 and you delete one, the new one should have 151, then 152, etc. And this can make your AD and DNS look ugly if you don't go in and clean it.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
jskfanAuthor Commented:
In which case you are saying when VMs are removed, the same names will be recreated at some point in time,  
ex:  PDT1-150
there will be no PDT151 at any time
jskfanAuthor Commented:
Thank you
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.