AD Domain Naming Constraints with Existing NT Domains

  • Thread starter Thread starter Shawn Skillman
  • Start date Start date
S

Shawn Skillman

We currently have an NT domain named 'VCFCORP'. I am setting up a Win2k
parallel AD domain for migration and would like to name it 'VCFCORP.com'.
In the context of domain naming would this cause any issues with the
existing domain? Are they considered seperate domains? We currently own
the internet .com address as well. Any help would be appreciated. Thank
you, SRS
 
We currently have an NT domain named 'VCFCORP'. I am setting up a Win2k
parallel AD domain for migration and would like to name it 'VCFCORP.com'.
In the context of domain naming would this cause any issues with the
existing domain?
Click to expand...

Yes -- by default VCFCORP.com Win2000 domain will use VCFCORP
as it's legacy NetBIOS name which will conflict with the existing domain.
You can alter this name but then it will later confuse people.
Are they considered seperate domains?
Click to expand...

Yes, if you mean NEW domain -- you want to do an UPGRADE, by upgrading
your PDC, you will upgrade the domain to Win2000.

If you are fearful of such an upgrade, you can take a BDC offline
(install an extra one first if necessary), and run it own a SEPARATE
network where you promote it to PDC and test, but ultimately you
will want to UPGRADE the existing domain in almost all cases.

(It's almost painless for almost everyone to just upgrade and NT/9x
boxes work just as well in a Win2000 domain as they did in an NT
domain -- perhaps better.)
I
We currently own the internet .com address as well.
Click to expand...

That helps.
 
Back
Top