Run the below query through your domain name and also check whether still any FSMO role owner is pointing to your old server.

You are watching: Active directory domain services could not transfer the remaining data in directory partition

dsquery * CN=Infrastructure,DC=DomainDnsZones,DC=xxxxx,DC=xxxx -attr fSMORoleOwner

Similar Discussion:

http://incubadoradeartistas.com/Forums/en-US/9d7c3cd8-6033-4232-8d4b-c44f99fa983a/fsmoroleowner-really-messed-up-unable-to-change-it?forum=winserverDS

http://incubadoradeartistas.com/Forums/windowsserver/en-US/72640045-616b-4b6c-8fc4-e30dd8463402/dcpromo-remove-domain-controller-failed?forum=winserverDS

Regards,Rafic If you uncovered this post helpful, please provide it a "Helpful" vote. If that answered your question, remember to mark it as an "Answer".This posting is provided "AS IS" v no warranties and confers no rights! always test any suggestion in a test environment prior to implementing!


Thursday, January 30, 2014 11:55 AM
*

*

0
sign in to vote

Hi Rafic,

OK, ns think I have resolved it.

When to run the dsquery * CN=Infrastructure,DC=DomainDnsZones,DC=xxxxx,DC=xxxx -attr fSMORoleOwner command it reported ago the surname of the old DC which to be decommissioned at some point ago.

Running the FixFsmo script has resolved the issue but I to be making a mistake in just how I was to run the script.

Basically I had forgotten to eliminate the -------fixfsmo.vbs------------------ line from the script exactly how it appears on the ms Site.

I then necessary to operation it whilst logged top top the framework Master in the kid Domain together an companies Admin native the parental Domain.

This successfully resolved the issue.


Thursday, January 30, 2014 12:22 PM

all replies


*

*

1
sign in to poll

Hi Etala,

Run the below query v your domain name and also check even if it is still any FSMO duty owner is pointing to your old server.

dsquery * CN=Infrastructure,DC=DomainDnsZones,DC=xxxxx,DC=xxxx -attr fSMORoleOwner

Similar Discussion:

http://incubadoradeartistas.com/Forums/en-US/9d7c3cd8-6033-4232-8d4b-c44f99fa983a/fsmoroleowner-really-messed-up-unable-to-change-it?forum=winserverDS

http://incubadoradeartistas.com/Forums/windowsserver/en-US/72640045-616b-4b6c-8fc4-e30dd8463402/dcpromo-remove-domain-controller-failed?forum=winserverDS

Regards,Rafic If you discovered this article helpful, please give it a "Helpful" vote. If that answered your question, psychic to mark it together an "Answer".This posting is detailed "AS IS" v no warranties and confers no rights! always test any kind of suggestion in a test environment before implementing!


Thursday, January 30, 2014 11:55 AM
*

0
sign in to vote

Hi Rafic,

OK, i think I have resolved it.

When running the dsquery * CN=Infrastructure,DC=DomainDnsZones,DC=xxxxx,DC=xxxx -attr fSMORoleOwner command it reported earlier the name of the old DC which to be decommissioned at some time ago.

Running the FixFsmo script has resolved the issue yet I to be making a wrong in just how I was running the script.

Basically I had forgotten to eliminate the -------fixfsmo.vbs------------------ heat from the script just how it shows up on the multiple sclerosis Site.

I then necessary to operation it whilst logged ~ above the framework Master in the child Domain together an enterprise Admin native the parental Domain.

See more: Failed To Load Resource: The Server Responded With A Status Of 404

This efficiently resolved the issue.


Thursday, January 30, 2014 12:22 PM
Newsletter|Contact Us|Privacy Statement|Terms of Use|Trademarks