persona managerment services is disable

[yulili9412]

My horizon environment is 7.4, and the vmware horizon view persona managerment for some of the virtual machines in my linked desktop pool does not start

1. Persona Managment service is disabled in all parents.  If I un/reinstall the agent it is still off.  If I try to start the service it fails with a time out.

2. In a linked clone where the user does not get their desktop icons and favorites which saved in profile, the service is in a disabled state.

3. in a linked clone (yes in the same pool) where a user does have their desktop icons and favorites the service is set to automatic and started.

Can anyone shed some light on this? Even if you aren't having the problem, can someone confirm what start persona services？

Thanks in advance for any insight.

[Shreyskar]

> Persona management service is by default set to 'Disabled' on master image and it is expected.

> When you login to VDI, persona GPO triggers a service start and it goes into 'Running' state. If in case, it doesn't start on VDI, thats a problem. You can check persona logs under C:\Program Data\VMware\VDM\logs\VMWVvp.txt and application events to see why service failed to start.

> Make sure persona GPO is getting applied correctly. Do a gpupdate /force on VDI and check if service starts.

> Other than these, make sure client side caching is disabled on VDI :

VMware Knowledge Base

> Take a look at VMware Knowledge Base if user profile is not syncing properly with persona remote repository.

> If running Windows 10 1803 or higher VDIs, make sure 'Roam local settings' GPO is disabled in Persona group policy otherwise user profile won't sync VMware Knowledge Base

[yulili9412]

Thank you for answering

A single problem desktop was tried as suggested and no log files were generated in the given directory

The service was changed from disabled to started after trying to update the group policy

The desktop pool is set to a logout refresh and no cache exists

The initial determination is that the group policy was not successfully executed

[Shreyskar]

You are correct. If forcing gpupdate triggers a service start, it means gpo is not applying properly at logon that you need to further investigate. You can check gpo events on that machine or gp logs to find what has happened at the time of logon.

Other than that the persona log file starts logging the profile sync information since the time service starts.