[535] in winnt
Re: NT/win2k Server issue
daemon@ATHENA.MIT.EDU (Bob Kaynor)
Tue Aug 29 14:55:25 2000
Message-Id: <4.3.2.7.0.20000829144601.01143a70@po12.mit.edu>
Date: Tue, 29 Aug 2000 14:55:15 -0400
To: Barbara Santorella <bsantore@mit.edu>
From: Bob Kaynor <bkaynor@MIT.EDU>
Cc: ntpartners@mit.edu
In-Reply-To: <39AC0415.44B6637A@mit.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
At 02:42 PM 08/29/2000 -0400, Barbara Santorella wrote:
>Bob Kaynor wrote:
>
>According to http://web.mit.edu/is/help/windows/winnews.html, it's win2k
>*Domain Controllers" that are not allowed on MITnet. I assume if I try to
>upgrade an NT domain controller, that it will become a win2k domain
>controller. (I don't know -- does it ask me?) I guess my best bet would
>be to
>wipe out the NT partition and do a clean install.
NT 4.0 domains and Win2K domains are *completely* different animals, even
though the terminology looks familiar. Win2K wants to own everything
(would you expect anything less...?). I don't remember if it's possible to
treat a Win2K server as a "member server" in an NT 4.0 domain, but I don't
think so. In any case the PDC/BDC concept doesn't exist anymore in Win2K -
authentication schemes, hierarchies, and trust relationships aren't the
same anymore.
>Thanks, this is good to know. (why PDC over BDC?) I have a P200 with IDE
>disks that I can use. I think I will install NT server on this first and make
>it a backup domain controller (and then promote it to a PDC). Next, I will
>wipe out the NT partition on the current backup server and do a clean install
>of win2k on it. Then, I'll upgrade my backup software on that
>machine. Sounds
>like a plan.
In general, the PDC manages relationships among computers and the BDC
handles login requests (actually, it depends on which one is physically
closer on the wire to the user machine). PDC activities are not
CPU-intensive; just give the system enough memory and a reasonable hard
disk (IDE is fine), and it's happy.
-RKK
