Choosing my new namespace?

  • Thread starter Thread starter Mark N.
  • Start date Start date
M

Mark N.

Okay, can somebody make a recommendation for me? My Windows network domain
is named "entire_company" - not sure why, but that's how I found it when I
started here four years ago and changing it wasn't an option at that time.
So now that I'm getting ready to implement active directory, I want to
entertain suggestions for naming my namespace. I have a very simple domain
structure - just one building; no future growth beyond is anticipated; only
about 100 nodes.

If my company's actual domain name is registered, I should probably include
that as the root in my namespace? So when I'm asked for a namespace, what
do you all suggest? Do I need that "entire_company" in the namespace?

Thanks,
Mark
 
Mark,

You might consider 'yourdomain.com' - the same as your registered
namespace - or you might consider 'yourdomain.local'. There are pros and
cons to both. I typically use the registered domain name but have set up a
couple of .local domains.

You do not want to have an underscore ( the "_" ) in your domain name -
neither the DNS name nor the NetBIOS name. It will give you grief. You
also do not want to have a single-label domain name ( which would be
'yourdomain' - notice there is neither the .com nor the .local on the end ).

If you have the hardware you might want to set up the WIN2000 domain with a
proper domain name, set up a trust between the two ( the new WIN2000 AD
environment and your existing WINNT 4.0 domain ) and use ADMT v2 to migrate
the user account objects, computer account objects and group accounts over.

I presume that you have Exchange involved somewhere?

HTH,

Cary
 
If you have the hardware you might want to set up the WIN2000 domain with
a
proper domain name, set up a trust between the two ( the new WIN2000 AD
environment and your existing WINNT 4.0 domain ) and use ADMT v2 to migrate
the user account objects, computer account objects and group accounts over.

I presume that you have Exchange involved somewhere?

HTH,

Cary
Click to expand...


I only have an NT4 domain but have all Win2K and 2003 Servers (except for my
PDC and BDC). I had planned on building a new NT4 machine and when the time
comes, promote that to PDC and then do an upgrade to retain the domain
information. I've been trying to do this in a non-destructive, experimental
fashion by pulling a BDC offline, promoting it and then running the
upgrade - just to see what I can expect, but it's angry that I haven't
connected it to the network.. I'm building another test machine right now
and will just make it a PDC in a new domain and test that.

The not-knowing-what-to-expect is the worst part of all of this. I do have
an Exchange 5.5 box running too.

The ADMT v2 migration is something I hadn't heard of. I don't know anything
about that. The more I read and research, and the more I ask questions
here, the more complicated this whole thing gets :-(

Mark
 
If you have the hardware you might want to set up the WIN2000 domain with
a
proper domain name, set up a trust between the two ( the new WIN2000 AD
environment and your existing WINNT 4.0 domain ) and use ADMT v2 to migrate
the user account objects, computer account objects and group accounts over.

I presume that you have Exchange involved somewhere?
Click to expand...


Let me see if I'm following you here...

I can take a spare server; install Win2003 Server and configure that
namespace as I'd like; then establish a trust between it and my current
domain; then migrate (copy?) my accounts and stuff over to it; then have my
existing servers "leave" the old domain and join the new one?

Is this right?
 
Back
Top