Forum Discussion
Problem changing PDC
Might check the results
netdom query fsmo
Dave Patrick I already did that and the roles are in the DC's to where i moved them and it seams that everything is alright. But every time i query the domain (ping -a <domain>) the IP that i receive is from the DC that i want the remove and when I use netdom query fsmo it point the PDC is the new server. Another thing is that when the roles are in the new server's if i shutdown the DC I want to remove i lost the Active Directory. To regain access again i have to start the old DC. I have done transfer the role without problem, i have seized the role but nothing worked.
- Dave PatrickAug 05, 2023MVP
if i shutdown the DC I want to remove i lost the Active Directory.How are you verifying this? Might also check the DHCP server hands out the addresses of healthy domain controllers.
- Sergio_RaposoAug 06, 2023Copper ContributorHello,
I don't have DHCP in the DC's. All the VM's are in Azure and the have fixed IP and DNS server are configured in the network configuration. To identifiy which DC'a have the PDC i run Get-ADDomainController -domainname edoc.local -Discover -Service PrimaryDC and nltest /dsgetdc:edoc.local. When the role is hosted by the DC that i want to remove works fine. When i change the PDC role to another DC i start to get this error:
Get-ADDomainController : The specified domain either does not exist or could not be contacted
At line:1 char:1
+ Get-ADDomainController -domainname edoc.local -Discover -Service Prim ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : ObjectNotFound: (:) [Get-ADDomainController], ADException
+ FullyQualifiedErrorId : GetADDomainController:BeginProcessingOverride:DiscoverDC:1355,Microsoft.ActiveDirectory.Management.Commands.GetADDomainController- Dave PatrickAug 06, 2023MVP
Please run;
Dcdiag /v /c /d /e /s:%computername% >C:\dcdiag.log (run on PDC emulator)
repadmin /showrepl >C:\repl.txt (run on **any** domain controller)
ipconfig /all > C:\%computername%.txt (run on **EVERY** domain controller)
ipconfig /all > C:\problemworkstation.txt (run on problem pc)
Also check the domain controller System and Replication (DFS or FRS) event logs for errors since last boot. Post the ***Event Source*** and ***Event IDs*** of any found. (no evtx files)
then put `unzipped` text files up on OneDrive and share a link.