The requested operation could not be performed because the directory service is not the master for that type of operation.

I am getting this erro when I try to move a user from child domain to root domain using ADMT.

2015-09-08 11:26:48 ERR2:7422 Failed to move source object 'CN=John alias'. hr=0x80072012  The requested operation could not be performed because the directory service is not the master for that type of operation.

Anyone faced the same issue?
is there anyone who can guide me fix this?
LVL 30
MAS (MVE)EE Solution GuideAsked:
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.

systechadminConsultantCommented:
it seems that issue is with the Account permission from which you are trying to move. Can you please check on the both domains for the account.
0
Amit KumarCommented:
please move your FSMO on destination server on which DC you are trying move this user.

Specially RID master.
0
MAS (MVE)EE Solution GuideAuthor Commented:
@Gaurav Singh
It is already an enterprise admin

@Amit
I am trying to move the a user from child doman DC to a DC in root domain which is the FSMO holder as of now.
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

Amit KumarCommented:
so does Child domain controller is hosting FSMO role in case you have ADC of child dc.
0
MAS (MVE)EE Solution GuideAuthor Commented:
@Amit
I didn't understand the above
0
Amit KumarCommented:
I was meant to RID master role hosting child domain's DC.
0
Zacharia KurianAdministrator- Data Center & NetworkCommented:
Have you tried moving the user, using Move Tree command line? If not please try the link for more info.

https://support.microsoft.com/en-us/kb/238394

Another thought is this; try removing the group membership and associated GPOs for the user .

Also make sure the user was not in account locked out state, if so reset the password and try.

Zac.
0
MAS (MVE)EE Solution GuideAuthor Commented:
@Zac
I am not familiar with movetree

This is a production server
0
MAS (MVE)EE Solution GuideAuthor Commented:
I found something today. When I run command "netdom query fsmo" from child DCs I am getting warning.

C:\Users\Administrator>netdom query fsmo
Schema master               *** Warning: role owner is a deleted DC: CN=NTDS Settings\0ADEL:584a2306-cca1-41fe-8443-5b4ecbe424f1,CN=MYDC01,CN=Servers,CN=mycompany,CN=Sites,CN=Configuration,DC=domain,DC=edu,DC=kw
Domain naming master        *** Warning: role owner is a deleted DC: CN=NTDS Settings\0ADEL:584a2306-cca1-41fe-8443-5b4ecbe424f1,CN=MYDC01,CN=Servers,CN=mycompany,CN=Sites,CN=Configuration,DC=domain,DC=edu,DC=kw
PDC                         MYDCCO-DC-01.domain.com
RID pool manager            MYDCCO-DC-01.domain.com
Infrastructure master       MYDCCO-DC-01.domain.com
The command completed successfully.

It is pointing to a deleted DC. If I run from root domain it is listing new DC.
0
Zacharia KurianAdministrator- Data Center & NetworkCommented:
Have you tried to clean the deleted DC using AD Metada?
Have you verified the Replications?
Try running ADBPA in the child dc and look at the issues.
Also check the following Registry Key and see if Root Domain is correctly pointed
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\NTDS\Parameters.
Look at Src Root Domain Srv and make sure that your PDC is pointed there.


Zac.
0
MAS (MVE)EE Solution GuideAuthor Commented:
I am not sure how to make the child DCs pick the new schema master and domain naming master
0
Amit KumarCommented:
run DCDIAG /s:<childDCname> /f:c:\result.txt

and have a look on errors if you want you can share it here.

However if you child DC lost its ownership then try to reboot or force replicate whole AD replication. If that won't work then log a case in MS. I think we should not play much with production box it can lead you mess in your infra.
0
Amit KumarCommented:
MAS there is something bad between your DC and CDC as they are not replicating with each other. I have found couple of errors for deleting AD partitions. SO better you go for a MS case if this is your production servers.
0
MAS (MVE)EE Solution GuideAuthor Commented:
Removed all the child domains and connected mailboxes to the parent domain users as I am running out of time
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
MAS (MVE)EE Solution GuideAuthor Commented:
Thanks to all
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
Windows Server 2008

From novice to tech pro — start learning today.

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.