[1809, ou] U-EV Template Not being applied

[mdking]

Hi All,

 

We are looking into the functions of U-EV and our upcoming deployment of Windows 10 1809.

 

But we are finding the the templates are not being applied. We setup a Notepad template, but when we login into a domain PC as a user, this notepad template isn't being applied.

 

Any ideas?

 

Thanks

Matt

 

 

We have followed the post below for a basic u-ev setup:

 

From PeterH - Edugeek user.

 

"OK I have just spent the best part of the last week battling with UE-V on Windows 10. There are a number of caveats and in our experience it is less than perfect, but the general configuration outlined below seems to work for us.

 

So to start with, UE-V is part of the latest builds of Windows 10. There is no agent to install - it is already there and simply needs switching on. To configure UE-V, it is best done with group policy. Again, if you are using the latest Windows 10 ADMX templates, the UE-V configuration items will be there already.

 

Firstly to configure UE-V, you will will need two network shares on a server somewhere. The first one is the Settings Storage Location, which is where each user's UE-V settings packages will be stored. The second is the Settings Template Catalogue, which contains the settings templates. These tell UE-V where each application stores is settings, so it knows which file / registry locations to sync. You can find a guide to creating these and the permissions you need here: https://docs.microsoft.com/en-us/mic...-2x-both-uevv2. However the permissions specified in that document did not work for us! So this is what we used to get it working:

 

Settings Storage Location (e.g. \\server1\uev-settings)

 

Share Permissons

 

Domain Admins: Full Control

Domain Users: Full Control

 

NTFS Permissions

 

Domain Admins: Full Control: This folder, subfolders and files

Domain Users: List folder / Read Data, Create Folders / Append Data: This folder only

Creator Owner: Full Control: Subfolders and Files Only

 

Settings Template Catalogue (e.g. \\server1\uev-templates)

 

Share Permissions

 

Domain Admins: Full Control

Domain Computers: Full Control

 

NTFS Permissions

 

Domain Admins: Full Control: This folder, subfolders and files

Domain Computers: Modify: This folder, subfolders and files

 

Once you have created your shares, you can configure UE-V using group policy. UE-V is configured in both Computer Configuration and User Configuration. There are a number of settings you will find in Administrative Templates / Windows Components / Microsoft User Experience Virtualization. The settings we made are as follows. Some things can be configured both in Computer and User configuration, so I'm not sure which is best practise, but the following works for us:

 

Computer Configuration

 

Sync Method: None (note that this actually disables the UE_V Sync provider and establishes a direct file connection to the settings storage path. In testing, we found this to be much more reliable)

Enable UEV: Enabled (note the auto-register inbox templates option doesn’t seem to work on Windows 10 1709, some searching online suggested this is no longer supported)

First Use Notification: Disabled

Settings Template Catalog Path: e.g. \\server1\uev-templates

Sync unlisted Windows apps: Enabled

Synchroinze Windows Settings: Enable all

Tray Icon: Disabled

Use user Experience Virtualisation: Enabled

 

 

 

User Configuration

 

Do not synchronise Windows Apps: Disabled

Settings Storage Path: e.g. \\server1\uev-settings\%username% (note you need %username% to create a folder for each user in the settings storage location)

Synchronise Windows Settings: Enabled

Use User Experience Virtualisation: Enabled

 

 

 

Having created all of the above, you need to copy the Microsoft UEV settings templates from a Windows 10 computer into your settings template catalogue share. On 1709, these may be found in C:\ProgramData\microsoft\uev\inboxtemplates - just copy the files over.

 

If you need any additional settings templates, there is a settings location template gallery here: https://go.microsoft.com/fwlink/p/?LinkID=246589. There are some templates to help with roaming desktop settings and pinned items on the taskbar and so on.

 

Reboot one of your workstations and you should find UE-V is working. You can use Powershell to test it, the following commands may be useful:

 

Get-UevConfiguration: This should show that SyncEnabled is True and it should show the settings storage path and the settings template catalog path that you configured in GPO

 

Get-UevTemplate: This should display a list of imported UEV templates and will confirm that your settings template catalog path is working correctly.

 

Finally, as each user logs in, it should create a folder for that user in your UEV Settings Location, containing the settings packages for that account (note that these are in hidden folders so you will not see them unless you are showing hidden files/folders in explorer)

 

 

There are a few additional items you can set in the registry to configure the UE-V agent. These are all in HLKM\Software\Microsoft\UEV\Agent\Configuration:

 

RepositoryOwnerCheckEnabled:REG_DWORD=1 (see https://docs.microsoft.com/en-us/mic...-2x-both-uevv2)

 

WaitForSyncOnLogon: REG_DWORD: 1 and WaitForSyncOnApplicationStart: REG_DWORD: 1 (we found setting these seemed to make syncing of pinned taskbar items more reliable)

 

There are a few issues we have discovered and there will be other things I'm sure that crop up:

 

Roaming Outlook profiles with UE-V is not supported (see https://support.microsoft.com/en-gb/...-not-supported). You may have issues with roaming Outlook signatures also, because the default signature is referenced in the Outlook profile.

Roaming IE Favorites with UE-V works OK, but Edge Favorites don't roam and is not supported and neither do any other Edge settings. Thanks Microsoft. No wonder people are switching to Chrome.

We still have a few issues roaming Office 2016 toolbar settings, which don't seem to work very reliably."

[midweek]

I'm just testing UEV too and found I had to register the UEV templates using powershell - https://docs.microsoft.com/en-us/powershell/module/uev/register-uevtemplate?view=win10-ps

 

This may or may not be necessary but it worked for our Chrome template so worth a shot.

 

Now to figure out how to keep the local profile creation time to a minimum for pupils/staff who use lots of different machines!

[OverWorked]

I had a similar issue with templates not being registered.

 

I found that gpupdate /force, then restarting fixed it.

 

I'm not sure why this worked. I think that forcing the gpupdate also forced the recreation of the UE-V Template Auto Update scheduled task, thought I found that manually starting the task didn't register the templates.

[techy32]

We are testing UEV which is not working for us and also unable to register the templates... getting error message.... the UEV service is not starting on windows 10 v1903 (tried manually / with local GPO )... any help?

[BrynJones216]

The group policy settings with a central template repository only refresh the policies when the "Template Auto Update" scheduled task runs (under Task Scheduler Library > Microsoft > UE-V) . This task is only set to trigger at 3:30am, when the computer starts, and when the task itself is created/modified.

I have no idea what happens if you run it manually while logged in. I suspect it probably isn't a good idea to add or modify a settings template for an application, while that application is actually running.

[OverWorked]

Do you also have a "UE-V Register Inbox Templates" scheduled task (probably disabled)?

 

I've also found in a few stubborn cases that logging on as admin then enabling and running that task manually fixes it. It disables itself again, but should only need running once.

 

There may be a brief Powershell window open while the script runs. Then restart the machine.

Edited July 10, 2019 by OverWorked

[techy32]

Do you also have a "UE-V Register Inbox Templates" scheduled task (probably disabled)?

 

I've also found in a few stubborn cases that logging on as admin then enabling and running that task manually fixes it. It disables itself again, but should only need running once.

 

There may be a brief Powershell window open while the script runs. Then restart the machine.

I will check it on Monday...