VMware Persona Management service sometime is and sometimes is not running on a VDI desktop after a recompose.

This is a strange one.  I have a desktop pool with 30 linked clone desktops.  When I look at the parent VM, the VMware Persona Management service is set to auto and is started. I recompose my desktop pool with a fresh snapshot of the parent VM,  After they complete many of the VDI desktops the VMware Persona Management service is not running and is set to disable.  Mind you not all 30, but a random amount.  I can recompose the pool again and again several (maybe more or maybe less) desktops the service is not running.  BTW, this is not a problem with the one desktop pool.  It is doing the same thing with another pool as well.  This pool only has 15 desktops.  Sometimes after a recompose half of the desktops the service fails to start and sometimes after a recompose may 3 of the 15 fail.  There just isn't any pattern I can find.  

I modified a power shell script that scans all my VDI desktops to see which ones the service is running on and which ones it is not.  Here is the results from me recomposing both pools just 30 minutes ago.  As you can see 20 of the 45 desktops the persona service is not started.

vm-dept-01       VMWVvpsvc       Running
vm-dept-02       VMWVvpsvc       Stopped
vm-dept-03       VMWVvpsvc       Stopped
vm-dept-04       VMWVvpsvc       Running
vm-dept-06       VMWVvpsvc       Running
vm-dept-07       VMWVvpsvc       Stopped
vm-dept-08       VMWVvpsvc       Stopped
vm-dept-09       VMWVvpsvc       Running
vm-dept-10       VMWVvpsvc       Stopped
vm-dept-11       VMWVvpsvc       Running
vm-dept-12       VMWVvpsvc       Running
vm-dept-13       VMWVvpsvc       Stopped
vm-dept-14       VMWVvpsvc       Stopped
vm-dept-15       VMWVvpsvc       Running
vm-gen-01        VMWVvpsvc       Stopped
vm-gen-02        VMWVvpsvc       Stopped
vm-gen-03        VMWVvpsvc       Running
vm-gen-04        VMWVvpsvc       Running
vm-gen-05        VMWVvpsvc       Stopped
vm-gen-06        VMWVvpsvc       Stopped
vm-gen-07        VMWVvpsvc       Running
vm-gen-08        VMWVvpsvc       Running
vm-gen-09        VMWVvpsvc       Running
vm-gen-10        VMWVvpsvc       Running
vm-gen-11        VMWVvpsvc       Stopped
vm-gen-12        VMWVvpsvc       Running
vm-gen-13        VMWVvpsvc       Stopped
vm-gen-14        VMWVvpsvc       Stopped
vm-gen-15        VMWVvpsvc       Stopped
vm-gen-16        VMWVvpsvc       Stopped
vm-gen-17        VMWVvpsvc       Running
vm-gen-18        VMWVvpsvc       Stopped
vm-gen-19        VMWVvpsvc       Running
vm-gen-20        VMWVvpsvc       Running
vm-gen-21        VMWVvpsvc       Running
vm-gen-22        VMWVvpsvc       Stopped
vm-gen-23        VMWVvpsvc       Running
vm-gen-24        VMWVvpsvc       Running
vm-gen-25        VMWVvpsvc       Running
vm-gen-26        VMWVvpsvc       Stopped
vm-gen-27        VMWVvpsvc       Running
vm-gen-28        VMWVvpsvc       Running
vm-gen-29        VMWVvpsvc       Stopped
vm-gen-30        VMWVvpsvc       Running


I just recomposed the two pools again and here is the results of the services scan.

vm-dept-01       VMWVvpsvc       Running
vm-dept-02       VMWVvpsvc       Running
vm-dept-03       VMWVvpsvc       Running
vm-dept-04       VMWVvpsvc       Running
vm-dept-06       VMWVvpsvc       Running
vm-dept-07       VMWVvpsvc       Running
vm-dept-08       VMWVvpsvc       Stopped
vm-dept-09       VMWVvpsvc       Running
vm-dept-10       VMWVvpsvc       Running
vm-dept-11       VMWVvpsvc       Running
vm-dept-12       VMWVvpsvc       Running
vm-dept-13       VMWVvpsvc       Stopped
vm-dept-14       VMWVvpsvc       Running
vm-dept-15       VMWVvpsvc       Running
vm-gen-01        VMWVvpsvc       Stopped
vm-gen-02        VMWVvpsvc       Running
vm-gen-03        VMWVvpsvc       Running
vm-gen-04        VMWVvpsvc       Running
vm-gen-05        VMWVvpsvc       Running
vm-gen-06        VMWVvpsvc       Stopped
vm-gen-07        VMWVvpsvc       Running
vm-gen-08        VMWVvpsvc       Running
vm-gen-09        VMWVvpsvc       Running
vm-gen-10        VMWVvpsvc       Running
vm-gen-11        VMWVvpsvc       Running
vm-gen-12        VMWVvpsvc       Running
vm-gen-13        VMWVvpsvc       Running
vm-gen-14        VMWVvpsvc       Stopped
vm-gen-15        VMWVvpsvc       Stopped
vm-gen-16        VMWVvpsvc       Stopped
vm-gen-17        VMWVvpsvc       Running
vm-gen-18        VMWVvpsvc       Running
vm-gen-19        VMWVvpsvc       Running
vm-gen-20        VMWVvpsvc       Running
vm-gen-21        VMWVvpsvc       Running
vm-gen-22        VMWVvpsvc       Stopped
vm-gen-23        VMWVvpsvc       Running
vm-gen-24        VMWVvpsvc       Running
vm-gen-25        VMWVvpsvc       Running
vm-gen-26        VMWVvpsvc       Running
vm-gen-27        VMWVvpsvc       Running
vm-gen-28        VMWVvpsvc       Running
vm-gen-29        VMWVvpsvc       Running
vm-gen-30        VMWVvpsvc       Running

Now there are only 8 desktops where the services is stopped.

Any idea where I can start looking.  Group Policy has been set to make sure the service is set to automatic.  Like I said, I can check the services on each VDI desktop and sometimes it is started after a recompose and sometimes it isn't.


Three HP Gen8 hosts running VMware 6.5 and Horizon 7