Can not demote Server 2008 Domain Controller due to not able to transfer the remaining data in directory partition.

Servers Setup::
Name                   OS         FSMO Holder
MCLS-DC01       2008
MCLS-DC02       2008
MCLS-DC03       2012              Yes
MCLS-DC04       2012

I am trying to migrate my Domain Controllers from 2008 to 2012 Standard Edition.  My goal is to demote DC01 and DC02 so I can remove them from the network. All servers point to DC03 and DC04 for DNS.  When I run dcpromo, it errors out with the message in the attached Picture called  "AD Error".  I have followed the instructions from this site to try and resolve this,

http://blog.mpecsinc.ca/2011/03/ad-ds-operation-failed-directory.html

but it does not resolve it because I can not make the change it refers to.  The first issue I have is that the website and all other sites that I have found refers to when the demotion fails and its for DC=ForestDNSZones.  My error is for DC=DomainDNS Zones.  If you follow the websites instructions it wants you to open ADSI Edit and connect to DC=DomainDNSZones......etc.  When I do this, I am on the FSMO role Master and get the following error in the attached picture called ASDIEdit and will not allow me to change the name to DC03 which is the new FSMO Master.  The highlighted section is referencing and old server called MCLS-SVR01 that has not been in service for years.  I have also attached a picture of a netdom query for FSMO.  Thank you in advance.

AD-errorfsmoasdi error
KineticNetworkingAsked:
Who is Participating?
 
Old UserCommented:
Note that when the infrastucture master is assigned to a deleted NTDSA on a DNS application partiton, like DomainDNSZones, it may also be missing for ForestDNSZones parttion or vice versa. Microsoft Commercial Support recommends that you verify that the for both the DomainDNSZones and ForestDNSZones partitions assigned to "live" Windows Server 2003 or later domain controllers hosting the DNS Server role and partition in question.

Use ADSIEDIT.MSC to assign the DN path for the fsMORoleOwner attribute to a live DC that was a direct replication partner of the original FSMO role owner then wait for that change to inbound replicate to the DC being demoted.

OR

Run the script in the Resolution section of MSKB 949257 for the partition in question.

OR

If the DC being demoted is not capable of inbound replicating changes for the directory partition in question, run the "DCPROMO /FORCEREMOVAL command to forcefuly demote the domain controoller.
1
 
Old UserCommented:
0
 
Ganesamoorthy STech LeadCommented:
Check AD replication and run dcdiag to check for issue before role move

http://www.windowstricks.in/2010/03/health-check-active-directory.html
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.

 
compdigit44Commented:
I agree with Ganesamoorthy S, it sounds like you might have some AD replication issues going on there. Could you post the out put of: repadmin / showrepl >c:\repadmin.txt    and dcdiag / v /e >c:\dcdiag.txt
0
 
KineticNetworkingAuthor Commented:
Please see attached files for results of repadmin and dcdiag.  Thank you
dcdiag.txt
repadmin.txt
0
 
compdigit44Commented:
From the dcdiag and repadmin you servers look healthy... Can you post the results of the netdom query fsmo role command from each server.
0
 
KineticNetworkingAuthor Commented:
Dave Preston,
     That  is the part i can't edit in ADSIEDIT.MSC.  No mater what server I am attached to, it say I don't have permission to change it.
0
 
Old UserCommented:
Have you tried either of the other 2 options?
0
 
Old UserCommented:
Hi,

I believe this article describes your issue, if you read it appears to agree with the previous post and kb949257.
0
 
KineticNetworkingAuthor Commented:
Dave Preston,
     I have always been nervous about running scripts because I do not have much background in scripting.  I went ahead and did the script in KB article 949257.  Did ADSIEDIT and looks like it has resolved that issue.  Now the demotion process is giving me the ForestDNS Zone error.  See attached Picture.  I am running into the same issue as before,  The dc that it shows has been out of commission for several years and can not change what it points to.  Can i run the script again but change it from

cscript fixfsmo.vbs DC=DomainDnsZones,DC=contoso,DC=com

to

cscript fixfsmo.vbs DC=ForestDnsZones,DC=contoso,DC=com
ForestError.jpg
0
 
Old UserCommented:
Hi, the article does say that you may get either or both error. Yes run the script again using

cscript fixfsmo.vbs DC=ForestDnsZones,DC=contoso,DC=com

To update the forestDnsZones
0
 
KineticNetworkingAuthor Commented:
Dcpromo is now running
0
 
Old UserCommented:
Glad you got it sorted
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.