Steve M
asked on
ADMT 3.2 Migration, Unable to verify the computer 'svr1.source.local' belongs to the domain 'source.local'. The remote procedure call failed and did not execute. (hr=0x800706bf)
We are trying to perform an intraforest domain migration. The source domain level is 2003 and the target is 2012. ADMT 3.2 is installed in the target domain on a server running 2012 r2. Their is a trust setup and we have had no problems so far, we have migrated some users and groups without issue and I am going to start on computers and servers.
When I went to run a migration on a server I received the following message on the pre-check, which subsequently failed:
Unable to verify the computer 'svr1.source.local' belongs to the domain 'source.local'. The remote procedure call failed and did not execute. (hr=0x800706bf)
I have scoured the internet and I have seen no other instances of this error to work off of. I have double-checked DNS settings and the health of the source domain, the error is still occurring. I have tried other servers and PCs and the pre-check always fails with the same error message. The service account we are using for this is the 'Administrator' account from the target domain, I have verified it is a member of the builtin administrator group on the source domain.
Any help or suggestions are appreciated greatly.
When I went to run a migration on a server I received the following message on the pre-check, which subsequently failed:
Unable to verify the computer 'svr1.source.local' belongs to the domain 'source.local'. The remote procedure call failed and did not execute. (hr=0x800706bf)
I have scoured the internet and I have seen no other instances of this error to work off of. I have double-checked DNS settings and the health of the source domain, the error is still occurring. I have tried other servers and PCs and the pre-check always fails with the same error message. The service account we are using for this is the 'Administrator' account from the target domain, I have verified it is a member of the builtin administrator group on the source domain.
Any help or suggestions are appreciated greatly.
Last Comment
ASKER
Coralon,
This has been done with no change in the resulting error. It's just odd that all pcs/servers on the old domain would be coming up with this error.
The new target domain is located over a vpn, but all traffic is allowed between the two networks over that vpn.
This has been done with no change in the resulting error. It's just odd that all pcs/servers on the old domain would be coming up with this error.
The new target domain is located over a vpn, but all traffic is allowed between the two networks over that vpn.
Well, it does look like a DCOM issue.. Can you verify that the account you use has launch permissions on both sides on the DC's?
There are also some 2003 hotfixes that sort of relate..
https://support.microsoft.
https://support.microsoft.
And this is definitely a vague shotgun approach to figure this out..
Coralon
There are also some 2003 hotfixes that sort of relate..
https://support.microsoft.
https://support.microsoft.
And this is definitely a vague shotgun approach to figure this out..
Coralon
ASKER
There are actually no longer any 2003 DCs in the domain, the server in question I am testing is 2008 r2.
And the account I am using to run the migration (target domain administration account) is a member of the builtin administration group on the source domain, and I also added it to the local administrator group of the server I tested, just to be sure.
And the account I am using to run the migration (target domain administration account) is a member of the builtin administration group on the source domain, and I also added it to the local administrator group of the server I tested, just to be sure.
In that case, do you have the option to raise the domain functionality level and then try the migration?
Coralon
Coralon
ASKER CERTIFIED SOLUTION
THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
I was able to get it working, while potentially not resolving the issue holding the process up initially.
Windows OS
This topic area includes legacy versions of Windows prior to Windows 2000: Windows 3/3.1, Windows 95 and Windows 98, plus any other Windows-related versions including Windows Mobile.
129K
Questions
--
Followers
--
Top Experts
Get a personalized solution from industry experts
TRUSTED BY
Coralon