Orphaned VMDKs Expected?

[ConradR314]

I have a quick question I am hoping a Horizon expert or two can weigh in on.

When running vCheck or other report-like scripts in my Horizon view environment, it is coming back and informing that I have a LOT of orphaned vmdks.

Upon inspecting the vmdks it lists, most of them have names appended like:

*vdm-disposable.vmdk

*digest.vmdk

*digest-delta.vmdk

*checkpoint-digest.vmdk

*checkpoint-digest-delta.vmdk

So my question....Is this something that is expected with Horizon? Should I just ignore the vmdks with those additions appended to the vmdk name because Horizon is managing them?

Thanks in advance!

[BenFB]

I see this when VMs are in the middle of provisioning/refresh/recompose operations. Once the operation completes they typically go away. However, sometimes they are files that need to be manually cleaned up. I just checked and had three VMs like this (All three were in a floating pool this is set to refresh on log off).

[techguy129]

Please see this KB: VMware Knowledge Base

That doesn't seem normal. Its not in my environments. Horizon does a lot of snapshoting, cloning, etc. so will cause a lot of those to exist but should be cleaned up. It would take some more investigation to see what is going on.