Re: New PDC...



Rob:

Thank you, yeah the old PDC is pretty badly jacked up for one, and two,
resources are minimal. The network is very small. I was worried about the
shares, etc etc, but at this point it shouldn't be a huge problem. Thank you
for your assistance, I'll probably just disjoing all workstations from the
domain. Introduce the new PDC, then rejoin the systems to the domain,
re-create the shares, etc. Shouldn't be a big deal. Just wanted to make
sure I was aware of all my options.

- Lex

"Rob McShinsky" wrote:

> Not upgrading the NT Box takes out the best way to do this since you could
> upgrade it to a W2K3 DC then bring up the new system as an AD DC, move all
> the roles over to the new box and then dcpromo down the old box. My guess
> is resources on the old Dell may be the problem if you are not considering
> this step.
>
> Depending on how SMALL your subnetwork is i.e. number of users and
> computers, you could potentially start over. Bring up the New DC and get it
> working, create duplicate user accounts, and then add the XP systems in
> manually at the workstations themselves. This is a kind of low tech
> approach, but could still save you time if the network is small enough since
> the only piece that would have to be done after hours (if you have an after
> hours) would be changing the workstations to the new domain. There are a
> number of other considerations as far as trusts with other domains and any
> other servers that need to come to the new domain. Shares in this case
> would have to be recreated since there would be new users accounts. Weigh
> the options based on your size and complexity. To preserve your accounts
> which would help you with your not having to remap your shares, you could
> also use the Migration tool from Microsoft. This may be a learning curve
> that may take longer to learn and perfect than is worth it for a small
> network. If your users are not flexible in say having to change their
> password when they log in the first time after you have made the switch or
> to have a few bumps after the above process, then take the time and learn
> the tools.
>
> Rob
>
>
>
> "Derrick" <Derrick@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:94B286DE-7422-4B27-9C7D-0E24D290C90B@xxxxxxxxxxxxxxxx
> > All:
> >
> > We presently have a small subnetwork set up, this network has all Windows
> > XP
> > SP2 clients, and 1 Windows NT PDC. This NT PDC is on an old Dell
> > workstation.
> >
> > I've purchased a newer faster system and installed Windows Server 2003
> > Standard on it. I want to introduce my new box as the NEW PDC. What's
> > the
> > best way to have my new server take over the PDC role? Since there is no
> > AD
> > currently in the domain (since the PDC is currently NT) how can I ensure
> > that
> > my accounts carry over, etc.
> >
> > I DO NOT want to have to upgrade the NT box to W3K because the box is
> > SOOOOO
> > SLOW!
>
>
>
.



Relevant Pages

  • Re: NT PDC can no longer administer users it its own domain but can in others.
    ... >> The network in question has been up and running for many years..... ... >> The PDC also had the NT Gateway for Netware service installed, ... >> However I get the same error message every time I try to select the PDC's ... >> I can go to the BDC and try to bring ...
    (microsoft.public.windows.server.general)
  • Re: ADMT TcpipClientSupport registry key NT 4.0 to AD
    ... I would take a network trace of the failure and see where it fails. ... > but I keep getting this error message "Either the source> domain's primary domain controller (PDC) has not been re-> started after setting the tcpipClientSupport registry key> to 1 or the PDC could not be contacted." ... > I have discarded the communication problem between the NT> 4.0 server and the Windows 2003 server because when I do> not select "Migrate user SIDs to target domain" the> migration is successful. ...
    (microsoft.public.win2000.active_directory)
  • workstations have problem with login after upgrading nt4 to w2k with AD and DNS
    ... We have a pretty small network that had a NT4 PDC and about 30 client ... To perform the 2k AD upgrade, I bought a server and installed NT4. ... I synchronized the new BDC with the PDC successfully. ... Now the problem is when I try to login from a client machine, ...
    (microsoft.public.windows.server.migration)
  • Re: Cant join domain: Network path was not found
    ... trying to join the domain 'hq.infotouchsys.com': Network path not ... I have a single server running as the primary domain controller (PDC) ... the registry tweaked to allow joining a domain.) ...
    (microsoft.public.win2000.active_directory)
  • Re: all user accounts locked out on PDC
    ... > I'm trying to determine the possible cause of my PDC ... > simultaneously locking all user accounts? ... All servers, PDC, BDC's are NT 4.0, ... > All servers and workstations are running most current SP's ...
    (microsoft.public.win2000.security)