Problem solve Get help with specific problems with your technologies, process and projects.

What OU naming convention is best to use internally?

I am in the process of planning my migration to Windows 2000 and I want to get it right. I currently have a single NT4 domain with one PDC, four BDCs and multiple application-specific standalone servers spread over three sites. The sites are connected by WAN links and each site runs Exchange 5.5 on the BDC.

I have a 2 MB connection to the Internet and run three different domains (i.e., x1.co.uk, x2.co.uk, x3.co.uk). These are used for identifying specific parts of the business to external clients, but are not used to distinguish internally.

If I want to maintain the single domain model internally and split the business using organizational units (OUs), what naming convention is the best to use internally? Should I use a .msft, a .dom or something else, like my primary external domain name (i.e., x1.co.uk)?

Thanks for any help and advice.

If none of the systems needs to be recognized externally, you can use whatever you like. I generally use ".local" -- seems to me this has no hopes of ever being a qualified Internet domain name. Using a sub-domain of the external domain will make the Exchange a touch easier, but I like keeping things separate myself.

Dig Deeper on Windows systems and network management

Have a question for an expert?

Please add a title for your question

Get answers from a TechTarget expert on whatever's puzzling you.

You will be able to add details on the next page.

Start the conversation

Send me notifications when other members comment.

Please create a username to comment.