Join or sign in Register for your free TechRepublic membership or if you are already a member, sign in using your preferred method below. Use Your Email Use FacebookUse Linkedin

NT4 PDC replaced by Win2K w/o AD?

Locked

We are currently running NT 4 on a 5 year old server that is our PDC. We have 7 people that connect to the domain.
We are looking to buy a Dell Server running Win2K.
If we run the Win 2K Server without Active Directory and no local DNS, will we be able to replicate the User Accts from our NT4 domain controller, then remove it from the domain and have the Win2K server handle domain logins?
Or is AD the only way to handle domain logins in Win2K?

Topic

NT4 PDC replaced by Win2K w/o AD?

In reply to NT4 PDC replaced by Win2K w/o AD?

Installing AD is the only way a Win2K server can become a domain controller (DC).

Further points:
1. A Win2K DC CANNOT exist in a NT4 domain.
2. To migrate a NT4 domain to a Win2K domain, Win2K (and AD) MUST be installed on the NT4 PDC.
3. AD requires access to a DNS which allows Dynamic Updates (which usually means setting up a local DNS server as most ISPs don’t want you dynamically updating their DNS servers).

You pretty much have 3 options in your situation:
1. No migration – Create a Win2K DC and recreate user accounts from scratch (with the number of users you have, this will be your least labor-intensive option).
2. If your old server meets minimum hardware requirements for Win2K and the NT4 install isn’t too messedup – Upgrade your old PDC to Win2K. AD installation will start automatically once Win2K recognizes it is being installed on a PDC. You may need to create a DNS server locally if you aren’t currently hosting your own DNS (see point 3 above). Promote your new Dell server to DC by installing AD. Force replication of the domain and transfer all server roles to the new server. Demote old server and remove from the domain (if that is your ultimate goal).
3. If the old server can’t meet hardware requirements or your NT4 install is hosed – (you’ll love this) Remove Win2K from the new Dell box and install NT4 as a BDC. Force synchronization from the PDC to the BDC. Promote the BDC (new server) to PDC. Remove the BDC (former PDC) from the domain (to be used as a fallback in case the Win2K install goes south). Reinstall Win2k on the PDC (new server) (to include installing DNS if necessary).

(continued)

NT4 PDC replaced by Win2K w/o AD?

In reply to NT4 PDC replaced by Win2K w/o AD?

None of the 3 choices is optimal. Option 1 entails recreating your domain structure. Option 2 leaves you with no fallback position in case of a Win2k install gone wrong (unless you have other BDCs available). Option 3 requires you to go through the pain and suffering of installing NT 4 on your new server and then reinstalling Win2K (unless you have other BDCs available that meet hardware requirements for Win2K).

A long-winded answer to your question, but stuff you need to know.

NT4 PDC replaced by Win2K w/o AD?

In reply to NT4 PDC replaced by Win2K w/o AD?

Poster rated this answer

NT4 PDC replaced by Win2K w/o AD?

In reply to NT4 PDC replaced by Win2K w/o AD?

The answers Tim gave are correct. I only wish to visit the need for a domain currently when you only have 7 people connecting. Is this for any particular application that requries a Domain, such as Exchange? If not you may want to consider going peer-to-peer.

If you ar eusing Exchange you may want to research the possiblity of using the Small Business Server by Microsoft, SBS does have some limitations but usually these don’t come into play for smaller domains (less than 50 users)

NT4 PDC replaced by Win2K w/o AD?

In reply to NT4 PDC replaced by Win2K w/o AD?

Thanks for the suggestion, but it didn’t apply to the installation. There is no SBS, nor Exchange.

NT4 PDC replaced by Win2K w/o AD?

In reply to NT4 PDC replaced by Win2K w/o AD?

This question was closed by the author

[Author]

Replies