ADMT Problem

From: Mike (shaman_60_at_yahoo.com)
Date: 02/25/04 

Date: Wed, 25 Feb 2004 15:05:56 -0800

Setup:
Domain A - PDC only - Windows NT 4.0 Terminal Service
Edition w/SP6

Domain B - Windows 2000 Server w/SP4

I'm trying to use the ADMT tool to migrate users and
groups from Domain A to Domain B. I've followed the how
to guide: Set Up ADMT for Windows NT 4.0 to Windows 2000
Migration along with a couple of other guides. When I try
to migrate users or groups and migrate SID history, I
receive the following error:

"Either the source domain's primary domain controller
(PDC) has not been restarted after setting the
TcpipClientSupport registry key to 1 or the PDC could not
be contacted."

Can anyone give me some direction here?

Thanks in advance.
-Mike

Relevant Pages

  • NT 4.0 PDC to 2000 SERVER AD admt question
    ... I would like to upgrade NT 4.0 PDC to Windows 2000 Server Active ... Directory on to a new hardware. ... Have a question on the ADMT tool: ...
    (microsoft.public.win2000.active_directory)
  • NT 4.0 PDC to Windows 2000 Server AD - admt domain question
    ... I would like to upgrade NT 4.0 PDC to Windows 2000 Server Active ... Directory on to a new hardware. ... Have a question on the ADMT tool: ...
    (microsoft.public.win2000.setup_upgrade)
  • Trust Between NT4 and 2003
    ... area for Windows 2003. ... The guide says you must use the NetBIOS name ... resolution to enable trust between domains... ... something I would have to turn on manually on the NT PDC ...
    (microsoft.public.win2000.security)
  • RE: NT4 to Server 2003 Migration
    ... Windows 2003 but the new hardware will not support Windows NT 4.0. ... It will only be used as a transition server. ... | functions, too), 1 PDC, and a few member ...
    (microsoft.public.windows.server.migration)
  • Re: NT4 > Win 2003 Server
    ... When two different Windows NT Advanced Servers or Windows NT Servers in a ... I think the most convenient upgrade solution is install Windows NT BDC on ... the new server, promote it to PDC and then inplace-upgrade it to Windows ...
    (microsoft.public.windows.server.migration)