none
domain replication issues - old sbs 2003 to new sbs 2011

    Frage

  • After "almost" finishing the upgrade from SBS 2003 to SBS 2011 completely, I was left with the task of removing Exchange 2003 and demoting the server. Well the Exchange 2003 server failed due to OWA not removing correctly, so I left it as is for a little longer. Well there was a hardware failure on the old server, and I was unable to get it up again for a while now. The new SBS 2011 server has been functioning without a problem at all for all this time (5 months or so).

    Today I fixed the hardware issue, brought it up, the AD is not able to replicate. I have narrowed it down to a dns issues, running dcdiag /test:dns gives a warning: The Active directory zone on this dc/dns server was not found (probably a misconfiguration).

    running dcdiag /test:dns on the new SBS 2011 shows there is a broken delegated domain _msdcs.domain.local

    Repadmin /showrepl shows a number of errors with the following: The target principal name is incorrect. same for repadmin /syncall. Same for doing it through AD Sites and Services.

    The DNS of the old server points to the new SBS 2011 - I had it point to itself and new server but still same replication errors.

    In the DNS server event logs, Event ID 4013 - DNS serve was unable to open Active Directory. On the old server, there is no Forward lookup zones listed at all.

    Now I found a few articles, mainly this http://support.microsoft.com/kb/2021446 and http://support.microsoft.com/kb/2001093 that seem to talk about the problem at hand - stale records removal, but nothing about re-adding the references to the DC that was added back. Also checked the DNS cnam and a records on the new server...all seem to still have the old server.

    Reading through, not sure what path to take. Should I recreate the forward lookup zone manually? Or make the following registry change and reboot the server:

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NTDS\Parameters
    Value name:  Repl Perform Initial Synchronizations
    Value type:  REG_DWORD
    Value data: 0

    It's also not helping that the server restarts every several hours...

    Any guidance is appreciated!

    Freitag, 8. Juni 2012 23:09

Antworten

  • If it were me I'd just shut off the old server and perfrom a metadata cleanup... seems faster and cleaner with all the issues you have.

    Samstag, 9. Juni 2012 01:36
  • Exchange removal part looks correct however i doubt you will be able to demote old sbs gracefully http://support.microsoft.com/kb/216498 will be required for the same which you can perform on new SBS. Additionally from dnsmgmt.msc remove any entry that points to the old sbs (you will need to expand all containers and delete those if present ). "Do not delete any Administrative group objects for exchange only delete the items under Server object ".Ensure to have a backup before proceeding with all this.

    Dienstag, 12. Juni 2012 19:11

Alle Antworten

  • If it were me I'd just shut off the old server and perfrom a metadata cleanup... seems faster and cleaner with all the issues you have.

    Samstag, 9. Juni 2012 01:36
  • Replicating with a dead server that too after 5 months post migration is something that you need to consider seriously. Considering tombstone period , migration life cycle etc. GreenlightTech  is correct "shut off the old server and perfrom a metadata cleanup" for which http://support.microsoft.com/kb/216498 has to be followed.
    Sonntag, 10. Juni 2012 11:14
  • Thanks for the suggestion GreenlightTech and Mohitkapoor! Agreed this would be the best course of action. Plan to first remove Exchange 2003 from the AD using the following steps:

    Click Start, point to Programs, point to Windows 2000 Support Tools, point to Tools, and then click ADSI Edit.
        Expand the following items:
        Configuration Container
        CN=Configuration, DC=Domain_Name,DC=com
        CN=Services
        CN=Microsoft Exchange
        CN=Your_Organization_Name
        CN=Administrative Groups
        CN=Your_Administrative_Group_Name_Or_Exchange5.5_Site_Name
        CN=Servers
        Note In this procedure, Domain_Name represents the name of your domain, Your_Organization_Name represents the name of your organization, and Your_Administrative_Group_Name_Or_Exchange5.5_Site_Name represents for the name of your administrative group or Exchange Server 5.5 site.
        Right-click the Exchange Server 2003 server object, and then click Delete.
        Click Yes in every adsiedit dialog box that prompts you to confirm the deletion.

    and then use the GUI to remove the OLD SBS server from AD using the following steps: http://technet.microsoft.com/en-us/library/cc816907%28WS.10%29.aspx

    Sound good?

    Dienstag, 12. Juni 2012 15:33
  • Exchange removal part looks correct however i doubt you will be able to demote old sbs gracefully http://support.microsoft.com/kb/216498 will be required for the same which you can perform on new SBS. Additionally from dnsmgmt.msc remove any entry that points to the old sbs (you will need to expand all containers and delete those if present ). "Do not delete any Administrative group objects for exchange only delete the items under Server object ".Ensure to have a backup before proceeding with all this.

    Dienstag, 12. Juni 2012 19:11