none
Windows 10 Group Policy Issue

All replies

  • Hi John,

    This issue can be caused by Remote Registry and DFS namespace services on the server.

    Please check the status of these two services and make sure they are set to start automatically.


    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    Thursday, November 05, 2015 7:08 AM
  • Hi,

    I've checked these services on both our DC's and they are fine.

    Setting the registry items as per the spiceworks article sorts it, but surely that can only be a temporary fix...

    The issue is only with Windows 10 machines.... Windows 7 and 8.1 are fine.

    Kind Regards,

    John

    Thursday, November 05, 2015 3:01 PM
  • Hi John,

    As can been seen from the link mentioned in your post, it is a known issue and for now, there is no solution yet. We will keep an eye on this and wait for the release of a solution.


    Please remember to mark the replies as answers if they help and un-mark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Monday, December 07, 2015 7:50 AM
    Moderator
  • Not really the answer..Kind of hoping for an update when this issues is resolved.
    Thursday, December 10, 2015 2:03 PM
  • Any update on this "known bug"...surely there must be a proper MS fix coming?
    Thursday, February 11, 2016 12:33 PM
  • Hi,

    Just a thought although it is apparently a known bug in windows 10 for UNC hardening to be enabled surely it should work...

    Just a thought... Our domain functional level is still server 2003 as when I put our last domain controller into action (we currently have server 2012 and server 2008 R2) we were getting rid of our last server 2003 servers. It would seem we are also using FRS rather than DFS.... Does UNC Hardening need DFS?

    Kind Regards,

    John

    Sunday, March 27, 2016 3:25 PM