ADMT v2 Error while migrating a computer

Tech-Archive recommends: Fix windows errors by optimizing your registry

At the end of computer migration I am getting the following error. The
computer object is created in W2K3 AD, however the computer doesn't change
it's domain nor reboot.

2005-04-15 16:45:55 Changed computer name to Tor-W2115200
2005-04-15 16:46:00 ERR3:7075 Failed to change domain affiliation,
hr=8007054b The specified domain either does not exist or could not be
contacted.
2005-04-15 16:46:00 Changed computer name to W2115200
2005-04-15 16:46:00 Wrote result file C:\Program
Files\OnePointDomainAgent\W211520084814515.result
2005-04-15 16:46:00 Operation completed.

Both the PDC (NT4 domain) and the DCs (AD domain) point to the same WINs
servers.

DHCP has been modified to include the AD DNS for the scope so the client
machine being migrated points to the AD DNS and has registered in DNS (A and
PTR records).

The trusts are setup correctly and the source domain migration group SD$$$
has been created. The domain admins group from the NT4 domain is in the
administrators group in AD and the domain admins group from the AD domain is
in the administrators group in the NT domain.

Groups and Users migrate ok however the computers don't change domain.
.

Relevant Pages

  • Re: Installing SBS2008
    ... I'm going to address the DNS and DHCP cleanup first, ... then later installing the server at the production location (your ... enough disk space to do preparation of the server for the migration. ...
    (microsoft.public.windows.server.sbs)
  • Re: Migrating NT domain to AD
    ... The W98 machines do not have to have AD client to be in the new domain, ... ONLY AD domain controllers are listed as preferred dns servers for your computers via ... The downside is that I believe some of the better migration tools ... require that the migration be to a native mode domain. ...
    (microsoft.public.win2000.security)
  • RE: NT4.o to WIn2003 Domain MIgration DNS configuration
    ... one thing more i want to point out that the primary dns suffix is not there ... that to change automatically upon migration. ... I am migrating these clients from nt4.0 domain to win2003 and this message ... Microsoft Online Partner Support ...
    (microsoft.public.windows.server.migration)
  • RE: Migrating small domain 2000 to 2003
    ... >>We are in the planning stages of migrating our DMZ domain from 2000 to ... >>migration with as few headaches as possible. ... >>This machine also hosts our external DNS. ... >>Reinstall Backup Exec and associated Hardware ...
    (microsoft.public.windows.server.migration)
  • RE: NT4.o to WIn2003 Domain MIgration DNS configuration
    ... We suggest you point all the clients machines to the new Windows 2k3 DNS ... and perform the migration. ... | nt4.0 domain dns which is in my dhcp settings. ...
    (microsoft.public.windows.server.migration)