Forum Discussion

Sergio_Raposo's avatar
Sergio_Raposo
Copper Contributor
Jul 30, 2023

Problem changing PDC

Hello, I have an environment with 3 DC's where I want to remove 1 DC. I manage to transfer all roles but whenever I disconnect the DC I want to remove I lose access to the AD and authentication star...
Active Directory
Windows Server
Sergio_Raposo's avatar
Sergio_Raposo
Copper Contributor
Aug 05, 2023

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 Patrick's avatar
Dave Patrick
MVP
Aug 05, 2023
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_Raposo's avatar
    Sergio_Raposo
    Copper Contributor
    Aug 06, 2023
    Hello,

    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 Patrick's avatar
      Dave Patrick
      MVP
      Aug 06, 2023

      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.  

        

       

      • Sergio_Raposo's avatar
        Sergio_Raposo
        Copper Contributor
        Aug 06, 2023
        Hello,

        The link for the files is this ... https://1drv.ms/f/s!Al6qCMQjnWZQmecAnI0kfOnzFkzCyA?e=2ONRru

        On the server to where i move the PDC role i found this:
        The DFS Replication service initialized SYSVOL at local path C:\Windows\SYSVOL\domain and is waiting to perform initial replication. The replicated folder will remain in the initial synchronization state until it has replicated with its partner EDOCCOM2.EDOC.local. If the server was in the process of being promoted to a domain controller, the domain controller will not advertise and function as a domain controller until this issue is resolved. This can occur if the specified partner is also in the initial synchronization state, or if sharing violations are encountered on this server or the sync partner. If this event occurred during the migration of SYSVOL from File Replication service (FRS) to DFS Replication, changes will not replicate out until this issue is resolved. This can cause the SYSVOL folder on this server to become out of sync with other domain controllers.

        Additional Information:
        Replicated Folder Name: SYSVOL Share
        Replicated Folder ID: 616342C9-9107-4C87-8FF3-BF1985A17368
        Replication Group Name: Domain System Volume
        Replication Group ID: F0046DA5-64B8-4D21-A281-C92A21BE55E6
        Member ID: 0E0F2930-7056-4D44-8EB5-5C07488B6DFC
        Read-Only: 0

        The DFS Replication service encountered an error communicating with partner EDOCCOM2 for replication group Domain System Volume.

        Partner DNS address: EDOCCOM2.EDOC.local

        Optional data if available:
        Partner WINS Address: EDOCCOM2
        Partner IP Address: 10.0.0.8

        The service will retry the connection periodically.

        Additional Information:
        Error: 1753 (There are no more endpoints available from the endpoint mapper.)
        Connection ID: F0046DA5-64B8-4D21-A281-C92A21BE55E6
        Replication Group ID: C2195BA6-6C4B-4F2E-AF1B-4E5D43C57DD3

        The DFS Replication service is stopping communication with partner EDOCCOM2 for replication group Domain System Volume due to an error. The service will retry the connection periodically.

        Additional Information:
        Error: 9033 (The request was cancelled by a shutdown)
        Connection ID: F0046DA5-64B8-4D21-A281-C92A21BE55E6
        Replication Group ID: C2195BA6-6C4B-4F2E-AF1B-4E5D43C57DD3

Resources