Monday, February 25, 2013 12:06 PM
I have Target and Source domains on different LANs. Joined together via site to site VPNs. I cannot get ADMT to migrate a computer. However I can migrate a user when my Migration server (where ADMT is installed) is in the target IP network. When I move the Migration server (it is a VM) to the source LAN it cannont find ANY domain controllers for the source LAN. It finds them, but says access is denied. Which is bollox as I can \\IPOFDC\admin$ and it opens (logged into my migration servers as Admin for my target domain). I can also ping the FQDN in both directions (as I changed its DNS and IP settings)
Has any one done this? Or can this only be done when the Target domain is physically in the same office?
Monday, February 25, 2013 9:22 PM
Add the ADMT service account onto workstation and try again.
Santhosh Sivarajan | Houston, TX
Windows 2012 Book - Migrating from 2008 to Windows Server 2012
This post is provided ASIS with no warran
- Marked As Answer by K_evin ZhuMicrosoft Contingent Staff, Moderator Wednesday, March 06, 2013 8:11 AM
Friday, March 08, 2013 9:37 AM
Yes, the ADMT user account has permission on the workstation. I am using the Administrator account on the Target domain. I added to locally to the Administrators group from the command line. I think the problem is that the Domain Trust continually breaks. I can browse the Admin$ and C$ share of the PC from my Migration Server and DC, I then reboot the PC to make sure no profiles are locked when I start ADMT, I'll then check that I can browse the shares again...and I can't. Even though I could before I rebooted.
I think it is because the Target DC isn't on the same LAN (even though there is a VPN between the two and DNS resolves correctly). Even if I took the Target DC to the LAN where my test PC is and got it to work, I'd then have to move my Target DC around for the other sites, which is not really workable.