Link to home
Create AccountLog in
Active Directory

Active Directory

--

Questions

--

Followers

Top Experts

Avatar of revellej
revellej🇺🇸

Problem Raising domain funtion level to 2003 after raising forest funtion level to 2003
I have a domain controller that is running Windows Server 2008r2. Last week we had a storm and now the dhcp server service is no longer working and will not start. I am trying to setup a new DC running windows server 2012. I have read that the domain and forest functional levels should be raised to at least Windows Sever 3003 functional level. I read that when I raise the forest functional level to 2003 that the domain functional level will be raised automatically. When I look in AD Domains and trusts, I see that the current forest level is now 2003 but the raise domain funtional level still shows the current domain funtional level is "Windows 2000 native". If I try to raise it to 2003 I get the following message: The funtional level could not be raised. The error is: The FSMO role ownership could not be verified because its directory partition has not replicated successfully with at least one replication partner.
I need to make this server a domain controller to take over the roles of the problem DC.
Any advice on how to proceed to make this a domain controller with a domain funtional level of 2003? Is there anything special that I need to do to promote the 2012 server to a DC??
Any thoughts would be appreaciated.

Zero AI Policy

We believe in human intelligence. Our moderation policy strictly prohibits the use of LLM content in our Q&A threads.


ASKER CERTIFIED SOLUTION
Avatar of Sarang TinguriaSarang Tinguria🇮🇳

Link to home
membership
Log in or create a free account to see answer.
Signing up is free and takes 30 seconds. No credit card required.
Create Account

Avatar of Mike KlineMike Kline🇺🇸

Can you run dcdiag and repadmin.  What errors are you seeing there?

Thanks

Mike

Avatar of revellejrevellej🇺🇸

ASKER

There are a few DC's in AD but they are all funtional.

I ran dcdiag with the following results:
            Event String:
            Internal event: Active Directory Domain Services has encountered the
 following exception and associated parameters.
         An error event occurred.  EventID: 0xC000043C
            Time Generated: 07/15/2013   13:59:59
            Event String:
            Internal event: Active Directory Domain Services could not update th
e following object with changes received from the following source directory ser
vice. This is because an error occurred during the application of the changes to
 Active Directory Domain Services on the directory service.
         An error event occurred.  EventID: 0xC000083C
            Time Generated: 07/15/2013   13:59:59
            Event String:
            This event contains REPAIR PROCEDURES for the 1084 event which has p
reviously been logged. This message indicates a specific issue with the consiste
ncy of the Active Directory Domain Services database on this replication destina
tion. A database error occurred while applying replicated changes to the followi
ng object. The database had unexpected contents, preventing the change from bein
g made.
         A warning event occurred.  EventID: 0x80000495
            Time Generated: 07/15/2013   13:59:59
            Event String:
            Internal event: Active Directory Domain Services has encountered the
 following exception and associated parameters.
         An error event occurred.  EventID: 0xC000043C
            Time Generated: 07/15/2013   13:59:59
            Event String:
            Internal event: Active Directory Domain Services could not update th
e following object with changes received from the following source directory ser
vice. This is because an error occurred during the application of the changes to
 Active Directory Domain Services on the directory service.
         An error event occurred.  EventID: 0xC000083C
            Time Generated: 07/15/2013   13:59:59
            Event String:
            This event contains REPAIR PROCEDURES for the 1084 event which has p
reviously been logged. This message indicates a specific issue with the consiste
ncy of the Active Directory Domain Services database on this replication destina
tion. A database error occurred while applying replicated changes to the followi
ng object. The database had unexpected contents, preventing the change from bein
g made.
         An error event occurred.  EventID: 0x000001D3
            Time Generated: 07/15/2013   14:00:01
            Event String:
            NTDS (636) NTDSA: Database C:\Windows\NTDS\ntds.dit: Index DRA_USN_i
