In this blog post I want to share my top 3 favorite/informative UEM Community Forum discussions of June 2017. Yeah, I know June isn’t over yet. But I want to share the following 3 discussions because they are worth sharing already and I may add another blog post later on for the second part of June ;-)
#3 - New 9.2 Microsoft Edge Flex Config - Issues
Key takeaway: How to make Microsoft Edge Flex Config File work
Forum user pchapman reported:
Tried out the new FlexConfig included in 9.2 for Microsoft Edge. It does seem to capture the settings, but doesn’t appear to restore them properly. Has anyone been successful getting Edge to work with UEM?
Pim_van_de_Vis his answer:
DirectFlex needs to be enabled, otherwise the UEM config file for Edge will not work. The settings need to be imported at application start, and not at logon. If you import them at logon, the settings will be overwritten bij Edge again. I have configured DirectFlex as the screenshot below and that works for me.
Export will always happen at logoff, because UEM does not see the Edge application close. In order to test you need to logoff first for the export to be succesfull.
#2 - Privilege Elevation
**Key takeaway: **How to exactly configure/use privilege elevation
Trying to get path-based elevation to function so that users who are not administrators can install software.
I enabled privilege elevation from global configuration and created a privilege elevation rule.
I created a path-based user-installed application rule and specified a network share that contains exe files for users to install.
During testing when I attempt to install a software I get the “you must be logged in as an administrator” error message.
Any help would be appreciated!
Are you using the exact same path for executing the installation? If you configured FQDN in the path name, make sure you use it. Also make sure that you do not use a mapped drive to that path.
For instance, if you configured \Share\Software , make sure you use \Share\Software\install.exe
#1 - FIXED! Roam the Windows 10 Start Menu in your VDI environment
Key takeaway: How to roam the Windows 10 (1703) start menu using the registry
Pim_van_de_Vis shares this awesome post:
Roaming the Start Menu layout, including all personalized tiles is still very hard to accomplish. The Start Menu in Windows 10 was stored in a database which was locked and could not be copied. With the Microsoft released Windows 10 version 1703 Creators Update, the Start Menu is no longer stored in a database, but stored in the registry. This makes it possible to roam the Start Menu again.
This article explains how to roam the Start menu layout by using VMware User Environment Manager. Note: This solution only works on Windows 10 version 1703 or later.
To allow users to personalize their Windows 10 Start Menu and roam those personal settings, a new UEM Configuration item needs to be created using the UEM Management Console:
Click Create Config File and select Create a custom config file and give it a name. On the Import/Export tab, paste these two lines:
Save the UEM Config file.
You can now customize and personalize your Start Menu, including pinning tiles to local apps, modern AppX apps, group tiles, resize, and re-order.
Note: Roaming the Start Menu with this approach even allows for roaming between 32-bit and 64-bit.
Also see this KB I just created: https://kb.vmware.com/kb/2150422