Our domain has two 2012 DC, one 2012 R2 DC, and one 2008 DC.
Only one DC has this problem (the 2012 DC that is not the PDC).
When one opens gpmc.msc and focus at the root of the domain, and on the Status tab click Detect Now.
A processing error occurred collecting data using this base domain controller. Please change the base domain controller and try again.
As per:
GPMC reports a Processing Error while trying to detect DCs
https://support.microsoft.com/en-ca/kb/2891966
1) DsGetDcName is reading the name information from HKLM\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Hostname.
Check the hostname entry, convert it to All CAPS and then restart the netlogon service on the DC to fix the problem.
Sure enough the other 2012 DC (the PDC) had a lower case name, so I changed to upper case and restarted Netlogon service.
The error continued on the one DC.
Overnight all DCs were restarted due to WSUS updates.
The error continues on this one DC.
2) You should also check the below locations to make sure there is no deleted or conflict references for the fSMORoleOwner Attribute. You would get the same errors if you have a bad entry for this attribute reference.
Places to be checked:
1. Open ADSIEdit and connect to DC=DomainDNSZones,DC=Domain,DC=com.
Right click the object CN=InfraStructure
Look for the attribute fSMORoleOwner and verify it is pointing to the right FSMO holder.
The values show the PDC is listed in the wrong Site Location.
Unfortunately a prior administrator physically moved the DC with all the FSMO roles back in 2014, without demoting and re-promoting it. We have had several issues due to this bad move.
So my question is: is it ok to manually change the name of the site to correctly reflect the 'new' location of the DC?
It really does not explain though why only the one DC would have a problem while the others are fine.
Advice is appreciated thank you.
Andy