Assigning FSMO Role

So I ran into this error when I tried to demote a Domain Controller (2008 R2):

Active Directory Domain Services could not transfer the remaining data in directory partition
DC=DomainDnsZones, DC=Development, DC=Local to Active Directory Domain Controller \\DC2.production.local

"The directory service is missing mandatory configuration information, and is unable to determine the ownership of floating single-master operation roles."

So I take it that DC2 needs to be assigned the FSMO role using Ntdsutil.exe. I run that on my old DC1 2008 R2 server, connect to my new DC2 2012 server and assign it each role. Am I right about all of this?
new_to_networksAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Mike KlineCommented:
There are a lot of steps that you can go through to fix this so you can gracefully demote  
http://blog.mpecsinc.ca/2011/03/ad-ds-operation-failed-directory.html

 Does your current 2012 server  hold all the FSMO roles?  Run netdom query fsmo on the 2012 box.

Thanks

Mike
0
new_to_networksAuthor Commented:
Just ran it- interestingly enough, the roles are assigned to a different 2012 DC in the domain. Which is fine- they can totally be where they're at, but then I don't realize why the one I'm trying to demote is mentioning one without those roles- why can't it be ok with the DC that actually has them?
0
Seth SimmonsSr. Systems AdministratorCommented:
it's trying to replicate data to the schema master but there is an issue with the attribute defining what the schema master is; probably has corrupt or invalid data

follow that posted link and do it on the schema master.  if you try on a different domain controller it will not allow you to apply the changes.

once the change is made, either force replication or just wait until it does it manually then run dcpromo again
0
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