ndex of table datatable is corrupted (0).
         A warning event occurred.  EventID: 0x80000495
            Time Generated: 07/15/2013   14:00:01
            Event String:
            Internal event: Active Directory Domain Services has encountered the
 following exception and associated parameters.
         An error event occurred.  EventID: 0xC000043C
            Time Generated: 07/15/2013   14:00:01
            Event String:
            Internal event: Active Directory Domain Services could not update th
e following object with changes received from the following source directory ser
vice. This is because an error occurred during the application of the changes to
 Active Directory Domain Services on the directory service.
         An error event occurred.  EventID: 0xC000083C
            Time Generated: 07/15/2013   14:00:01
            Event String:
            This event contains REPAIR PROCEDURES for the 1084 event which has p
reviously been logged. This message indicates a specific issue with the consiste
ncy of the Active Directory Domain Services database on this replication destina
tion. A database error occurred while applying replicated changes to the followi
ng object. The database had unexpected contents, preventing the change from bein
g made.
         An error event occurred.  EventID: 0x000001D3
            Time Generated: 07/15/2013   14:00:44
            Event String:
            NTDS (636) NTDSA: Database C:\Windows\NTDS\ntds.dit: Index DRA_USN_i
ndex of table datatable is corrupted (0).
         A warning event occurred.  EventID: 0x80000495
            Time Generated: 07/15/2013   14:00:44
            Event String:
            Internal event: Active Directory Domain Services has encountered the
 following exception and associated parameters.
         An error event occurred.  EventID: 0xC000043C
            Time Generated: 07/15/2013   14:00:44
            Event String:
            Internal event: Active Directory Domain Services could not update th
e following object with changes received from the following source directory ser
vice. This is because an error occurred during the application of the changes to
 Active Directory Domain Services on the directory service.
         An error event occurred.  EventID: 0xC000083C
            Time Generated: 07/15/2013   14:00:44
            Event String:
            This event contains REPAIR PROCEDURES for the 1084 event which has p
reviously been logged. This message indicates a specific issue with the consiste
ncy of the Active Directory Domain Services database on this replication destina
tion. A database error occurred while applying replicated changes to the followi
ng object. The database had unexpected contents, preventing the change from bein
g made.
         An error event occurred.  EventID: 0x000001D3
            Time Generated: 07/15/2013   14:01:16
            Event String:
            NTDS (636) NTDSA: Database C:\Windows\NTDS\ntds.dit: Index DRA_USN_i
ndex of table datatable is corrupted (0).
         A warning event occurred.  EventID: 0x80000495
            Time Generated: 07/15/2013   14:01:16
            Event String:
            Internal event: Active Directory Domain Services has encountered the
 following exception and associated parameters.
         An error event occurred.  EventID: 0xC000043C
            Time Generated: 07/15/2013   14:01:16
            Event String:
            Internal event: Active Directory Domain Services could not update th
e following object with changes received from the following source directory ser
vice. This is because an error occurred during the application of the changes to
 Active Directory Domain Services on the directory service.
         An error event occurred.  EventID: 0xC000083C
            Time Generated: 07/15/2013   14:01:16
            Event String:
            This event contains REPAIR PROCEDURES for the 1084 event which has p
