Question : ADMT NT4 to 2K Computer migration agent fails - Domain does not exist.

hi,

We have a small NT4 network with a single domain called NT4DOMAIN, one PDC, one BDC and half a dozen member servers.
I have installed a WIn2K server as the only AD server on the network and given it the domain name testdomain.testforest.com (don't worry after playing about I'll reinstall with the proper registered DNS name!).

Trusts are set up between the domains and tested OK.
Domain admins on the AD domain have local admin rights on the client PC's so that ADMT can install it's migration agents on the PC's.

All parts of the computer migration work fine up until the agent tries to get the PC to join the AD domain and reboot.
The new computer account in AD is created, the agent is installed on the client PC and it does it's stuff changing security on the client etc.

Then I get the error: ERR3:7075 Failed to change domain affiliation, hr=8007054b The specified domain either does not exist or could not be contacted.

If I manually try to join the AD domain from the client PC it works fine - but I don't want to have to do this on 100+ clients.
If I manually browse the network from the client PC's I can see both domains.

I have a feeling it could be a DNS issue...

NT4 PDC runs DNS for the NT domain and has 3 zones set up. Forwarders are set to point to the ISP DNS servers.
The Win2K srever runs DNS for the AD domain and has 1 zone the same name as the AD domain.

Do I need to put some sort of record on the NT4 DNS server to let the client PC's know how to contact the AD domain??

Many Thanks,

Anthony.

Answer : ADMT NT4 to 2K Computer migration agent fails - Domain does not exist.

Sounds like you're on the right track.  AD requires several DNS entries in order to locate the directory services.

Option 1: Add a slave zone to your NT4 server that will transfer your AD domain DNS and allow it to resolve for your clients that use the NT4 DNS.

Option 2: Set your NT4 DNS to use the W2K AD DNS as forwarder and set the W2K DNS to forward out the the ISP.

Option 3: NT4 doesn't care about DNS in relation to the domain.  Set-up all of your DNS zones on the W2K machine with forwading to the ISP, reconfigure the PCs with the DHCP scope to use the W2K as DNS, and stop the NT4 DNS service.