new_to_networksAuthor Commented:
So on the DC that is the current schema master reassign it as the schema master? Isn't it already? Or are you telling me to make the one that it is looking at that has nothing the schema master?
0
Seth SimmonsSr. Systems AdministratorCommented:
no...look at that article and you'll see what we're talking about
there is an infrastructure object  in both DomainDNSZones and ForestDNSZones (you'll have to check which one is the issue on your server) and when you look at the value for fSMORoleOwner has a server that is not valid - that value needs to be changed to the server that is the schema master
0
new_to_networksAuthor Commented:
Can't connect to it. Getting Operation failed. Error code: 0x202b A referral was returned from the server. 0000202B: RefErr:DSID-031007EF, data 0, 1 access points ref 1: 'domaindnszones.domain.local'
0
new_to_networksAuthor Commented:
Ok, new things- The error has changed to the actual correct fsmo server now, but the error is the same. Before it was showing the wrong server, now its showing the right one. I'm able to connect now like it instructs on the link but I'm a little lost- am I doing this on the server I'm trying to demote or on the correct fsmo holder server?
0
Seth SimmonsSr. Systems AdministratorCommented:
the server that holds the schema master role
0
new_to_networksAuthor Commented:
Confused still- the instructions they give in Obtain the Correct Setting and then in Correct the Problematic Setting are like identical- I end up in the same place and what I would be pasting over is exactly what I just copied. It just takes me back to CN=Infrastructure and fSMORoleOwner in both sets of instructions.
0
Seth SimmonsSr. Systems AdministratorCommented:
did you look at both ForestDNSZones and DomainDNSZones?

one of them could be correct; i've seen this happen where one is correct and the other is wrong causing this problem.  once i've also seen both wrong and had to fix both
0
new_to_networksAuthor Commented:
See attached. This is where I'm at. I'm on the schema master server. Notice the two connections on the left are the same place. Confused when you say forest vs domain- where that's located exactly.
adsiedit.jpg
0
Seth SimmonsSr. Systems AdministratorCommented:
if you look at that page and go to step 2 in selecting the distinguished name or naming context, that's where you type those in.  you show DomainDNSZones so repeat that step but put ForestDNSZones instead of DomainDNSZones
0
new_to_networksAuthor Commented:
Ok so, in the first set of instructions I'm copying CN=Infrastructure and fSMORoleOwner from DomainDNSZones and then in part 2 I'm connecting to ForestDNSZones and pasting what I copied from DomainDNSZones? Is that right?
0
Seth SimmonsSr. Systems AdministratorCommented:
yes, replace Domain with Forest in the distinguished name box
0
new_to_networksAuthor Commented:
The fSMORoleOwner is identical in both domain and forest.
0
Seth SimmonsSr. Systems AdministratorCommented:
run dcdiag on all domain controllers and report back any errors

if that attribute is correct then there is something else going on
0
new_to_networksAuthor Commented:
DC that I'm trying to demote had these errors:

Starting test: SystemLog
         An error event occurred.  EventID: 0x00000422
            Time Generated: 09/12/2013   07:55:44
Event String:
            The processing of Group Policy failed. Windows attempted to read the
 file \\Development.Local\SysVol\Development.Local\Policies\{84A6969E-66D0-4578-
9ACE-16E90CD38179}\gpt.ini from a domain controller and was not successful. Grou
p Policy settings may not be applied until this event is resolved. This issue ma
y be transient and could be caused by one or more of the following:
         An error event occurred.  EventID: 0x00000422
            Time Generated: 09/12/2013   08:00:44
            Event String:
            The processing of Group Policy failed. Windows attempted to read the
 file \\Development.Local\SysVol\Development.Local\Policies\{84A6969E-66D0-4578-
9ACE-16E90CD38179}\gpt.ini from a domain controller and was not successful. Grou
p Policy settings may not be applied until this event is resolved. This issue ma
y be transient and could be caused by one or more of the following:
         An error event occurred.  EventID: 0x00000422
            Time Generated: 09/12/2013   08:05:45
            Event String:
            The processing of Group Policy failed. Windows attempted to read the
 file \\Development.Local\SysVol\Development.Local\Policies\{84A6969E-66D0-4578-
9ACE-16E90CD38179}\gpt.ini from a domain controller and was not successful. Grou
p Policy settings may not be applied until this event is resolved. This issue ma
y be transient and could be caused by one or more of the following:
         An error event occurred.  EventID: 0x00000422
            Time Generated: 09/12/2013   08:10:46
            Event String:
            The processing of Group Policy failed. Windows attempted to read the
 file \\Development.Local\SysVol\Development.Local\Policies\{84A6969E-66D0-4578-
9ACE-16E90CD38179}\gpt.ini from a domain controller and was not successful. Grou
p Policy settings may not be applied until this event is resolved. This issue ma
y be transient and could be caused by one or more of the following:
         An error event occurred.  EventID: 0x00000422
            Time Generated: 09/12/2013   08:15:46
            Event String:
            The processing of Group Policy failed. Windows attempted to read the
 file \\Development.Local\SysVol\Development.Local\Policies\{84A6969E-66D0-4578-
9ACE-16E90CD38179}\gpt.ini from a domain controller and was not successful. Grou
p Policy settings may not be applied until this event is resolved. This issue ma
y be transient and could be caused by one or more of the following:
         An error event occurred.  EventID: 0x00000422
            Time Generated: 09/12/2013   08:20:47
            Event String:
            The processing of Group Policy failed. Windows attempted to read the
 file \\Development.Local\SysVol\Development.Local\Policies\{84A6969E-66D0-4578-
9ACE-16E90CD38179}\gpt.ini from a domain controller and was not successful. Grou
p Policy settings may not be applied until this event is resolved. This issue ma
y be transient and could be caused by one or more of the following:
         An error event occurred.  EventID: 0x00000422
            Time Generated: 09/12/2013   08:25:48
            Event String:
            The processing of Group Policy failed. Windows attempted to read the
 file \\Development.Local\SysVol\Development.Local\Policies\{84A6969E-66D0-4578-
9ACE-16E90CD38179}\gpt.ini from a domain controller and was not successful. Grou
p Policy settings may not be applied until this event is resolved. This issue ma
y be transient and could be caused by one or more of the following:
         An error event occurred.  EventID: 0x00000422
            Time Generated: 09/12/2013   08:30:48
            Event String:
            The processing of Group Policy failed. Windows attempted to read the
 file \\Development.Local\SysVol\Development.Local\Policies\{84A6969E-66D0-4578-
9ACE-16E90CD38179}\gpt.ini from a domain controller and was not successful. Grou
p Policy settings may not be applied until this event is resolved. This issue ma
y be transient and could be caused by one or more of the following:
         An error event occurred.  EventID: 0x00000422
            Time Generated: 09/12/2013   08:35:49
            Event String:
            The processing of Group Policy failed. Windows attempted to read the
 file \\Development.Local\SysVol\Development.Local\Policies\{84A6969E-66D0-4578-
9ACE-16E90CD38179}\gpt.ini from a domain controller and was not successful. Grou
p Policy settings may not be applied until this event is resolved. This issue ma
y be transient and could be caused by one or more of the following:
         An error event occurred.  EventID: 0x00000422
            Time Generated: 09/12/2013   08:40:49
            Event String:
            The processing of Group Policy failed. Windows attempted to read the
 file \\Development.Local\SysVol\Development.Local\Policies\{84A6969E-66D0-4578-
9ACE-16E90CD38179}\gpt.ini from a domain controller and was not successful. Grou
p Policy settings may not be applied until this event is resolved. This issue ma
y be transient and could be caused by one or more of the following:
         An error event occurred.  EventID: 0x00000422
            Time Generated: 09/12/2013   08:45:50
            Event String:
            The processing of Group Policy failed. Windows attempted to read the
 file \\Development.Local\SysVol\Development.Local\Policies\{84A6969E-66D0-4578-
9ACE-16E90CD38179}\gpt.ini from a domain controller and was not successful. Grou
p Policy settings may not be applied until this event is resolved. This issue ma
y be transient and could be caused by one or more of the following:
         An error event occurred.  EventID: 0x00000422
            Time Generated: 09/12/2013   08:50:51
            Event String:
            The processing of Group Policy failed. Windows attempted to read the
 file \\Development.Local\SysVol\Development.Local\Policies\{84A6969E-66D0-4578-
9ACE-16E90CD38179}\gpt.ini from a domain controller and was not successful. Grou
p Policy settings may not be applied until this event is resolved. This issue ma
y be transient and could be caused by one or more of the following:
         An error event occurred.  EventID: 0x00000422
            Time Generated: 09/12/2013   08:51:01
            Event String:
            The processing of Group Policy failed. Windows attempted to read the
 file \\Development.Local\SysVol\Development.Local\Policies\{84A6969E-66D0-4578-
9ACE-16E90CD38179}\gpt.ini from a domain controller and was not successful. Grou
p Policy settings may not be applied until this event is resolved. This issue ma
y be transient and could be caused by one or more of the following:
         ......................... DC1 failed test SystemLog


Errors on Schema Master:

Starting test: NetLogons
         [DC2] User credentials does not have permission to perform this
         operation.
         The account used for this test must have network logon privileges
         for this machine's domain.
         ......................... DC2 failed test NetLogons
      Starting test: ObjectsReplicated
         ......................... DC2 passed test ObjectsReplicated
      Starting test: Replications
         [Replications Check,DC2] DsReplicaGetInfo(PENDING_OPS, NULL)
         failed, error 0x2105 "Replication access was denied."
         ......................... DC2 failed test Replications
      Starting test: RidManager
         ......................... DC2 passed test RidManager
      Starting test: Services
            Could not open NTDS Service on DC2, error 0x5
            "Access is denied."
         ......................... DC2 failed test Services
      Starting test: SystemLog
         An error event occurred.  EventID: 0x00000422
            Time Generated: 09/12/2013   08:04:00
            Event String:
            The processing of Group Policy failed. Windows attempted to read the
 file \\Development.Local\SysVol\Development.Local\Policies\{84A6969E-66D0-4578-
9ACE-16E90CD38179}\gpt.ini from a domain controller and was not successful. Grou
p Policy settings may not be applied until this event is resolved. This issue ma
y be transient and could be caused by one or more of the following:
         An error event occurred.  EventID: 0x00000422
            Time Generated: 09/12/2013   08:07:27
            Event String:
            The processing of Group Policy failed. Windows attempted to read the
 file \\Development.Local\SysVol\Development.Local\Policies\{84A6969E-66D0-4578-
9ACE-16E90CD38179}\gpt.ini from a domain controller and was not successful. Grou
p Policy settings may not be applied until this event is resolved. This issue ma
y be transient and could be caused by one or more of the following:
         An error event occurred.  EventID: 0x00000422
            Time Generated: 09/12/2013   08:09:00
            Event String:
            The processing of Group Policy failed. Windows attempted to read the
 file \\Development.Local\SysVol\Development.Local\Policies\{84A6969E-66D0-4578-
9ACE-16E90CD38179}\gpt.ini from a domain controller and was not successful. Grou
p Policy settings may not be applied until this event is resolved. This issue ma
y be transient and could be caused by one or more of the following:
         An error event occurred.  EventID: 0x00000422
            Time Generated: 09/12/2013   08:14:00
            Event String:
            The processing of Group Policy failed. Windows attempted to read the
 file \\Development.Local\SysVol\Development.Local\Policies\{84A6969E-66D0-4578-
9ACE-16E90CD38179}\gpt.ini from a domain controller and was not successful. Grou
p Policy settings may not be applied until this event is resolved. This issue ma
y be transient and could be caused by one or more of the following:
         An error event occurred.  EventID: 0x00000422
            Time Generated: 09/12/2013   08:19:00
            Event String:
            The processing of Group Policy failed. Windows attempted to read the
 file \\Development.Local\SysVol\Development.Local\Policies\{84A6969E-66D0-4578-
9ACE-16E90CD38179}\gpt.ini from a domain controller and was not successful. Grou
p Policy settings may not be applied until this event is resolved. This issue ma
y be transient and could be caused by one or more of the following:
         An error event occurred.  EventID: 0x00000422
            Time Generated: 09/12/2013   08:24:00
            Event String:
            The processing of Group Policy failed. Windows attempted to read the
 file \\Development.Local\SysVol\Development.Local\Policies\{84A6969E-66D0-4578-
9ACE-16E90CD38179}\gpt.ini from a domain controller and was not successful. Grou
p Policy settings may not be applied until this event is resolved. This issue ma
y be transient and could be caused by one or more of the following:
         An error event occurred.  EventID: 0x00000422
            Time Generated: 09/12/2013   08:29:01
            Event String:
            The processing of Group Policy failed. Windows attempted to read the
 file \\Development.Local\SysVol\Development.Local\Policies\{84A6969E-66D0-4578-
9ACE-16E90CD38179}\gpt.ini from a domain controller and was not successful. Grou
p Policy settings may not be applied until this event is resolved. This issue ma
y be transient and could be caused by one or more of the following:
         An error event occurred.  EventID: 0x00000422
            Time Generated: 09/12/2013   08:34:01
            Event String:
            The processing of Group Policy failed. Windows attempted to read the
 file \\Development.Local\SysVol\Development.Local\Policies\{84A6969E-66D0-4578-
9ACE-16E90CD38179}\gpt.ini from a domain controller and was not successful. Grou
p Policy settings may not be applied until this event is resolved. This issue ma
y be transient and could be caused by one or more of the following:
         An error event occurred.  EventID: 0x00000422
            Time Generated: 09/12/2013   08:39:01
            Event String:
            The processing of Group Policy failed. Windows attempted to read the
 file \\Development.Local\SysVol\Development.Local\Policies\{84A6969E-66D0-4578-
9ACE-16E90CD38179}\gpt.ini from a domain controller and was not successful. Grou
p Policy settings may not be applied until this event is resolved. This issue ma
y be transient and could be caused by one or more of the following:
         An error event occurred.  EventID: 0x00000422
            Time Generated: 09/12/2013   08:44:01
            Event String:
            The processing of Group Policy failed. Windows attempted to read the
 file \\Development.Local\SysVol\Development.Local\Policies\{84A6969E-66D0-4578-
9ACE-16E90CD38179}\gpt.ini from a domain controller and was not successful. Grou
p Policy settings may not be applied until this event is resolved. This issue ma
y be transient and could be caused by one or more of the following:
         An error event occurred.  EventID: 0x00000422
            Time Generated: 09/12/2013   08:49:01
            Event String:
            The processing of Group Policy failed. Windows attempted to read the
 file \\Development.Local\SysVol\Development.Local\Policies\{84A6969E-66D0-4578-
9ACE-16E90CD38179}\gpt.ini from a domain controller and was not successful. Grou
p Policy settings may not be applied until this event is resolved. This issue ma
y be transient and could be caused by one or more of the following:
         An error event occurred.  EventID: 0x00000422
            Time Generated: 09/12/2013   08:54:02
            Event String:
            The processing of Group Policy failed. Windows attempted to read the
 file \\Development.Local\SysVol\Development.Local\Policies\{84A6969E-66D0-4578-
9ACE-16E90CD38179}\gpt.ini from a domain controller and was not successful. Grou
p Policy settings may not be applied until this event is resolved. This issue ma
y be transient and could be caused by one or more of the following:
         An error event occurred.  EventID: 0x00000422
            Time Generated: 09/12/2013   08:59:02
            Event String:
            The processing of Group Policy failed. Windows attempted to read the
 file \\Development.Local\SysVol\Development.Local\Policies\{84A6969E-66D0-4578-
9ACE-16E90CD38179}\gpt.ini from a domain controller and was not successful. Grou
p Policy settings may not be applied until this event is resolved. This issue ma
y be transient and could be caused by one or more of the following:
         ......................... DC2 failed test SystemLog
0
Seth SimmonsSr. Systems AdministratorCommented:
[DC2] User credentials does not have permission to perform this operation.

can you try this again from an elevated command prompt?
there are definitely issues based on the event log output but some of these tests won't work unless it's from an elevated command prompt
0
new_to_networksAuthor Commented:
Ok ran it as admin- passed all those premilinary ones and errors look the same as the other now:


Starting test: SystemLog
         An error event occurred.  EventID: 0x00000422
            Time Generated: 09/12/2013   08:24:00
            Event String:
            The processing of Group Policy failed. Windows attempted to read the
 file \\Development.Local\SysVol\Development.Local\Policies\{84A6969E-66D0-4578-
9ACE-16E90CD38179}\gpt.ini from a domain controller and was not successful. Grou
p Policy settings may not be applied until this event is resolved. This issue ma
y be transient and could be caused by one or more of the following:
         An error event occurred.  EventID: 0x00000422
            Time Generated: 09/12/2013   08:29:01
            Event String:
            The processing of Group Policy failed. Windows attempted to read the
 file \\Development.Local\SysVol\Development.Local\Policies\{84A6969E-66D0-4578-
9ACE-16E90CD38179}\gpt.ini from a domain controller and was not successful. Grou
p Policy settings may not be applied until this event is resolved. This issue ma
y be transient and could be caused by one or more of the following:
         An error event occurred.  EventID: 0x00000422
            Time Generated: 09/12/2013   08:34:01
            Event String:
            The processing of Group Policy failed. Windows attempted to read the
 file \\Development.Local\SysVol\Development.Local\Policies\{84A6969E-66D0-4578-
9ACE-16E90CD38179}\gpt.ini from a domain controller and was not successful. Grou
p Policy settings may not be applied until this event is resolved. This issue ma
y be transient and could be caused by one or more of the following:
         An error event occurred.  EventID: 0x00000422
            Time Generated: 09/12/2013   08:39:01
            Event String:
            The processing of Group Policy failed. Windows attempted to read the
 file \\Development.Local\SysVol\Development.Local\Policies\{84A6969E-66D0-4578-
9ACE-16E90CD38179}\gpt.ini from a domain controller and was not successful. Grou
p Policy settings may not be applied until this event is resolved. This issue ma
y be transient and could be caused by one or more of the following:
         An error event occurred.  EventID: 0x00000422
            Time Generated: 09/12/2013   08:44:01
            Event String:
            The processing of Group Policy failed. Windows attempted to read the
 file \\Development.Local\SysVol\Development.Local\Policies\{84A6969E-66D0-4578-
9ACE-16E90CD38179}\gpt.ini from a domain controller and was not successful. Grou
p Policy settings may not be applied until this event is resolved. This issue ma
y be transient and could be caused by one or more of the following:
         An error event occurred.  EventID: 0x00000422
            Time Generated: 09/12/2013   08:49:01
            Event String:
            The processing of Group Policy failed. Windows attempted to read the
 file \\Development.Local\SysVol\Development.Local\Policies\{84A6969E-66D0-4578-
9ACE-16E90CD38179}\gpt.ini from a domain controller and was not successful. Grou
p Policy settings may not be applied until this event is resolved. This issue ma
y be transient and could be caused by one or more of the following:
         An error event occurred.  EventID: 0x00000422
            Time Generated: 09/12/2013   08:54:02
            Event String:
            The processing of Group Policy failed. Windows attempted to read the
 file \\Development.Local\SysVol\Development.Local\Policies\{84A6969E-66D0-4578-
9ACE-16E90CD38179}\gpt.ini from a domain controller and was not successful. Grou
p Policy settings may not be applied until this event is resolved. This issue ma
y be transient and could be caused by one or more of the following:
         An error event occurred.  EventID: 0x00000422
            Time Generated: 09/12/2013   08:59:02
            Event String:
            The processing of Group Policy failed. Windows attempted to read the
 file \\Development.Local\SysVol\Development.Local\Policies\{84A6969E-66D0-4578-
9ACE-16E90CD38179}\gpt.ini from a domain controller and was not successful. Grou
p Policy settings may not be applied until this event is resolved. This issue ma
y be transient and could be caused by one or more of the following:
         An error event occurred.  EventID: 0x00000422
            Time Generated: 09/12/2013   09:04:02
            Event String:
            The processing of Group Policy failed. Windows attempted to read the
 file \\Development.Local\SysVol\Development.Local\Policies\{84A6969E-66D0-4578-
9ACE-16E90CD38179}\gpt.ini from a domain controller and was not successful. Grou
p Policy settings may not be applied until this event is resolved. This issue ma
y be transient and could be caused by one or more of the following:
         An error event occurred.  EventID: 0x00000422
            Time Generated: 09/12/2013   09:09:02
            Event String:
            The processing of Group Policy failed. Windows attempted to read the
 file \\Development.Local\SysVol\Development.Local\Policies\{84A6969E-66D0-4578-
9ACE-16E90CD38179}\gpt.ini from a domain controller and was not successful. Grou
p Policy settings may not be applied until this event is resolved. This issue ma
y be transient and could be caused by one or more of the following:
         An error event occurred.  EventID: 0x00000422
            Time Generated: 09/12/2013   09:14:02
            Event String:
            The processing of Group Policy failed. Windows attempted to read the
 file \\Development.Local\SysVol\Development.Local\Policies\{84A6969E-66D0-4578-
9ACE-16E90CD38179}\gpt.ini from a domain controller and was not successful. Grou
p Policy settings may not be applied until this event is resolved. This issue ma
y be transient and could be caused by one or more of the following:
         An error event occurred.  EventID: 0x00000422
            Time Generated: 09/12/2013   09:19:02
            Event String:
            The processing of Group Policy failed. Windows attempted to read the
 file \\Development.Local\SysVol\Development.Local\Policies\{84A6969E-66D0-4578-
9ACE-16E90CD38179}\gpt.ini from a domain controller and was not successful. Grou
p Policy settings may not be applied until this event is resolved. This issue ma
y be transient and could be caused by one or more of the following:
         ......................... DC2 failed test SystemLog
0
Seth SimmonsSr. Systems AdministratorCommented:
go into event viewer and system log and find this error (based on frequency there is likely a lot there)
just select anyone and click the details tab; there should be an error code listed (either 3, 5, or 53)
0
new_to_networksAuthor Commented:
Its a 3.
0
Seth SimmonsSr. Systems AdministratorCommented:
0
new_to_networksAuthor Commented:
I installed DFS on the DC that won't demote and removed its DNS Server role- still same error when I try to demote. The error has the wrong DC on it again - its referencing DC3 and not DC2 where FSMO actually is at.
0
Seth SimmonsSr. Systems AdministratorCommented:
from the elevated command prompt, can you do repadmin /syncall ?
0
new_to_networksAuthor Commented:
From server that won't demote:



Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

CALLBACK MESSAGE: The following replication is in progress:
    From: 66cdb806-7313-42e7-8cbe-d9c5cb4da528._msdcs.Development.Local
    To  : 2a09e3fc-d0e9-43fa-aa94-0b18ff132464._msdcs.Development.Local
CALLBACK MESSAGE: The following replication completed successfully:
    From: 66cdb806-7313-42e7-8cbe-d9c5cb4da528._msdcs.Development.Local
    To  : 2a09e3fc-d0e9-43fa-aa94-0b18ff132464._msdcs.Development.Local
CALLBACK MESSAGE: The following replication is in progress:
    From: c8054e2f-ac2e-473f-8ef9-cc6547ee0b21._msdcs.Development.Local
    To  : 2a09e3fc-d0e9-43fa-aa94-0b18ff132464._msdcs.Development.Local
CALLBACK MESSAGE: The following replication completed successfully:
    From: c8054e2f-ac2e-473f-8ef9-cc6547ee0b21._msdcs.Development.Local
    To  : 2a09e3fc-d0e9-43fa-aa94-0b18ff132464._msdcs.Development.Local
CALLBACK MESSAGE: SyncAll Finished.
SyncAll terminated with no errors.
0
Seth SimmonsSr. Systems AdministratorCommented:
DC3?  your original post shows DC2 in the error message
0
new_to_networksAuthor Commented:
Sorry its confusing-

DC1 - DC I'm trying to demote.
DC2 - DC that has the fsmo roles.
DC3 - Another DC.

The error message switches back and forth naming DC2 and DC3. DC2 is in fact the actual holder and DC3 has nothing to with any of this. I just got the error and at the moment its naming the correct holder- DC2.
0
Seth SimmonsSr. Systems AdministratorCommented:
i want to review my initial thought since i can't make sense of this aside from the entry of the infrastructure master not being correct and the fact that there are no replication issues.  every time i've seen this happen with a domain controller the issue was with one or both of these values being incorrect.

when looking at that fSMORoleHolder for both DomainDNSZones and ForestDNSZones, the attribute does show similar to this (site name would be your AD site that server is in) ?

CN=NTDS Settings,CN=DC2,CN=Servers,CN=MySite,CN=Sites,CN=Configuration,DC=development,DC=local
0
new_to_networksAuthor Commented:
Sorry I was away for so long, I've been bombarded with work. See attached screenshot of fsmo holder. Yes, the forest fsmo and the domain fsmo are the same. They're the same on the fsmo holder and the DC that I'm trying to demote. There's nothing for me to change.
0
new_to_networksAuthor Commented:
Got it to work. Followed script at http://support.microsoft.com/kb/949257. The script changed this:

CN=NTDS Settings\(combination of letters and numbers),CN=CONTROLLER,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=Development,DC=Local

To this:

CN=NTDS Settings,CN=DC1,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=Development,DC=Local

I changed DC1 to DC2 and then I could demote DC1. Because that combo of letters and numbers was identical in both forest and domain, and on both DCs- there was nothing for me to change. Once I ran the script, the whole thing appeared differently and I was able to make the changes.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
new_to_networksAuthor Commented:
The script at that link made the fsmo entry field appear different, once that happened I could make the needed changes.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Active Directory

From novice to tech pro — start learning today.