reviously been logged. This message indicates a specific issue with the consiste
ncy of the Active Directory Domain Services database on this replication destina
tion. A database error occurred while applying replicated changes to the followi
ng object. The database had unexpected contents, preventing the change from bein
g made.
         ......................... ATLANTIS failed test KccEvent
      Starting test: KnowsOfRoleHolders
         ......................... ATLANTIS passed test KnowsOfRoleHolders
      Starting test: MachineAccount
         ......................... ATLANTIS passed test MachineAccount
      Starting test: NCSecDesc
         Error NT AUTHORITY\ENTERPRISE DOMAIN CONTROLLERS doesn't have
            Replicating Directory Changes In Filtered Set
         access rights for the naming context:
         DC=DomainDnsZones,DC=cooperinstrument,DC=com
         Error NT AUTHORITY\ENTERPRISE DOMAIN CONTROLLERS doesn't have
            Replicating Directory Changes In Filtered Set
         access rights for the naming context:
         DC=ForestDnsZones,DC=cooperinstrument,DC=com
         ......................... ATLANTIS failed test NCSecDesc
      Starting test: NetLogons
         ......................... ATLANTIS passed test NetLogons
      Starting test: ObjectsReplicated
         ......................... ATLANTIS passed test ObjectsReplicated
      Starting test: Replications
         [Replications Check,ATLANTIS] A recent replication attempt failed:
            From QA-TEST to ATLANTIS
            Naming Context: CN=Configuration,DC=cooperinstrument,DC=com
            The replication generated an error (8451):
            The replication operation encountered a database error.
            The failure occurred at 2013-07-15 13:57:45.
            The last success occurred at 2013-07-10 09:05:50.
            767 failures have occurred since the last success.
            A serious error is preventing replication from continuing.
            Consult the error log for further information.
            If a particular object is named, it may be necessary to manually
            modify or delete the object.
            If the condition persists, contact Microsoft Support.
         [Replications Check,ATLANTIS] A recent replication attempt failed:
            From CENTAURUS to ATLANTIS
            Naming Context: CN=Configuration,DC=cooperinstrument,DC=com
            The replication generated an error (8451):
            The replication operation encountered a database error.
            The failure occurred at 2013-07-15 13:57:46.
            The last success occurred at 2013-07-09 17:32:22.
            405 failures have occurred since the last success.
            A serious error is preventing replication from continuing.
            Consult the error log for further information.
            If a particular object is named, it may be necessary to manually
            modify or delete the object.
            If the condition persists, contact Microsoft Support.
         [Replications Check,ATLANTIS] A recent replication attempt failed:
            From LEVIATHAN to ATLANTIS
            Naming Context: CN=Configuration,DC=cooperinstrument,DC=com
            The replication generated an error (8451):
            The replication operation encountered a database error.
            The failure occurred at 2013-07-15 13:57:46.
            The last success occurred at 2013-07-10 09:26:50.
            390 failures have occurred since the last success.
            A serious error is preventing replication from continuing.
            Consult the error log for further information.
            If a particular object is named, it may be necessary to manually
            modify or delete the object.
            If the condition persists, contact Microsoft Support.
         [Replications Check,ATLANTIS] A recent replication attempt failed:
            From EXCHANGE to ATLANTIS
            Naming Context: CN=Configuration,DC=cooperinstrument,DC=com
            The replication generated an error (8451):
            The replication operation encountered a database error.
            The failure occurred at 2013-07-15 13:57:46.
            The last success occurred at 2013-07-10 09:37:43.
            769 failures have occurred since the last success.
            A serious error is preventing replication from continuing.
            Consult the error log for further information.
            If a particular object is named, it may be necessary to manually
            modify or delete the object.
            If the condition persists, contact Microsoft Support.
         [Replications Check,ATLANTIS] A recent replication attempt failed:
            From QA-TEST to ATLANTIS
            Naming Context: DC=cooperinstrument,DC=com
            The replication generated an error (8451):
            The replication operation encountered a database error.
            The failure occurred at 2013-07-15 13:57:47.
            The last success occurred at 2013-07-12 07:07:53.
            1585 failures have occurred since the last success.
            A serious error is preventing replication from continuing.
            Consult the error log for further information.
            If a particular object is named, it may be necessary to manually
            modify or delete the object.
            If the condition persists, contact Microsoft Support.
         [Replications Check,ATLANTIS] A recent replication attempt failed:
            From LEVIATHAN to ATLANTIS
            Naming Context: DC=cooperinstrument,DC=com
            The replication generated an error (8451):
            The replication operation encountered a database error.
            The failure occurred at 2013-07-15 14:00:01.
            The last success occurred at 2013-07-12 07:07:22.
            981 failures have occurred since the last success.
            A serious error is preventing replication from continuing.
            Consult the error log for further information.
            If a particular object is named, it may be necessary to manually
            modify or delete the object.
            If the condition persists, contact Microsoft Support.
         [Replications Check,ATLANTIS] A recent replication attempt failed:
            From CENTAURUS to ATLANTIS
            Naming Context: DC=cooperinstrument,DC=com
            The replication generated an error (8451):
            The replication operation encountered a database error.
            The failure occurred at 2013-07-15 14:00:44.
            The last success occurred at 2013-07-12 07:06:28.
            2331 failures have occurred since the last success.
            A serious error is preventing replication from continuing.
            Consult the error log for further information.
            If a particular object is named, it may be necessary to manually
            modify or delete the object.
            If the condition persists, contact Microsoft Support.
         [Replications Check,ATLANTIS] A recent replication attempt failed:
            From EXCHANGE to ATLANTIS
            Naming Context: DC=cooperinstrument,DC=com
            The replication generated an error (8451):
            The replication operation encountered a database error.
            The failure occurred at 2013-07-15 14:01:16.
            The last success occurred at 2013-07-11 07:27:10.
            3198 failures have occurred since the last success.
            A serious error is preventing replication from continuing.
            Consult the error log for further information.
            If a particular object is named, it may be necessary to manually
            modify or delete the object.
            If the condition persists, contact Microsoft Support.
         ......................... ATLANTIS failed test Replications
      Starting test: RidManager
         ......................... ATLANTIS passed test RidManager
      Starting test: Services
         ......................... ATLANTIS passed test Services
      Starting test: SystemLog
         An error event occurred.  EventID: 0x00000457
            Time Generated: 07/15/2013   14:01:12
            Event String:
            Driver Xerox WorkCentre 5845 PCL6 required for printer !!voyager!Xer
