active directory additional infect

با سلام
2 تا active directory دارم یکی فقط additional حالا dc اصلی را با image بر گردوندم به یک هفته پیش چه راهی وجود داره که دومی همه اطلاعات را از این دستگاه که به قبل برگشته بگیره

ضمنا روی additional active directory دومین سرویس dns همان دامین نیز وجود دارد

در این حالت برای replication پیغام زیر را می ده
source server is currently rejecting replication requests

[LEFT][SIZE=2][B]Here is our assumptions:[/B]
[/SIZE]
[B]1.[/B] You have 1 forest with one domain with two domain controllers.

[B]2.[/B] The machine that you are referring to as the PDC is a Windows 2000 domain
controller hosting all five FSMO roles and the global catalog (GC).

[B]3.[/B] DNS for your domain is running on the remaining domain controller you
refer to as the BDC.

[B]Here is what you need to do[/B]

[B]1.[/B] The re-installed machine you refer to as the PDC make it a member of a
workgroup. If you have already joined it to the domain join it back to a
workgroup. You can call the workgroup any name you want as long as it does
not conflict with any other NetBIOS name on your network.

[B]2.[/B] Make sure that the name on the re-install machine you refer to as PDC has
the name you want it to have. If that name is the same as it was before the
re-build that is OK.

[B]3.[/B] Make sure that the machine you call BDC is running DNS.

[B]4.[/B] Make sure that the machine you call BDC is pointing to itself for DNS in
the TCP/IP properties

[B]5.[/B] Make sure that the re-installed machine you refer to as the PDC is
pointing to the machine you call BDC for DNS in the TCP/IP properties

[B]6.[/B] Performa a metadata cleanup to remove the machine you call PDC from the
active directory.

[B]a.[/B] HOW TO: Remove Data in Active Directory After an Unsuccessful
Domain Controller Demotion - [URL="http://support.microsoft.com/?kbid=216498"]How to remove data in Active Directory after an unsuccessful domain controller demotion[/URL]

[B]7.[/B] If the computers machine account object is present in Active Directory
User and Computers under the Domain Controllers OU, try and delete it. If
the object cannot be deleted you will need to change the UserAccountControl
attribute on the object to a value of 4096 with ADSI Edit which is part of
the support tools. This should allow you to readily delete the object.

[B]a.[/B] How to Use the UserAccountControl Flags to Manipulate User
Account Properties - [URL="http://support.microsoft.com/?kbid=305144"]How to use the UserAccountControl flags to manipulate user account properties[/URL]

[B]8.[/B] Use NTDSUTIL to seize the FSMO roles to the machine you call BDC
[B]
a.[/B] Windows 2000 Active Directory FSMO Roles -
[URL="http://support.microsoft.com/?kbid=197132"]Windows 2000 Active Directory FSMO roles[/URL]
[B]
b.[/B] Using Ntdsutil.exe to Seize or Transfer FSMO Roles to a
Domain Controller - [URL="http://support.microsoft.com/?kbid=255504"]Using Ntdsutil.exe to transfer or seize FSMO roles to a domain controller[/URL]

[B]9.[/B] Make the machine you refer to as BDC a Global Catalog.

[B]a.[/B] HOW TO: Create or Move a Global Catalog in Windows 2000 -
[URL="http://support.microsoft.com/?kbid=313994"]How to create or move a global catalog in Windows Server 2003, Windows 2000, or Small Business Server 2000[/URL]

[B]b.[/B] When you make the machine you refer to as BDC a Global
Catalog you will receive an 1110 event in the Directory Service log. Do not
reboot the machine until you receive an 1119 event in the Directory Service
log.

[B]10.[/B] You are now ready to join the re-installed machine you call PDC back to
the domain as a member server. Please make sure that the machine account
shows up in Active Directory Users and Computers.
[B]
11.[/B] Run DCPROMO to promote the machine back to a domain controller.

After the successful promotion you will be free to move DNS, the FSMO roles
and the GC back to their original positions
[/LEFT]