New
#1
On updated to 1511 machines gpedit.msc reports namespace conflict
It looks like it began after the update to 1511, but I'm not sure about that. Maybe it happened sometime earlier, since I don't use gpedit.msc too often. A computer with clean install of 1511 does not suffer from this problem.
Anyway, trying to run gpedit.msc now results in "Namespace 'Microsoft.Policies.Sensors.WindowsLocationProvider' is already defined as the target namespace for another file in the store" error message (reported twice).
After clicking OK in that message window, Policy Editor continues to work properly. Apparently we are looking at the same issue as the one described by Microsoft here
https://support.microsoft.com/en-us/kb/3077013
Indeed, my policy store has both LocationProviderADM.admx and Microsoft-Windows-Geolocation-WLPAdm.admx, referring to the same namespace (no .adml files though).
Files at that location are protected and not immediately deletable and renamable. What would be the proper way of deleting and renaming these files? Restarting into repair console?