ox WorkCentre 5845 PCL6 is unknown. Contact the administrator to install the dri
ver before you log in again.
         ......................... ATLANTIS failed test SystemLog
      Starting test: VerifyReferences
         ......................... ATLANTIS passed test VerifyReferences


   Running partition tests on : DomainDnsZones
      Starting test: CheckSDRefDom
         ......................... DomainDnsZones passed test CheckSDRefDom
      Starting test: CrossRefValidation
         ......................... DomainDnsZones passed test
         CrossRefValidation

   Running partition tests on : ForestDnsZones
      Starting test: CheckSDRefDom
         ......................... ForestDnsZones passed test CheckSDRefDom
      Starting test: CrossRefValidation
         ......................... ForestDnsZones passed test
         CrossRefValidation

   Running partition tests on : Schema
      Starting test: CheckSDRefDom
         ......................... Schema passed test CheckSDRefDom
      Starting test: CrossRefValidation
         ......................... Schema passed test CrossRefValidation

   Running partition tests on : Configuration
      Starting test: CheckSDRefDom
         ......................... Configuration passed test CheckSDRefDom
      Starting test: CrossRefValidation
         ......................... Configuration passed test CrossRefValidation

   Running partition tests on : cooperinstrument
      Starting test: CheckSDRefDom
         ......................... cooperinstrument passed test CheckSDRefDom
      Starting test: CrossRefValidation
         ......................... cooperinstrument passed test
         CrossRefValidation

   Running enterprise tests on : cooperinstrument.com
      Starting test: LocatorCheck
         ......................... cooperinstrument.com passed test
         LocatorCheck
      Starting test: Intersite
         ......................... cooperinstrument.com passed test Intersite

C:\Users\administrator.COOPERDOMAIN>

What command line should I run for repadmin?

netdom query fsmo results are:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Users\administrator.COOPERDOMAIN>netdom query fsmo
Schema master               ATLANTIS.cooperinstrument.com
Domain naming master        ATLANTIS.cooperinstrument.com
PDC                         ATLANTIS.cooperinstrument.com
RID pool manager            ATLANTIS.cooperinstrument.com
Infrastructure master       ATLANTIS.cooperinstrument.com
The command completed successfully.


C:\Users\administrator.COOPERDOMAIN>

run repadmin /replsum

Its seems there are issues with DB on Atlantis as below error is showing

1) The replication operation encountered a database error.

