GPO Edit --- Error: "Namespace Microsoft.Policies.Sensors.WindowsLocationProvider is already defined"

Hans Hard
Hans Hard used Ask the Experts™
on
Okay, this bug has kept me busy for quite some time. Grateful for all the help.

For starters, everything works. roughly-ish.

I have an AD with 4 servers, all of them are 2012R2. I think the servers have been upgraded sometime before I started working here and that may be the problem.

When I edit a GPO, I often get the error message: Namespace Microsoft.Policies.Sensors.WindowsLocationProvider is already defined as the target namspace for another file in the store. And a link to our sysvol share. After that, I can't edit or see settings on the GPO.

Things I've tested:

1. Executed the dcdiag command on the domain controller:
Starting test: DFSREvent
   There are warning or error events within the last 24 hours after the
   SYSVOL has been shared.  Failing SYSVOL replication problems may cause
   Group Policy problems.


2. Checked event logs and found this error message ... even though there are messages that the sync is actually working. I don't understand this. We have not run out of disk space.
The DFS Replication service encountered an error communicating with partner server02 for replication group Domain System Volume.
 
Partner DNS address: server02.int.xxxxx.se
 
Optional data if available:
Partner WINS Address: server02
Partner IP Address: 10.0.0.16
 
The service will retry the connection periodically.
 
Additional Information:
Error: 14 (Not enough storage is available to complete this operation.)
Connection ID: 98EB60E4-BED1-46F2-90C6-xxxxxxxx
Replication Group ID: 2B6FDF40-35EA-415F-A9E7-xxxxxxxx


3. I read that I was able to test the health of DFSR by installing DFSR management tools. After installing this and running the diagnostics, the tests say everything is ok. hu?

4. This folder on the server C:\Windows\SYSVOL_DFSR\domain\Policies\PolicyDefinitions
- do not have a Microsoft-Windows-Geolocation-WLPAdm.adml file.
- do have a LocationProviderADM.adml
Is that normal?

5. I think i should use a command called repadmin but don't know how.

Grateful for all the help.
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Shabarinath RamadasanInfrastructure Architect

Commented:
repadmin /replsummary from an elevated command prompt will give you AD Replication Status. But thats going to be specific to AD Database Replication health.

Looking from the error, it points to be an issue on the ADML.

See if this KB is helpful.
https://support.microsoft.com/en-in/help/3077013/microsoft-policies-sensors-windowslocationprovider-is-already-defined

Cheers !

Author

Commented:
Thanks for the reply!

The link you attached describes exactly the problem I have. But for server 2012R2 and the error makes it impossible to edit GPOs.

OK, so my AD Replication Status looks pretty good?

Source DSA          largest delta    fails/total %%   error
 xxxxxx3                   39m:36s    0 /   5    0
 xxxxxx4                   43m:13s    0 /  10    0
 xxxxxxxx2                 41m:32s    0 /  10    0
 xxxxxxxx3                 47m:20s    0 /   5    0


Destination DSA     largest delta    fails/total %%   error
 xxxxxx3                   43m:13s    0 /   5    0
 xxxxxx4                   39m:36s    0 /  10    0
 xxxxxxxx2                 47m:20s    0 /  10    0
 xxxxxxxx3                 41m:33s    0 /   5    0

Open in new window


It may be that an external consultant, before me, has tried to follow this guide, without success: https://support.microsoft.com/en-in/help/3077013/microsoft-policies-sensors-windowslocationprovider-is-already-defined

It is about replacing two files, like this:
-Delete the LocationProviderADM.admx and LocationProviderADM.adml files from the central store.
-Rename Microsoft-Windows-Geolocation-WLPAdm.admx as LocationProviderADM.admx.
-Rename Microsoft-Windows-Geolocation-WLPAdm.adml as LocationProviderADM.adml.


I do have a LocationProviderADM.admx (1.485 bytes) in C:\Windows\PolicyDefinitions on all DC servers.

On server G2 and G3 i have LocationProviderAdm.adml (1,212 bytes) from ‎November ‎21, ‎2014, ‏‎7:54:08 AM
On server A3 (DC) and A4 i have LocationProviderAdm.adml  (1.212 bytes) from 30. ‎september ‎2013, ‏‎23:20:00

No AD server have Microsoft-Windows-Geolocation-WLPAdm.admx
No AD server have Microsoft-Windows-Geolocation-WLPAdm.adml
(not in C:\Windows\PolicyDefinitions nor in C:\Windows\PolicyDefinitions\en-US)

Grateful for all and any help. /Hans
Shabarinath RamadasanInfrastructure Architect

Commented:
Hello Hans,

Replication looks good. It looks mostly an issue with the ADMX templates.
 
https://techcommunity.microsoft.com/t5/itops-talk-blog/step-by-step-managing-windows-10-with-administrative-admx/ba-p/842926

Refer the steps on getting the Windows 10 ADMX templates moved to SYSVOL.
Copy the existing files safely and try getting the new files to Sysvol.

I dont have a test domain now, hence couldnt try it out from my end.

Cheers
Big thanks to all the answers.

Since this was critical, I had to take extreme measures. In fact, read the error message properly. It is the wrong file. :(

Very close... but not right.

With the correct file name I could find there was a manual backup file in sysvol. Both files are read by GPEdit.

After removing the manual copy, we can now for the first time since 2017 edit the existing GPOs. Hurray.

Thanks for helping everyone.

(will buy an extra set of eagle eyes)

Author

Commented:
Thankyou!

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial