none
User Settings Sync not working with Windows 10 1607 RRS feed

  • Question

  • I recently clean installed a few test computers straight to 1607 to see what the "automated" experience will be like.  These computers all previously worked seamlessly so I know the permissions are all set correctly on the storage.  However it will not sync any windows settings.

    Looking at this guide: https://technet.microsoft.com/en-us/itpro/windows/manage/uev-upgrade-uev-from-previous-releases

    I do see all the correct settings in powershell (the paths are set through group policy) but the registry location does not contain any paths so not sure if that is the cause.

    It is syncing my templates, just not the windows settings even though those are in my folder.


    Wednesday, August 3, 2016 3:19 PM

All replies

  • I don't have any help, but I can report that I'm seeing the same behavior
    Wednesday, August 3, 2016 4:24 PM
  • Running Get-UevTemplate shows custom templates, but does not show the DesktopSettings template that I believe is supposed to be built-in and enabled when the policy is set.

    Unless it works some other way......

    Wednesday, August 3, 2016 4:58 PM
  • I'm having a similar issue but even my custom templates don't register.

    I have to manually register both the default and the custom templates - they're defaults are present in c:\programdata\microsoft\uev\inboxtemplates, but they don't exist in c:\programdata\microsoft\uev\templates until you run the command

    "register-uevtemplate C:\programdata\microsoft\uev\inboxtemplates\templatename.xml".

    The template then gets copied to c:\programdata\microsoft\uev\templates and appears when I run get-uevtemplate.

    Like you though I'm not sure if this is how it's meant to work!


    • Edited by NickyMayB Thursday, August 4, 2016 10:40 AM
    • Proposed as answer by lforbes Thursday, February 16, 2017 11:37 PM
    Thursday, August 4, 2016 9:03 AM
  • Figured out why my custom templates weren't loading - my own fault! (https://social.technet.microsoft.com/Forums/en-US/4ea4904f-e705-4682-a8a8-91462422e737/windows-10-build-1607-uev-templates-dont-register-automatically?forum=mdopuev)

    So it looks like I do have exactly the same problem.

    I guess we could work around it by copying the default templates to the custom settings template catalog folder, and then setting "replace the default Microsoft templates" to "enabled" in the GPO.

    Doesn't seem like we should have to do this though...

    • Proposed as answer by NickyMayB Monday, August 8, 2016 2:58 PM
    Thursday, August 4, 2016 3:01 PM
  • This is the work-around that I'm testing currently. Not a great answer and I agree we shouldn't have to, but gotta make it work, amiright?

    • Proposed as answer by NickyMayB Monday, August 8, 2016 2:58 PM
    Thursday, August 4, 2016 3:20 PM

  • This seems to be working OK for us, so it's what we'll go with for now! Hope it's working for you too.

    Reading between the lines of the documentation, I think the need to manually register the local templates is implied, though not very clear - this article https://technet.microsoft.com/en-us/itpro/windows/manage/uev-upgrade-uev-from-previous-releases?f=255&MSPPError=-2147217396 mentions that you have to re-register the Notepad template, and this one https://technet.microsoft.com/en-us/itpro/windows/manage/uev-deploy-uev-for-custom-applications says "Important: After you enable the UE-V service, you’ll need to register the settings location templates using the Register-UevTemplate cmdlet in Windows PowerShell".

    Guess this is very early days for 1607 in any sort of enterprise environment so hoping this stuff gets ironed out before we actually try to go live with it...

    Monday, August 8, 2016 3:07 PM
  • This work-around is doing fine for us too.

    As UE-V is pretty much exclusively an enterprise solution, I would hope that Microsoft realizes that requiring the templates to be registered locally per machine is a bit unwieldy/unsustainable. Also, what's the point of having group policy settings if they don't actually do anything (like activate the appropriate built-in template).

    For better or worse, I have to start going live with it nearly immediately (long story), so here's hoping it continues to work and that the work-around doesn't cause issues when they fix it and GPO starts working.

    Monday, August 8, 2016 4:55 PM
  • I will give it a go too but agreed with the others that this needs to be automated (either through group policy or some other mechanism).

    I almost wonder if the preferred solution will be to ultimately control everything with templates and they just release a "theme settings" template that we keep with the others.  Especially makes more sense since the company settings front end is no longer there.

    Monday, August 8, 2016 8:31 PM
  • Count me in as affected by this, as well. I had been testing using a custom catalog path on a network share, which was working, but if I test UE-V without that catalog path listed, instead relying on enabling specific Windows apps in the GPO, absolutely no templates are being registered, and thus nothing is being sync'd. This is just one of the little issues I see with this new version of UE-V.

    Edit: I guess I posted too soon. If I enable the custom catalog path in the GPO, but specify the local path ("%allusersprofile%\Microsoft\UEV\InboxTemplates"), some of the templates do get copied to the folder. Specifically, the Office, Outlook, and Skype templates (all 2016) get copied, but no others, even though I have other apps enabled, like calculator and Wordpad, as well as the desktop theme.

    • Edited by NTP66 Friday, August 26, 2016 1:40 PM
    Friday, August 26, 2016 1:14 PM
  • Do you mind me asking, what other issues are you seeing with the new 1607 embedded UE-V?  We haven't done much formal testing yet, wouldn't mind knowing if there are specific glitches to look out for.  Thanks!
    Friday, August 26, 2016 1:30 PM
  • Do you mind me asking, what other issues are you seeing with the new 1607 embedded UE-V?  We haven't done much formal testing yet, wouldn't mind knowing if there are specific glitches to look out for.  Thanks!
    The biggest issue is the fact that Microsoft's native UE-V restore commands are not working as explained in the documentation. I actually posted a detailed thread on the issue yesterday (link).
    Friday, August 26, 2016 1:33 PM
  • Saw that just after I asked the question!  I will try to repeat your findings next week - I'll post on that other thread if I get anywhere.
    Friday, August 26, 2016 2:07 PM
  • Do you mind me asking, what other issues are you seeing with the new 1607 embedded UE-V?  We haven't done much formal testing yet, wouldn't mind knowing if there are specific glitches to look out for.  Thanks!

    The biggest issue is the fact that Microsoft's native UE-V restore commands are not working as explained in the documentation. I actually posted a detailed thread on the issue yesterday (link).

    I have noticed that as well.  Seems UEV still needs quite a bit of work before its ready for primetime.  The idea is really great when used in conjunction with folder redirection but its just too unstable and too many issues currently.  Will be keeping it in testing only and hopefully they can improve some things via windows update.
    Wednesday, September 7, 2016 1:13 AM
  • Ways to register inbox templates are
    1. Register-UevTemplate for each of the inbox templates available at c:\programdata\Microsoft\uev\inboxtemplates
    2. Copy the templates from c:\programdata\Microsoft\uev\inboxtemplates to template catalog store. Set the template catalog path in GPO and select to replace MS Templates. If you are not using GPO, then you can use set-uevconfiguration to set the template catalog path and update the registry value 'OverrideMSTemplates' to 1 under the key hklm:\software\microsoft\uev\agent\configuration


    Friday, September 23, 2016 9:52 PM
  • While this does work, as indicated in prior posts, the issue is that we should not have to do this manually - especially if we are not using a GPO to specify custom templates. This isn't how the previous version of UE-V worked, and in an enterprise environment, it definitely isn't how it should work in Windows 10.
    Monday, September 26, 2016 12:03 PM
  • I'm seeing exactly the same problem with clean 1607 installations.

    Please could Microsoft confirm if this is "by design" given 1607 is now Current Branch for Business. Like the others on this thread I don't think this is workable in an enterprise environment where we want to manage UE-V via GPO.

    Thanks


    Douks

    Thursday, December 1, 2016 11:52 AM
  • Yea maybe somebody can help me. UE-V is working on 7 32 and 64, 8, 8.1 (32 and 64 bit), Windows 10(32 and 64bit) but not on any windows 10 1607 32 or 64 bit. We use no custom setting templates. Made sure UE-V has the proper configuration, but the desktop setting do no sync. When I applied a custom template and registered it works perfectly but the Windows desktop setting still don't sync. Any help would greatly be appreciated. 
    Monday, December 12, 2016 6:49 PM
  • As Lakshmi Kiranmayi Yeddanapudi says - you have to manually run the "register-uevtemplate" command against each of the templates in the inboxtemplates folder, e.g.

    register-uevtemplate C:\programdata\microsoft\uev\inboxtemplates\templatename.xml

    You'd need to script this on every client.

    Either that or use the workaround that cyrandir and I suggested of putting the default templates in a custom template location and using the GPO to specify the path to them.  That's what we're using in the meantime.

    It's a change in behaviour from earlier OS/UE-V agent versions and it's not clear whether it's by design or a bug, but it is what it is for the time being.

    • Proposed as answer by rahine Tuesday, December 13, 2016 7:55 PM
    • Unproposed as answer by rahine Tuesday, December 13, 2016 7:55 PM
    • Proposed as answer by Lakshmi Kiranmayi Yeddanapudi Wednesday, January 4, 2017 1:05 AM
    Tuesday, December 13, 2016 4:32 PM
  • I don't think we have an answer until MS confirm if this is by design.

    Douks

    Thursday, January 5, 2017 1:47 PM
  • Hi,

    It is in the documentation that you must register templates manually. https://technet.microsoft.com/sv-se/itpro/windows/manage/uev-getting-started

    Regards,
    Jörgen


    -- My System Center blog ccmexec.com -- Twitter @ccmexec

    Wednesday, January 18, 2017 1:41 PM
  • Hi,

    Thanks for your feedback and we will be making a change to activate the MS templates automatically via GP in an upcoming Windows release.

    Regards,

    Tommy N

    UE-V Team

    Wednesday, February 8, 2017 8:06 PM
  • I am having the same issue. We have 35,000 machines Windows 10 1607 and UEV set by policy. The LOCAL DEFAULT Microsoft Templates are not showing up at all.

    I have run the UEV Tasks while logged on and they are running fine without errors.

    My custom templates are there and registered. My storage location is fine. Everything looks like it should be working.

    NickyMayB<abbr class="affil"></abbr>above actually provided the default location of the Microsoft Templates that wasn't included in any of Microsoft's Documenation anywhere. I will copy to the custom template location and see if that works.

    • Edited by lforbes Thursday, February 16, 2017 11:44 PM fix info
    Thursday, February 16, 2017 11:30 PM
  • THANK YOU! I have literally been pulling my hair out about this for weeks. I have read all the documentation three times on UEV for Windows 10 1607 and no one ever in any of the articles mentioned this.

    They said that the notepad template would have to be re-registered but not the location that the templates even were or the name or anything.

    I will now copy those from the default location above to our custom template share and see if that enables them to automatically register.

    This is a big oversight from Microsoft. UEV is an Enterprise Solution. It is unfeasible to think organizations can run powershell commands to register templates on thousands of computers when Group Policy is available and should be able to do it.

    I found it funny that my Chrome settings roamed by copying the custom chrome template to the custom location but my Windows settings did not.

    So I tried copying them to the Template Share and running the

    "register-uevtemplate C:\programdata\microsoft\uev\inboxtemplates\templatename.xml".

    And so far they are still not appearing in the C:\ProgramData\Microsoft\UEV|Templates nor in the get-uevtemplate.

    Maybe the service needs a hotfix.


    lforbes


    • Edited by lforbes Friday, February 17, 2017 1:35 AM
    Thursday, February 16, 2017 11:41 PM
  • The Microsoft ones are supposed to be automatically registered when you enable the UE-V service via Group Policy. It is definitely broken.

    https://technet.microsoft.com/en-ca/itpro/windows/manage/uev-prepare-for-deployment

    Desktop applications synchronized by default in UE-V

    When you enable the UE-V service on user devices, it registers a default group of settings location templates that capture settings values for these common Microsoft applications.


    lforbes

    Thursday, February 16, 2017 11:50 PM
  • It sounds like a hotfix for the UE-V Service is needed. The Service should register the default group of templates when enabled. This is not happening.

    The Microsoft ones are supposed to be automatically registered when you enable the UE-V service via Group Policy. It is definitely broken.

    https://technet.microsoft.com/en-ca/itpro/windows/manage/uev-prepare-for-deployment

    Desktop applications synchronized by default in UE-V

    When you enable the UE-V service on user devices, it registers a default group of settings location templates that capture settings values for these common Microsoft applications.


    lforbes

    Thursday, February 16, 2017 11:52 PM
  • As has been mentioned, why is this not better documented?

    So, yes, I can now manually register the templates and I hear there is an update to GP in the next release.

    However, I have found that templates need re-registering. For some reason some synchronizations stop and on investigation I find some, not all, templates are no longer registered.

    I'm sure I'm not the only one here who's enterprise migration to W10 is on hold now until this is resolved and reliably enforced.

    Friday, February 17, 2017 10:36 AM
  • Hi,

    Thanks for your feedback and we will be making a change to activate the MS templates automatically via GP in an upcoming Windows release.

    Regards,

    Tommy N

    UE-V Team

    Any chance you can be more specific? Is this going to be in a hotfix that nobody will know about unless they search? Version update? Windows 10 security update? Also, any chance Microsoft will include the fix for the restore commands not working properly, as seen in this thread?
    Friday, February 17, 2017 11:44 AM
  • Tommy, what is the story here?  You haven't replied to the multiple requests for clarification.  Is this coming in a hotfix or not?

    FWIW we run LTSB (1607) and also have the issue.  Need to know if a fix will be pushed via Windows Update or if we'll be stuck until the next major release.

    Thursday, May 25, 2017 6:41 AM
  • We disagree 100% in our organization. we would HATE if all templates auto-registered. We register templates on a per-machine per-application basis. 

    You say " I would hope that Microsoft realizes that requiring the templates to be registered locally per machine is a bit unwieldy/unsustainable. " However... I am really confused by your comment. Enterprise SHOULD have a way to run commands on mass on their machines, either at build time (MDT/SCCM/Image), Post build time (SCCM/GPO/login script). If you really wanted to you could even do this with a login script (even though I wouldn't). For us in our organization the UEV template registration is part of the Image AND application deployment process. when machines are imaged in MDT/SCCM the common settings templates (windows settings, office 2016 [word, excel, outlook], notepad, quick access) get registered automatically by script. When we install each application on a per user build basis (also done out of MDT/SCCM by script) that additional settings template is registered on that machine only, for example in our AutoCAD silent SCCM install script, it registers the template.

    Registering ALL your organizations templates, even on machines that dont contain the software, seems crazy to me and registering on a per machines basis is TOTALLY the right way to do things. 

    Friday, June 2, 2017 10:30 PM