2) NTDS (636) NTDSA: Database C:\Windows\NTDS\ntds.dit: Index DRA_USN_i
ndex of table datatable is corrupted (0).

I would have simply demoted/promoted rather than fighting for database repair

Reward 1Reward 2Reward 3Reward 4Reward 5Reward 6

EARN REWARDS FOR ASKING, ANSWERING, AND MORE.

Earn free swag for participating on the platform.


Avatar of revellejrevellej🇺🇸

ASKER

when I ran repadmin /replsum, the results were:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Users\administrator.COOPERDOMAIN>repadmin /replsum
Replication Summary Start Time: 2013-07-15 14:27:23

Beginning data collection for replication summary, this may take awhile:
  ........




Destination DSA     largest delta    fails/total %%   error
 ATLANTIS          05d.20h:55m:01s    8 /  18   44  (8451) The replication opera
tion encountered a database error.
 CENTAURUS                 31m:20s    0 /  13    0
 EXCHANGE                  29m:26s    0 /   8    0
 LEVIATHAN                 40m:29s    0 /   6    0
 QA-TEST                   41m:03s    0 /  10    0



C:\Users\administrator.COOPERDOMAIN>

Can I promote the 2012 server even thought the domain functional level is 2000 native?

No, you can not promote 2012 in 2000 native mode you will get below errorUser generated image

Avatar of revellejrevellej🇺🇸

ASKER

How can I get around it when it will not let me raise the domain funtional level to 2003?

Free T-shirt

Get a FREE t-shirt when you ask your first question.

We believe in human intelligence. Our moderation policy strictly prohibits the use of LLM content in our Q&A threads.


As there is broken replication you need to seize roles to working DC using link below
force Demote ATLANTIS, clean up metadata using link below, promote this DC again with same IP and name using dcpromo

Forcefull removal of DC:
http://support.microsoft.com/kb/332199 (2003)
http://technet.microsoft.com/en-us/library/cc731871(v=ws.10).aspx (2008)

Metadata cleanup:
http://www.petri.co.il/delete_failed_dcs_from_ad.htm

Seize FSMO role:
http://www.petri.co.il/seizing_fsmo_roles.htm

Avatar of Mike KlineMike Kline🇺🇸

Can you run repadmin /showreps on  ATLANTIS    

Thanks

Mike

Avatar of revellejrevellej🇺🇸

ASKER

Mike, This is what I get when I run repadmin /showreps on  ATLANTIS:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Users\administrator.COOPERDOMAIN>repadmin /showreps
Cooper-Atkins-CT\ATLANTIS
DSA Options: IS_GC
Site Options: (none)
DSA object GUID: 379f5487-1c5e-4f05-b5b1-1cd9d5a05341
DSA invocationID: ae9d7566-1474-4deb-bc88-893861d331dd

==== INBOUND NEIGHBORS ======================================

DC=cooperinstrument,DC=com
    Cooper-Atkins-CT\LEVIATHAN via RPC
        DSA object GUID: 4412b19b-1099-46e1-9f92-e9e5324dd98c
        Last attempt @ 2013-07-15 15:20:30 failed, result 8451 (0x2103):
            The replication operation encountered a database error.
        1010 consecutive failure(s).
        Last success @ 2013-07-12 07:07:22.
    Cooper-Atkins-CT\CENTAURUS via RPC
        DSA object GUID: 3d8dbfa9-bcab-4f3c-94c7-94447655a8bb
        Last attempt @ 2013-07-15 15:20:32 failed, result 8451 (0x2103):
            The replication operation encountered a database error.
        2412 consecutive failure(s).
        Last success @ 2013-07-12 07:06:28.
    Cooper-Atkins-CT\QA-TEST via RPC
        DSA object GUID: 165be400-00aa-408f-978c-ccccc16a02db
        Last attempt @ 2013-07-15 15:20:40 failed, result 8451 (0x2103):
            The replication operation encountered a database error.
        1639 consecutive failure(s).
        Last success @ 2013-07-12 07:07:53.
    Cooper-Atkins-CT\EXCHANGE via RPC
        DSA object GUID: a94db8d0-20ce-4c4d-a2bd-1f635f3ce98e
        Last attempt @ 2013-07-15 15:21:09 failed, result 8451 (0x2103):
            The replication operation encountered a database error.
        3262 consecutive failure(s).
        Last success @ 2013-07-11 07:27:10.

