Internal domain naming for NT4 to Win2k migration

We are in the beginning stages of planning the migration from 4.0 to 2000. We have 70 servers, 1300 users, 10 office locations. We have a registered domain name for Internet access and a private internal domain space called FIRM. Our Exchange config for Org=FIRM, Site=location of office server=each office has its own Exchange server. What is your opinion on what we should have as an internal name? Should we keep it as is, knowing it can never be used externally? Should we change it to FIRM.OURCOMPANY.COM for the 2000 rollout? Or change it to our external registered name?
I would change the domain name to FIRM.OURCOMPANY.COM. This should make it possible for you to still access the Internet and potentially have Internet traffic routed into your network. At the same time you are protecting yourself to a certain degree since FIRM.OURCOMPANY.COM is not an Internet published domain name.
This was first published in February 2001

Dig Deeper on Microsoft Active Directory Migration



Find more PRO+ content and other member only offers, here.

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.



Forgot Password?

No problem! Submit your e-mail address below. We'll send you an email containing your password.

Your password has been sent to:









  • VDI assessment guide

    Wait! Don't implement VDI technology until you know your goals and needs. A VDI assessment should consider the benefits of a VDI ...

  • Guide to calculating ROI from VDI

    Calculating ROI from VDI requires a solid VDI cost analysis. Consider ROI calculation models, storage costs and more to determine...

  • Keep the cost of VDI storage under control

    Layering, persona management tools and flash arrays help keep virtual desktop users happy and VDI storage costs down.