Re: Setup new Windows SBS 2003 R2 on NT 4.0 network
You might want to look at your plan more carefully.
You can not add the SBS server to the NT 4.0 domain and have it take over
the NT 4.0 server roles.
In order for the SBS server to take over the NT 4.0 domain you MUST upgrade
the NT 4.0 PDC first. The NT 4.0 PDC is the only server on the NT 4.0 domain
that holds a writeable copy of the SAM. In order to carry that SAM into the
AD domain you MUST upgrade the NT 4.0 PDC. Upgrading or adding *any* *other*
server will create a NEW SAM. New SAM = new domain (even if you name the new
domain the same name, which put you on the path to a position that may take
a format and reinstall to recover from). You will be stuck recreating your
users from scratch and removing each computer from the NT 4.0 domain and
adding it to the AD domain and a new profile will be created.
Look into ADMT. you can set the AD domain and the NT 4.0 domain "side by
side" on the same wire and use ADMT to migrate the users from the NT 4.0
domain to the AD domain. Of course you would have to create a trust in order
to use ADMT. When creating a trust you can not have two domains with the
same name, so if you need to keep the same domain name you need to work out
either renaming the NT 4.0 domain before you start and name the AD domain
what you need it to be OR create the AD domain with a temporary name and
rename it, as the final step, to what you need the name to be.
hth
DDS
"JP" <JP@discussions.microsoft.com> wrote in message
news:19897864-52BA-4FF6-9BBB-ED19D4C36088@microsoft.com...
> Will be installing SBS 2003 R2 on a new HP ML350 G5 server. Need advice
> on
> best way to proceed. Network currently has two NT 4.0 servers, one domain
> server, one backup. I want the SBS to take over as the primary server
> while
> still having the NT servers available so that data folders and other items
> may be transfered over in the following weeks.