Re: PDC only

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: MartinHTN (m_at_ht.n)
Date: 08/17/04


Date: Tue, 17 Aug 2004 08:43:25 -0400

Steve:

The BDC(s) still authenticate users after the PDC is upgraded to 2000/2003.
The issue you will have is that those computers/users that still
authenticate to the NT 4.0 BDCs will not be able to use Group Policies,
among other things. It's not a big issue at the early stages, though. Just
get your PDC upgraded first, then get rid of your NT 4.0 BDCs before you
start fully leveraging AD features such as GPOs. Feng gave you a few good
articles to get started on and I have some additional info below from
personal experience upgrading to 2003.

- Plan your DNS namespace well. This should be at the top of your list. For
example, if your current NT domain NetBIOS name is MYNTDOMAIN, and you want
to upgrade that domain (not migrate to a new domain), then you want to make
your DNS name myntdomain.local or myntdomain.net. There is some debate on
whether you should use .local, or a real top-level domain like .com or .net.
The NetBIOS and DNS domain names can be totally different, but for
consistency, it's best to keep have the NetBIOS name contained in the DNS
name.

For our company, we took our NT domain name and appended our Internet
registered domain name to it, so it ended up being
myntdomain.registered-domain.com. Note that myntdomain.registered-domain.com
is one domain, it's not a domain with a subdomain. This whole DNS thing can
get confusing, so the best thing to do is to make sure you run this through
in a test environment first to fully understand it.

- It's usually best to do a clean install of an OS - not an upgrade. That
being stated, what I did was use an older server that was previously
decommissioned. I added it to our domain as an NT 4.0 BDC, then promoted to
PDC, then ran the upgrade to 2003 on it. I then went to the server that we
specifically bought for use as our new 2003 DC and installed DNS and ran
dcpromo on it and seized all the FSMO roles from the PDC. I then ran dcpromo
on the PDC to demote it to a member server and then decommissioned it. As
you can see, the PDC was just used temporarily, so there is no need to use a
beefy server for that task if you have a small company of only a few hundred
users.

- Getting rid of your old NT 4.0 BDCs is pretty straight-forward. After you
are sure it is no longer needed for any resources such as file or print
sharing, just shut it down and delete the computer account from the domain.
You should also check WINS and DNS to make sure the server's entries are
removed.

There are a few other things to be aware of, but reading various articles
and books should fill in the rest of the pieces. If you have any more
questions after doing a test upgrade, feel free to post them to this
newsgroup.

Regards,
Martin
MCSA: M

"SteveW" <SteveW@=No=Spam.org> wrote in message
news:eJo8RVDhEHA.1344@TK2MSFTNGP11.phx.gbl...
> Thanks Martin,
>
> I will check out the KB, certainly, but it helps to be pointed in the
right
> direction first!
> What becomes of the BDC when the PDC has been upgraded? Does it have a
role
> to play in the upgraded domain? Or does it need to be removed or upgraded
> itself?
>
> Thanks again to you and Herb,
>
> Steve W
>
> "MartinHTN" <m@ht.n> wrote in message
> news:uEGdw96gEHA.1344@TK2MSFTNGP11.phx.gbl...
> > Steve:
> >
> > You must do the upgrade on the PDC. However, you can promote the best
> > candidate out of all your BDCs (or add a new BDC) to the PDC. There
should
> > be a plethora of articles from MS and others on doing such an upgrade,
so
> > check them out.
> >
> > Regards,
> > Martin
> >
> > "SteveW" <SteveW@=No=Spam.org> wrote in message
> > news:%231fgHt2gEHA.216@tk2msftngp13.phx.gbl...
> > > Hi,
> > >
> > > I have an NT domain with several W2k servers, and a BDC and of course
a
> > PDC.
> > > What is the recommended method for upgrading to 2000? Do I do the PDC
> > first
> > > then the BDC, or vice versa?
> > >
> > > Thanks
> > > Steve W
> > >
> > >
> >
> >
>
>



Relevant Pages

  • dcpromo fails on 2nd server after in-place upgrade of NT to W2K3
    ... After completing an in-place upgrade of our NT 4 PDC to Windows 2003 Server, ... I cannot run dcpromo to create a second domain controller on a server running ... The Active Directory name (and DNS zone) is MyDomain.com and the NetBIOS ...
    (microsoft.public.windows.server.active_directory)
  • Re: NT to 2003 domain upgrade - DNS related question
    ... running W2K3 on it as an upgrade, it will automatically assume the "PDC ... promo the new box to PDC, and THEN do the in-place upgrade. ... The problem is that you're going to lose your DNS server if you do plan B ...
    (microsoft.public.windows.server.migration)
  • NT4 to 2k3 in place upgrade rollback problems
    ... first BDC and promoted one of the new BDC's to a PDC. ... that PDC to 2k3 and AD adding DNS to the new DC during the upgrade. ... Then we turned back on the original PDC and 1st BDC in our NT4 network. ...
    (microsoft.public.windows.server.migration)
  • Recently Upgraded NT4 to 2k3 and having serious problems.
    ... subnets in 3 locations. ... the other NT BDCs are still online. ... Everything seemed to work fine after the upgrade until I ... found because the DNS Domain name could not be retrieved. ...
    (microsoft.public.windows.server.dns)
  • Re: DNS Name Convention or Spaces
    ... Was it still a PDC? ... You must NOT try to Upgrade a PDC unless you ... both the DNS and the NetBIOS domain names but be ... >>> The Provider has for example abc.com Domain Name. ...
    (microsoft.public.windows.server.migration)