W2K DC relationship to NT4 PDC/BDC Question.

[artadmin]

This is probably a silly question. I have a NT 4 domain in place. I'm preparing to add W2K Terminal Servers to the domain, and wish to take advantage of GPOs. I may be wrong on this, but it seems that without AD, you only have one GPO (local machine) that applies to all users on that computer. So I am thinking I need a W2K DC in my current domain, so that I can create domain and site GPOs. If I'm off on this, please tell me.

So, if all the above is true, my question is:
In a mixed-mode environment, can a W2K DC be in a domain whose PDC is NT4? Or. . . does W2K have to be a DC, and all NT 4 servers are BDCs of W2K?

 

[yawnbob]

You can have a W2K server as a member server of the NT4 domain but then you can't install Active Directory on it. That can only be created on a W2K DC.

So to create that first W2K DC you have to upgrade your current NT4 PDC and it then takes on the role of PDC for the NT4 BDC's.

If you have a concern about doing this to your PDC (as most of us who have done this have had) you can take a spare (but reliable) machine, install NT4 server on it and make it a BDC, syncronize the domain, then promote it to PDC. Upgrade the new PDC to Windows 2000. If you have problems you can always shut off the new server and promote your original PDC (which was demoted) back to PDC.
"Time flies like an arrow. Fruit flies like a banana." - Groucho

 

[artadmin]

In short, You must have 1 W2K DC, the rest of you NT domain controllers act like BDCs? -crap!

 

[artadmin]

Just to clarify. I was swearing about microsoft, not your response. Thanks for telling me how it is.

 

[yawnbob]

I understand. I usually use much stronger adjectives when I'm refering to Micro$oft.
"Time flies like an arrow. Fruit flies like a banana." - Groucho