Creating a new-fully patched 1709 master image resolved the issue. I made absolutely NO changes to my mandatory profile config.
Thanks to all who participated in the solution. Very nice to have this solved the day before I leave for vacation!
I'm also experiencing this exact same issue on 1803
2018-09-24 17:27:32.337 [WARN ] ExportFiles::ExportFile: Sharing violation for file '<LocalAppData>\Microsoft\Windows\CloudStore\cloudstore.dat'
2018-09-24 17:27:32.337 [WARN ] ExportFiles::ExportFile: Sharing violation for file '<LocalAppData>\Microsoft\Windows\CloudStore\cloudstore.dat.LOG1'
2018-09-24 17:27:32.337 [WARN ] ExportFiles::ExportFile: Sharing violation for file '<LocalAppData>\Microsoft\Windows\CloudStore\cloudstore.dat.LOG2'
I also notice this isn't the only UEM setting with this issue.
It also appears to be the case for Edge:
2018-09-24 17:27:32.056 [WARN ] ExportFiles::ExportFile: Sharing violation for file '<LocalAppData>\Packages\Microsoft.MicrosoftEdge_8wekyb3d8bbwe\Settings\settings.dat'
2018-09-24 17:27:32.056 [WARN ] ExportFiles::ExportFile: Sharing violation for file '<LocalAppData>\Packages\Microsoft.MicrosoftEdge_8wekyb3d8bbwe\Settings\settings.dat.LOG1'
2018-09-24 17:27:32.056 [WARN ] ExportFiles::ExportFile: Sharing violation for file '<LocalAppData>\Packages\Microsoft.MicrosoftEdge_8wekyb3d8bbwe\Settings\settings.dat.LOG2'
I'd rather not have to go back to 1709. I have opened a support case so I'll let you know if anything comes of it.
For reference I followed not only this guide:
But also this series:
None of which have helped with the UEM issue.
I am curious if there has been any progress or suggestions for this with 1803?
I have UEM working well for persisting the start menu without mandatory profile. (and even using UEM built in "default settings" for a standardized start menu on first logon!)
Mandatory profiles are a requirement due to the fact that logon of Win 10 is simply too slow without them. The UEM Start menu config does not work and I am getting the same results as the original poster (only edge icon)
I am also getting the issue with 1803, did anyone resolve the issue?
Hi MattVico. I have been experiencing the same problem and came up with a fix for our environment. This may work for you it may not.
So the first thing that I did was go into the registry on our golden image and change the following service keys' "Start" DWORD value data to 4:
These services seemed to be causing the system to hang on to the cloudstore.dat, cloudstore.dat.log1, and cloudstore.dat.log2 during logout and if those files don't get pulled over by UEM on logoff, then a user will not have anything on their start menu when they log back in. While I was able to start persisting the start menu including programs, accessories, and user pinned start menu tiles, after a certain amount of logoffs i would start losing my start menu every other login. So what I found were a couple of things.
If you are using the following VMware provided templates: Start Menu, Taskbar, and Windows Explorer, there is one duplicated registry tree and one duplicated registry value that are being pulled for multiple config file. So that you can see the values that are a part of the VMware provided template, you must highlight the Template, click on Manage, and then click on expand. You will get the pop up box letting you know that the template's built in definitions and this is okay. The items that I adjusted are as follows:
This is located in both the VMware provided Taskbar and Windows Explorer Config templates. I commented them out in one of the locations. It doesn't matter which one.
This is located in both the VMware provided Taskbar and Start Menu Config templates. I commented them out in one of the locations. It doesn't matter which one.
If you are using the Windows Explorer template config provided by VMware, try adding the following to exclude the key that tends to cause the Start Menu to fail to show anything every other time.
Now my start menu will load every single time. Please let me know if you have any questions or have any ideas to add to what I already put down. I battled this for a couple of weeks so I understand your frustrations. Thanks!
PS - I created my image by following the guide from VMware on creating an optimized Windows Image with a few minor adjustments specific to our environment. I also used mandatory profiles.
What are the names of the DWORD entries?
My apologies. The DWORD entries that need to have their value data changed are all 'Start'. I will make sure to update my original post. Please let me know if you have any other questions. Thanks!
I disabled those four service starts and made the other three reg changes and our 1083 image with a mandatory profile is looking much better. All start menu changes are saving.
Any pointers on how to configure the initial start menu layout/contents for the mandatory profile?
What breaks when you disable these services? I mean the OneSync service says in the service itself:
This service synchronizes mail, contacts, calendar and various other user data. Mail and other applications dependent on this functionality will not work properly when this service is not running.
The WpnService handles notifications. I find that if you disable it you get no notification popups. Do you just accept that in your environment?