Win server 2003 Replication failing after a system state restore

Home Forums Server Operating Systems Windows Server 2000 / 2003 / 2003 R2 Win server 2003 Replication failing after a system state restore

This topic contains 2 replies, has 2 voices, and was last updated by  biggles77 8 months, 1 week ago.

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts

  • sandleaf
    Member
    #167492

    Hello,

    We’ve got a couple windows 2003 server with exchange 2007 installed on it.FSMO functions RID, PDC and Infrastructure are set up on a single Server and Schema Master and Domain Name master is set up on different server.
    In addition, we have another DC that are also set up with market 2007 on it that are placed at several place.

    Lately because of a corruption we conducted a system restore on the DC with Schema master and Domain Naming Master.
    The system state restore was successful but after the restart the DNS sever couldn’t begin on the host and of the Exchange related services too couldn’t start.

    Please assist.


    biggles77
    Spectator
    #214396

    How old was the System State? You may have a Tombstoned Server.


    biggles77
    Spectator
    #214397

    If by chance it has been tombstoned, you can untombstone it with this reg hack.

    Windows Registry Editor Version 5.00

    [HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesNTDSParameters]

    “Allow Replication With Divergent and Corrupt Partner”=dword:00000001[/CODE]

    Save in notepad or Notepad++ with a [B].reg[/B] extension. If this works (or doesn’t work) run the following to disable what was done because it is a security hole that may be exploited to gain access to your network.

    [CODE]Windows Registry Editor Version 5.00

    [HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesNTDSParameters]

    “Allow Replication With Divergent and Corrupt Partner”=dword:00000000[/CODE]

    If you look closely you will see that the very last digit was changed from a [B]1 [/B]to a [B]0[/B] (zero).

    I have mentioned tombstoning because you don’t say what other operating system it is replication with. If it is another 2003 o/s then you have 180 days of non contact with each other before the server is tombstoned. Later operating systems usually have a default of 60 days but this can be lowered even more by the system Administrator.

    [B][URL=”http://www.itprotoday.com/management-mobility/q-how-can-i-check-tombstone-lifetime-my-active-directory-forest”]How can I check the tombstone lifetime of my Active Directory forest[/URL][/B][CODE]Windows Registry Editor Version 5.00

    [HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesNTDSParameters]

    “Allow Replication With Divergent and Corrupt Partner”=dword:00000001[/CODE]

    Save in notepad or Notepad++ with a .reg extension. If this works (or doesn’t work) run the following to disable what was done because it is a security hole that may be exploited to gain access to your network.

    Windows Registry Editor Version 5.00

    [HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesNTDSParameters]

    “Allow Replication With Divergent and Corrupt Partner”=dword:00000000[/CODE]

    If you look closely you will see that the very last digit was changed from a [B]1 [/B]to a [B]0[/B] (zero).

    I have mentioned tombstoning because you don’t say what other operating system it is replication with. If it is another 2003 o/s then you have 180 days of non contact with each other before the server is tombstoned. Later operating systems usually have a default of 60 days but this can be lowered even more by the system Administrator.

    [B][URL=”http://www.itprotoday.com/management-mobility/q-how-can-i-check-tombstone-lifetime-my-active-directory-forest”]How can I check the tombstone lifetime of my Active Directory forest[/URL][/B][CODE]Windows Registry Editor Version 5.00

    [HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesNTDSParameters]

    “Allow Replication With Divergent and Corrupt Partner”=dword:00000000[/CODE]

    If you look closely you will see that the very last digit was changed from a 1 to a 0 (zero).

    I have mentioned tombstoning because you don’t say what other operating system it is replication with. If it is another 2003 o/s then you have 180 days of non contact with each other before the server is tombstoned. Later operating systems usually have a default of 60 days but this can be lowered even more by the system Administrator.

    How can I check the tombstone lifetime of my Active Directory forest

Viewing 3 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic.