Domain name on install

  • Thread starter Thread starter DianeA
  • Start date Start date
D

DianeA

I'm finally moving my NT 4.0 SBS to Windows 2003. We have a small network
with one internal domain "NTDOMAIN" (not ntdomain.anything). I have DNS
running on a Windows 2000 server. I'm a little confused as to what i'm going
to end up with when I switch us to the Windows 2003 Server.

Because the SBS server hardware will not handle an upgrade, i'm going to
install NT 4.0 server on a new box and upgrade it to Windows 2003 and retire
the SBS server. I'm walking through the steps of the install to ensure i have
all my ducks in a row prior to the install.

When i get to installing AD I understand it will ask me to create a new
domain (Domain in a new forest)..
1. will it use "NTDOMAIN" at this point?
2. When it asks me to type full DNS name of the domain. do I use
ntdomain.loc (we don't have a registered name and have no need for one)
3. Can i change my domain to something else "newdomainname.loc" at any
point or am i stuck with NTDOMAIN.loc?

appreciate any help... not very good with domain name stuff.

Diane
 
Are you going from NT 4.0 SBS to Win 2k3 SBS or is the new install of Win
2k3 not SBS?


DDS
 
In
DianeA said:
I'm finally moving my NT 4.0 SBS to Windows 2003. We have a small
network with one internal domain "NTDOMAIN" (not ntdomain.anything).
I have DNS running on a Windows 2000 server. I'm a little confused
as to what i'm going to end up with when I switch us to the Windows
2003 Server.

Because the SBS server hardware will not handle an upgrade, i'm going
to install NT 4.0 server on a new box and upgrade it to Windows 2003
and retire the SBS server. I'm walking through the steps of the
install to ensure i have all my ducks in a row prior to the install.

When i get to installing AD I understand it will ask me to create a
new domain (Domain in a new forest)..
1. will it use "NTDOMAIN" at this point?
2. When it asks me to type full DNS name of the domain. do I use
ntdomain.loc (we don't have a registered name and have no need for
one)
3. Can i change my domain to something else "newdomainname.loc" at
any point or am i stuck with NTDOMAIN.loc?

appreciate any help... not very good with domain name stuff.

Diane
Click to expand...

You can make the AD DNS domain name any DNS compliant hierarchal name you
want, such as ntdomain.local, ntdomain.corp, ntdomain.diane, etc. Just don't
leave it as a single name such as NTDOMAIN or it will cause numerous issues.
It will also ask you to choose the NetBIOS name, which then of course I
would suggest NTDOMAIN.

--
Regards,
Ace

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT,
MVP Microsoft MVP - Directory Services
Microsoft Certified Trainer

For urgent issues, you may want to contact Microsoft PSS directly. Please
check http://support.microsoft.com for regional support phone numbers.

Infinite Diversities in Infinite Combinations
 
But can I change the domain name from ntdomain to a new name?

And to answer Danny's question.. This will be only a Windows Server 2003 not
SBS.
 
In
DianeA said:
But can I change the domain name from ntdomain to a new name?

And to answer Danny's question.. This will be only a Windows Server
2003 not SBS.
Click to expand...

If you currently have an NT4 SBS domain, and you install an additional NT4
BDC (which I believe you can do, but can't remember because SBS is a totally
different animal than regular Windows) in preparation to upgrade it to
Windows 2003 non-SBS, then NO, you cannot change the NetBIOS name. However
you can choose any DNS name you like. Once you remove the NT4 SBS from the
now new Windows 2003 AD domain, and bump up the functional level to 2003,
you can use the domain rename tool.

However, there are some caveats with SBS. Once you bring up the Win2003
server to a DC, it will want to hold the PDC Emulator role because the
domain is now an Active Directory domain. However NT4 SBS rules I believe
say it MUST be the PDC. If you have Exchange 55 on it and you want to
upgrade that to Ex2003, that adds to the stew.

You know, I would probably suggest to post this to the SBS groups for better
help.

Cross-posted to the microsoft.public.windows.server.sbs newsgroup and
follow-ups set to both.

Diane, you can simply check back here for any responses from the SBS folks.

Ace

For the folks in the SBS newsgroup, here is the original post in this thread
by the OP:
_____________________

I'm finally moving my NT 4.0 SBS to Windows 2003. We have a small network
with one internal domain "NTDOMAIN" (not ntdomain.anything). I have DNS
running on a Windows 2000 server. I'm a little confused as to what i'm
going
to end up with when I switch us to the Windows 2003 Server.

Because the SBS server hardware will not handle an upgrade, i'm going to
install NT 4.0 server on a new box and upgrade it to Windows 2003 and retire
the SBS server. I'm walking through the steps of the install to ensure i
have
all my ducks in a row prior to the install.

When i get to installing AD I understand it will ask me to create a new
domain (Domain in a new forest)..
1. will it use "NTDOMAIN" at this point?
2. When it asks me to type full DNS name of the domain. do I use
ntdomain.loc (we don't have a registered name and have no need for one)
3. Can i change my domain to something else "newdomainname.loc" at any
point or am i stuck with NTDOMAIN.loc?

appreciate any help... not very good with domain name stuff.

Diane
 
Ace seems to have the process down OK.

The key being that SBS4.x won't give up the PDC role. The process Ace
describes is sortta a 'partial swing' as described at www.sbsmigration.com.
Jeff would need to be informed about the netbios name change which is
desired.

I'd install a tempDC, NT4 as BDC (non-SBS), allow the domain to sync, then
take this one offline and assume the PDC role, remove references to the
original PDC, and take the NT domain to mixed mode AD by either upgrading
the now isolated tempPDC or using another box (or virtual machine), remove
tempPDC from the AD, raise the level so that you can then use RenDOM. The
swing docs would come in handy for references about checking and tidying the
AD at this point.

SBS4, wow, haven't heard it mentioned for a while. Why aren't you taking
them to SBS 2003? or maybe waiting a few more months and SBS 2008?
 
In
SuperGumby said:
Ace seems to have the process down OK.

The key being that SBS4.x won't give up the PDC role. The process Ace
describes is sortta a 'partial swing' as described at
www.sbsmigration.com. Jeff would need to be informed about the
netbios name change which is desired.

I'd install a tempDC, NT4 as BDC (non-SBS), allow the domain to sync,
then take this one offline and assume the PDC role, remove references
to the original PDC, and take the NT domain to mixed mode AD by
either upgrading the now isolated tempPDC or using another box (or
virtual machine), remove tempPDC from the AD, raise the level so that
you can then use RenDOM. The swing docs would come in handy for
references about checking and tidying the AD at this point.

SBS4, wow, haven't heard it mentioned for a while. Why aren't you
taking them to SBS 2003? or maybe waiting a few more months and SBS
2008?
Click to expand...

Thanks, didn't know I was that close with SBS. I wasn't sure if you can add
an NT4 BDC to it.

One more comment to Diane about the upgrade and add to SuperGumby's commet
about it being so old (which I agree) - I would probably in the face of the
system being old, install a fresh 2003 forest and migrate everything using
ADMT. This would eliminate some hassles with the name change as well as an
Exchange 55 to 2003 or 2007 upgrade making it easier just using an Exmerge
two-step, that is if Diane is using SBS' Exchange. It would also give a
fresh clean pristine start eliminating legacy data.

Ace
 
I agree with Ace here, to install a fresh, not-migrated SBS server and only
migrate users, settings etc instead of doing a partial migration that maybe
will bring some problems with it, Is what I would do. The std answer from MS
would be that your scenario Is not supported, to upgrade from NT to current
version. Jeff however has other possibilities.

How about the hardware? Have you purchased new HW or Is that on the todo
list fo this? If you are going to buy new, then also pls consider the
SBS2008 wich then will be usable on this new HW.

If going to 2003 anyway, pls consider an upgrade license option with MS wich
gives you right to upgrade to latest version (Im not good with these deals
and dont have the right name for It).
 
In
Henrik (Hear) said:
I agree with Ace here, to install a fresh, not-migrated SBS server
and only migrate users, settings etc instead of doing a partial
migration that maybe will bring some problems with it, Is what I
would do. The std answer from MS would be that your scenario Is not
supported, to upgrade from NT to current version. Jeff however has
other possibilities.
How about the hardware? Have you purchased new HW or Is that on the
todo list fo this? If you are going to buy new, then also pls
consider the SBS2008 wich then will be usable on this new HW.

If going to 2003 anyway, pls consider an upgrade license option with
MS wich gives you right to upgrade to latest version (Im not good
with these deals and dont have the right name for It).
Click to expand...

Henrik,
Thanks for the affirmation.

Also, she did mention:
"[...] install NT 4.0 server on a new box and upgrade it to Windows 2003
[...]"

But I'm not sure what the "new" box is.

Ace
 
:-) yes, that word "new" slipped me.. regarding the OS choice, just
wanted to pint out a possible advantage of maybe wait some more. Cant make a
"call" on here position on this ..
--
Henrik Arenblad, MCP SBS,


Ace Fekay said:
In
Henrik (Hear) said:
I agree with Ace here, to install a fresh, not-migrated SBS server
and only migrate users, settings etc instead of doing a partial
migration that maybe will bring some problems with it, Is what I
would do. The std answer from MS would be that your scenario Is not
supported, to upgrade from NT to current version. Jeff however has
other possibilities.
How about the hardware? Have you purchased new HW or Is that on the
todo list fo this? If you are going to buy new, then also pls
consider the SBS2008 wich then will be usable on this new HW.

If going to 2003 anyway, pls consider an upgrade license option with
MS wich gives you right to upgrade to latest version (Im not good
with these deals and dont have the right name for It).
Click to expand...

Henrik,
Thanks for the affirmation.

Also, she did mention:
"[...] install NT 4.0 server on a new box and upgrade it to Windows 2003
[...]"

But I'm not sure what the "new" box is.

Ace
Click to expand...
 
In
Henrik (Hear) said:
:-) yes, that word "new" slipped me.. regarding the OS choice,
just wanted to pint out a possible advantage of maybe wait some more.
Cant make a "call" on here position on this ..
Click to expand...

