Just wrote about the KB how to update your administrative templates on your domain controller for easy access. For those who have not read the KB is probably not aware of the problem that most probably will occur.
“Namespace ‘Microsoft.Policies.Sensors.WindowsLocationProvider’ is already defined as a target namespace for another file in the store. File \\<domain name>\SysVol\<domain name>\PolicyDefinitions\microsoft-windows-geolocation-wlpadm.admx, line 5, column 110″
The problem is simply that the file LocationProviderADM.admx was renamed in Windows 10 as Microsoft-Windows-Geolocation-WLPAdm.admx.
The workaround?
- Simply ignore it
OR
- Delete the LocationProviderADM.admx and LocationProviderADM.adml files from the central store.
- Rename Microsoft-Windows-Geolocation-WLPAdm.admx to LocationProviderADM.admx
- Rename Microsoft-Windows-Geolocation-WLPAdm.adml to LocationProviderADM.adml
Reference KB: “‘Microsoft.Policies.Sensors.WindowsLocationProvider’ is already defined” error when you edit a policy in Windows
DeployWindows 
this was not necessary for me using the ADMX-Files from a german Win10 64bit in version 1511. Perhaps this was corrected in 1511?
LikeLike
Thanks for your reflection! This is not applicable for all scenarios as you say.
LikeLike