Hans Hard
asked on
GPO Edit --- Error: "Namespace Microsoft.Policies.Sensors.WindowsLocationProvider is already defined"
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
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-xx
Replication Group ID: 2B6FDF40-35EA-415F-A9E7-xx
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\dom
- do not have a Microsoft-Windows-Geolocat
- 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.
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
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-xx
Replication Group ID: 2B6FDF40-35EA-415F-A9E7-xx
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\dom
- do not have a Microsoft-Windows-Geolocat
- 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.
ASKER
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?
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-Geolocat
-Rename Microsoft-Windows-Geolocat
I do have a LocationProviderADM.admx (1.485 bytes) in C:\Windows\PolicyDefinitio
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-Geolocat
No AD server have Microsoft-Windows-Geolocat
(not in C:\Windows\PolicyDefinitio
Grateful for all and any help. /Hans
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 0It 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-Geolocat
-Rename Microsoft-Windows-Geolocat
I do have a LocationProviderADM.admx (1.485 bytes) in C:\Windows\PolicyDefinitio
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-Geolocat
No AD server have Microsoft-Windows-Geolocat
(not in C:\Windows\PolicyDefinitio
Grateful for all and any help. /Hans
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
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
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thankyou!
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 !