I agree. Let's see if Diane can elaborate.

:-)
Ace
 
Hi Guys... ok.. the renaming of the domain is not a big issue but more of a
nice to have at this point.

To clarify... My SBS is only used as domain controller. I have basically
moved everything from if over time and we don't have a local exchange server.

I have 2 BDCs on the SBS network, one which is on the Proliant ML370. This
is the one which I intend to promote to PDC (NT4.0) (It is also a fresh
install) and upgrade to Windows 2003 after I shutdown the SBS box.

My 2nd BDC is going to be shutdown also during all this to avoid corruption.
The SBS box will be retired and not brought back onto the network.

SuperGumby says to " remove references to the original PDC" ... I'm not
exactly sure what this means.


This has been very helpful... thanks
Diane
 
I will also add that my DHCP / WINS / File&Print / IIS / DNS all reside on
other member servers.
 
In
DianeA said:
Hi Guys... ok.. the renaming of the domain is not a big issue but
more of a nice to have at this point.

To clarify... My SBS is only used as domain controller. I have
basically moved everything from if over time and we don't have a
local exchange server.

I have 2 BDCs on the SBS network, one which is on the Proliant ML370.
This is the one which I intend to promote to PDC (NT4.0) (It is also
a fresh install) and upgrade to Windows 2003 after I shutdown the SBS
box.

