Has anyone solved with issue with Windows 10 1803 not syncing persona data to the assigned share?
- The Windows 10 VDI is fully patched.
- I have tried agents 7.4, 7.5, and 7.6.
Still no joy... Anyone conquer this yet?
Spent a ton of time on the phone with VMware technical support. We are running 7.5 with vsphere 6.7 and persona. We just went to 1709 because 1803 is supported with persona even though 1803 is supported with 7.5. Also the big problem that we had was the 7.5 agent wouldn't work. So we had to use the 7.3.2 agent to get everything to work. Their big solution was just to upgrade to UEM.
As i saw on win10 1803 does not support not even roaming profiles.
I try all the versions of agents for persona and nothing worked.
So we stay on win10 1709 for now.
I think they try to stop persona management but they never announce it officially.
This is bad for the companies, UEm does not copy Appdata and personal files of the users, sop the "roaming profile" experience will be totally different.
So big change with no formal anouncement.
does anyone have an info when vmware fixes this problem?
The view agent 7.4, 7.5 (official and 7.5 from the link), as well as 7.6 dont solve the persona problem with win10 1803.
The persona issue is fixed in view version 7.7, you can install the view gent version 7.7 in the machine and then check it.
I have installed the view agent 7.7.0 on win10 1803.
The persona management problematic remains.
No sync with the .V6 Profile. The "Microsoft Software Shadow Copy Provider" service is started.
does anyone have the same problem or any idea?
I believe that I used the 7.3 version of the agent with 7.6 and it worked fine. Very frustrating. They want to push you to UEM, which is fine, but my customer was running standard edition with linked clones. and persona.
if a user logs on to the golden-master image and then later with this account on the vdi-clone the profile works fine.
All new users receive an empty V6 profile. Yes, this is very frustrating. we have also the standard edition and the pools are "linked-clones".
When I logout I see two folders in the V6 profile.
in the hidden folder is a text file withe the hostname from the VM. The other one with the GUID is the profile folder. When the logoff process is completed, the folders are deleted.
Exactly the same finding I have since the beginning with 7.5.1 agent.
Creates the main profile folder, but never populate it after logoff.
I had the same problem when "Roam local settings folders" was enabled. The .V6 profile would never copy over to the share.
In the VMWVvp.txt log I noticed it keep on failing during the upload.
This can be fixed by removing the "WindowsApps" folder from the default profile on the golden image. Another option is to enable the "File and folders excluded from roaming" and use "Appdata\Local\Microsoft\WindowsApps" path.
I removed the "WindowsApps" from the default profile and the profiles are syncing properly. I'm currently using Windows 10 1809 and View Horizon 7.7 with 7.7 agent. I hope this information can be some use to you.
This worked for me! Awesome find! I was doing some folder redirection testing and that worked except for local settings so i figured it was related to that. Thank you!
Thank You very much for this helpful contribution. It solved ourproblem with sync of Persona Management controlled roaming profiles. Still we have an issue with the profiles.
After the first login everything works fine, settings and custumization of OS are being made by user. Among others, Chrome is set to default browser. After the second login, the standard apps are resetted every time, which is very annoying. Edge is being set as default browser but crashes every time on start.
do you use default app customization with xml?
check this Windows 10 – How to configure file associations for IT Pros? – C:>Windows Internals – L'équipe Française de Support Wind… maybe it will help.
Or you could make a custom default profile. That could work.