I personally stay away from WV and use UEM. ITs much easier to manage and troubleshoot issues with users profiles and data.
IS there a specific reason you are using WVs?Mike_A
I've tried capturing the start menu with both 2.10 and 3.x it seems like that it's not possible, I think this is a Microsoft issue the interface is tied to a .edb file some sort of mini database:
Other vendors have run into the same problems. My final solution was to capture only the files and folders basically the old style start menu (either with WV or UEM) and leave out the new metro style tiles interface. You can create an .xml export and apply this with a GPO to create sort of like a mandatory tile interface. Customize Windows 10 Start with Group Policy (Windows 10)
BTW: there is a anniversary release coming from Microsoft, I'm hoping that this will fix the issue.
I'm having the same issue.
I have figured out the same thing as HuibDijkstra, Microsoft needs to come up with a few fixes for enterprise administration with Windows 10 in the enterprise.
I have talked to a lot of experts and combed the internet and found that you can't do anything with Start Layout but to lock it down and only allow the user to make changes to desktop and all programs locations.
Hopefully there will be a August release and they will have these fixes implemented.Mike_A
Anniversary update 1607 is confirmed that still has the issue. Ticket is open with Vmware since we got hit with this today Running Vmware horizon 7.0.1 and persistent disks for the non-roaming profiles. Really hoping Vmware can help with this quickly. We're digging through all the GPO we have that customize the start menu in Windows 10 in an effort to narrow it down, but we're pretty much shooting in the dark and trying to fix the symptom at this point.
We actually had two problems we think, still in the post-diagnostic stage, but we found out that the Windows 10 start menu issue was fixed by disabling USB restriction security in Dell Desktop Authority. We also had a profile corruption issue too, but we rebuilt the gold image and appeared to have fixed the corruption from the persistent disk by doing that.
What did you have to do where you say "capture only the files and folders basically the old style start menu"? I'm using writable volumes. Any instructions you could share? I've been beating my head against this for a week. Last thing hanging me up before testing for deployment. Thanks for any help!
Late to the party but hey .
I've just tested 2.11 with Anniversary version of W10 and my startmenu works like a charm..
What edition of Windows 10 are you using (Pro, Enterprise, or LTSB)?Mike_A
W10 64 bits Enteprise. We didn;t do any customization to the start menu though at least not the tiles part.
Check out Blog post: Managing Windows 10 with VMware User Environment Manager - VMware Blogs
The following is pulled from the start menu section. I have decided to not include STEP 3 as it does not work. I have seen multiple environments that do not work for this. What you need to do instead is to create a small PS1 script to launch at login that just loops and runs the export command on an interval (I use 60 Seconds)
Sample PS1 code
$test = $true
export-startlayout -path "$env:localappdata\Microsoft\Windows\Shell\Layoutmodification.xml"
That will run the export every 60 seconds. I have been doing this for some time now and it has been running just fine.
Step 1. Add Exclusion to Windows Explorer.INI
Add the following exclusion to the User Environment Manager configuration file called Windows Explorer. This exclusion prevents the Start Menu icons from appearing blank or disappearing.
Step 2. Create New User Environment Manager Config File to Roam the Start Menu
Create a new User Environment Manager configuration file called Windows 10 Start Menu. This will allow User Environment Manager to export and import the Start Menu layout at logoff and logon. Add the following content to the User Environment Manager configuration file:
NOTE: this fix makes it to where you can't remove Edge from the task bar.
I've had plenty of start menu errors with our Windows 10 VDI deployment. A lot of the users mention the Appdata/Local area above me, so I wont list my problems with that. One issue that I found in our environment is that if you disable the windows firewall service it will break the start menu.
I thought this was fixed with the latest App Volumes 2.12 release, but we have seen the problem on Win10 Anniversary 1607 and AppVol 2.12. The problem seemed to go away once the user removed Edge from the start menu and logged out and logged in.