CN=Configuration,DC=cooperinstrument,DC=com
    Cooper-Atkins-CT\CENTAURUS via RPC
        DSA object GUID: 3d8dbfa9-bcab-4f3c-94c7-94447655a8bb
        Last attempt @ 2013-07-15 14:57:46 failed, result 8451 (0x2103):
            The replication operation encountered a database error.
        406 consecutive failure(s).
        Last success @ 2013-07-09 17:32:22.
    Cooper-Atkins-CT\LEVIATHAN via RPC
        DSA object GUID: 4412b19b-1099-46e1-9f92-e9e5324dd98c
        Last attempt @ 2013-07-15 14:57:46 failed, result 8451 (0x2103):
            The replication operation encountered a database error.
        391 consecutive failure(s).
        Last success @ 2013-07-10 09:26:50.
    Cooper-Atkins-CT\QA-TEST via RPC
        DSA object GUID: 165be400-00aa-408f-978c-ccccc16a02db
        Last attempt @ 2013-07-15 15:12:46 failed, result 8451 (0x2103):
            The replication operation encountered a database error.
        772 consecutive failure(s).
        Last success @ 2013-07-10 09:05:50.
    Cooper-Atkins-CT\EXCHANGE via RPC
        DSA object GUID: a94db8d0-20ce-4c4d-a2bd-1f635f3ce98e
        Last attempt @ 2013-07-15 15:12:46 failed, result 8451 (0x2103):
            The replication operation encountered a database error.
        774 consecutive failure(s).
        Last success @ 2013-07-10 09:37:43.

CN=Schema,CN=Configuration,DC=cooperinstrument,DC=com
    Cooper-Atkins-CT\CENTAURUS via RPC
        DSA object GUID: 3d8dbfa9-bcab-4f3c-94c7-94447655a8bb
        Last attempt @ 2013-07-15 14:57:47 was successful.
    Cooper-Atkins-CT\LEVIATHAN via RPC
        DSA object GUID: 4412b19b-1099-46e1-9f92-e9e5324dd98c
        Last attempt @ 2013-07-15 14:57:47 was successful.
    Cooper-Atkins-CT\QA-TEST via RPC
        DSA object GUID: 165be400-00aa-408f-978c-ccccc16a02db
        Last attempt @ 2013-07-15 15:12:46 was successful.
    Cooper-Atkins-CT\EXCHANGE via RPC
        DSA object GUID: a94db8d0-20ce-4c4d-a2bd-1f635f3ce98e
        Last attempt @ 2013-07-15 15:12:46 was successful.

DC=ForestDnsZones,DC=cooperinstrument,DC=com
    Cooper-Atkins-CT\CENTAURUS via RPC
        DSA object GUID: 3d8dbfa9-bcab-4f3c-94c7-94447655a8bb
        Last attempt @ 2013-07-15 14:57:50 was successful.
    Cooper-Atkins-CT\QA-TEST via RPC
        DSA object GUID: 165be400-00aa-408f-978c-ccccc16a02db
        Last attempt @ 2013-07-15 15:12:47 was successful.
    Cooper-Atkins-CT\EXCHANGE via RPC
        DSA object GUID: a94db8d0-20ce-4c4d-a2bd-1f635f3ce98e
        Last attempt @ 2013-07-15 15:12:47 was successful.