My 2nd BDC is going to be shutdown also during all this to avoid
corruption. The SBS box will be retired and not brought back onto the
network.

SuperGumby says to " remove references to the original PDC" ... I'm
not exactly sure what this means.


This has been very helpful... thanks
Diane
Click to expand...

Thanks for elaborating. If you promote the ML370 to a PDC, shutdown the SBS
FIRST. I do not think it will allow itself to succumb to a demotion due to
it being SBS, Mabye Henrik can verify that. So make sure that whatever apps
or services or files, etc, are on the SBS, that when you go to promote the
new machine, make sure you are ready to turn it off for good.

Ace
 
Thanks Ace... SBS cannot be demoted.

I've turned it off last night and letting BDC do the authentications.. All
appear great so far.. working on the Upgrade today...

Thanks for everyones assistance, sure does make it easier to bounce
questions off others.

Thanks again
Diane
 
Hi, If Im not misstakened here you are right, Ace.
Cant see that there is something else.
 
In
Henrik (Hear) said:
Hi, If Im not misstakened here you are right, Ace.
Cant see that there is something else.
Click to expand...

Thanks, Henrik. I wasn't sure, but one thing I AM sure about is when it
comes to SBS, there are always some sort of limits and gotchas that I'm not
aware of and assume the worse until I find out otherwise!

:-)

Ace
 
In
DianeA said:
Thanks Ace... SBS cannot be demoted.

I've turned it off last night and letting BDC do the
authentications.. All appear great so far.. working on the Upgrade
today...

Thanks for everyones assistance, sure does make it easier to bounce
questions off others.

Thanks again
Diane
Click to expand...

That's what we're here for. Glad everything worked out with the upgrade.
Once you remove all of your NT4 BDCs, bump the domain and forest functional
levels to Windows 2003.

Keep in mind as well that there are differences in attributes (more than
double withif I remember) and limitations with upgraded user accounts from
NT4 compared to newly created user accounts. Some things may not work with
them that work fine with a newly created account. You can use LDIFDE to
export a new user and an older user account and compared the attributes. I
remember wireless issues a few years back with a Sony AP. It would work with
new users but not with users upgraded from NT4. After some research, I found
out the differences were due to missing attributes in the older accounts and
how specifically the Sony APs authentication works. I recommended that the
client purchase a Cisco 1231 AP to resolve the problem. I've heard of other
minor issues as well.

Someone's always here, so post back if you have any questions with your new
domain.

:-)

Ace
 
Back
Top