Windows

Things to watch out for:

First I would either create a BDC and syncronize it. Then take it off line to preserve the SAM. Or take off an existing BDC.

The pro is when you're all done you can go to native mode and implement Active Directory. You can also begin using DFS.

I really don't know of any technical cons, just the expense of upgrading all the CAL's.

Chapter 10, Deployment Planning Guide, Windows 2000 Resource Kit. It is your domain migration's best friend.

Back up your file and print services or DHCP services that are running on your PDC or BDCs. Test the tapes.

Fully synchronize all BDCs with the PDC. Take one offline for disaster recovery of upgrade, upgrade it to PDC and check the data.

Have contingency plans and utilize them. Don't keep going if any part of the upgrade seems to fail.

In addition to the very accurate answers so far:

It sounds like you run 1 domain, with your remote locations being connected by lease lines (T1s, ISDN, etc). You can keep the same single domain AD structure in your new rollout. If so, then I suggest setting up each remote location as its own Site. You would then set up the computers and users who only log in at these remote Sites within the Sites themselves. This logically organizes all of the objects. (and yes, users are objects just like printers and computers; we are no longer individuals! Sounds Borg-like.) Sites look very nice on paper for management-types too!
Here is a URL on AD structure:
http://www.microsoft.com/windows2000/techinfo/planning/activedirectory/adsites.asp
(please remove any spaces)

Hope this helps.

- Sync the BDC with the PDC and take it offline in case you need to roll back.
- AD requires that DNS server be on the network so if you don't have one you can choose to install DNS on the PDC you are upgrading. W2K uses DNS for name resolution but is also backwards compatible with NetBIOS so be aware.
- Your domain must run in mixed mode until all of the BDC have been upgraded to W2K b/c if you switch to native mode your BDC's will no longer be able to sync with AD.
- Make sure your documentation is up-to-date because some programs and drivers might not be compatible.
- You will love the centralized user administration and group policies. Service Pack installs w/ GPO's are the best, it will save you a lot of time down the road.

Good luck.

This question was auto closed due to inactivity