DC=DomainDnsZones,DC=cooperinstrument,DC=com
    Cooper-Atkins-CT\CENTAURUS via RPC
        DSA object GUID: 3d8dbfa9-bcab-4f3c-94c7-94447655a8bb
        Last attempt @ 2013-07-15 14:57:50 was successful.
    Cooper-Atkins-CT\QA-TEST via RPC
        DSA object GUID: 165be400-00aa-408f-978c-ccccc16a02db
        Last attempt @ 2013-07-15 15:12:47 was successful.
    Cooper-Atkins-CT\EXCHANGE via RPC
        DSA object GUID: a94db8d0-20ce-4c4d-a2bd-1f635f3ce98e
        Last attempt @ 2013-07-15 15:12:48 was successful.

Source: Cooper-Atkins-CT\CENTAURUS
******* 2407 CONSECUTIVE FAILURES since 2013-07-12 07:06:28
Last error: 8451 (0x2103):
            The replication operation encountered a database error.

Source: Cooper-Atkins-CT\EXCHANGE
******* 3257 CONSECUTIVE FAILURES since 2013-07-11 07:27:10
Last error: 8451 (0x2103):
            The replication operation encountered a database error.

Source: Cooper-Atkins-CT\LEVIATHAN
******* 1008 CONSECUTIVE FAILURES since 2013-07-12 07:07:22
Last error: 8451 (0x2103):
            The replication operation encountered a database error.

Source: Cooper-Atkins-CT\QA-TEST
******* 1636 CONSECUTIVE FAILURES since 2013-07-12 07:07:53
Last error: 8451 (0x2103):
            The replication operation encountered a database error.

C:\Users\administrator.COOPERDOMAIN>

Reward 1Reward 2Reward 3Reward 4Reward 5Reward 6

EARN REWARDS FOR ASKING, ANSWERING, AND MORE.

Earn free swag for participating on the platform.


Avatar of Mike KlineMike Kline🇺🇸

You can start going through the TechNet article below

http://technet.microsoft.com/en-us/library/replication-error-8451-the-replication-operation-encountered-a-database-error(v=ws.10).aspx

However, the steps provided to demote and promote might be faster and less painful.

Thanks

Mike

Avatar of revellejrevellej🇺🇸

ASKER

I need to transfer the FSMO roles from Atlantis (2008 r2) to Leviathan (2003 r2 standard) without demoting the DC atlantis as there are many machines pointing to atlantis for DNS. is that possible? What is the best way to do it?

Link given above my me will work for you... You will have to seize roles.....as you will demote then will again promote hence no dns issue should occur....refer my above rply...

Free T-shirt

Get a FREE t-shirt when you ask your first question.

We believe in human intelligence. Our moderation policy strictly prohibits the use of LLM content in our Q&A threads.


Avatar of revellejrevellej🇺🇸

ASKER

The instructions in the link look pretty straight forward. I have not had a chance to seize the roles yet as there are some things that are still running on the bad DC and I will need to reinstall Windows Server 2008 r2 on it (There are too many things wrong with it)... I will be out of the office until next tuesday and will work on it when I return. I'll let you know how it goes.

Avatar of revellejrevellej🇺🇸

ASKER

Sorry for not getting back sooner but I'm Still having a problem with Cisco agent loseing connection when ever I unplug the bad DC. I need to resolve this before I continue.

Avatar of revellejrevellej🇺🇸

ASKER

I want to thank you very much for your help on this. Everything went very well. I was able to seize the fsmo roles on a different DC, removed metadata of the old DC. I then rebuilt Atlantis and promoted it to a DC again and raised the forest and domain funtion levels to 2003 without any problems.
Thanks again.

Reward 1Reward 2Reward 3Reward 4Reward 5Reward 6

EARN REWARDS FOR ASKING, ANSWERING, AND MORE.

Earn free swag for participating on the platform.

Active Directory

Active Directory

--

Questions

--

Followers

Top Experts

Active Directory (AD) is a Microsoft brand for identity-related capabilities. In the on-premises world, Windows Server AD provides a set of identity capabilities and services, and is hugely popular (88% of Fortune 1000 and 95% of enterprises use AD). This topic includes all things Active Directory including DNS, Group Policy, DFS, troubleshooting, ADFS, and all other topics under the Microsoft AD and identity umbrella.