Domain naming problem

[golfbill]

I have inherited a situation where I have 4 branch offices. Each is set up as its own network and server. The domains are all NT domain names that are the same name (abc). Later they found that (abc.com) was already taken as a FQDN and consequently they registered xyz.com). I am replacing the servers and installing win2k server on them. In planning for the domain naming structure for AD, what would be the best DNS naming scheme for each office. Should they all be in one domain, or should each office be a separate domain. ie, all offices using xyz.com for a domain vs. north.xyz.com, south.xyz.com, east.xyz.com, west.xyz.com. These are small offices of 30-40 users each. I would like to connect them via VPN eventually. I have a DSL in in each office and externally hosted email and web page.

 

[Antony13]

This decision needs really to based on the business needs. Is administration going to be centralised? Do you want people in one office to be able to access resources in other offices? If so, these are both justifications to have just the one domain. On the flip side, if administration is being done locally in each office with no need for administrators from one office to administrate another or if each office needs to be locked down securely so that users from one office can't access resources in another, these are both justifications for a domain in each (though these objectives can still be met with one domain, you just have to tighten security.

I suggest you read through some deployment documents located at:

http://www.microsoft.com/windows2000/technologies/directory/ad/default.asp

(click on Planning and Deployment Guides link). People who see me in this forum often will notice I keep getting people to plan before they deploy AD and that's because it really is so important to get it right otherwise you'll have a nightmare administrating it all!

Cheers, Antony