Help adout migrate from NT4 to SBS

I have to migrate a NT4 server to a sbs2003 server, on a new hardware.
Microsoft documents tell to install SBS, create a new domain with different
netbios name and then migrate with AMDT, also from w2000 srv to SBS2003.
Instead of this, can I upgrade then NT4 server to 2000 server ( and this
convert all accounts to AD) , then add the SBS to the 2000 domain ,
sincronyze AD and then remove the old server with dcpromo? Any experience
about this? Or where can I find docs?
Thank you
Alessandro

 

You can't upgrade NT4 to SBS 2003. You'll have to go with the document
migration from SBS 4.5 (NT4 /Exchange 5.5) to SBS 2003. This works
perfectly. It will transfer the user and computeraccounts and the mailboxes
and shared folders.
Do you have that document yet?

 

I don't want to upgrade NT4 to SBS, but NT4 to 2000 and then add the new
SBS2003 to the existing domain.
I've read somewhere that SBS2003 allow to have an other 2000 domain root
server for a shot time, in order to allow this operation.
Yes, I have the document, I hoped to do the migration without change then
netbios domain name, but as you write it is not possible, isnt'it?
Thank you
Alex

 

What is wrong with changing the domainname? You're going to a double process
if you first upgrade to SBS 2000 and then to 2003.

--
Regards,

Marina
Microsoft SBS-MVP

 

I do not believe that SBS 2003 will allow any other server
to be root of the domain, so joining it to another domain
is not possible - I will check, but this is the golden
rule as I understand it. You can have other AD servers in
an SBS 2003 domain

thanks

David

 

I don't have to upgrade to SBS2000: my actual server is a NT4 server (not
SBS), so I'd like to upgrade this to 2000 server.
The problem is not also about the domain name: I 'd like keep the old nt4
(upgraded to 2000) still working on the network to have more time to
complete all the migration from the old server to the new one.

Ciao
Alessandro

 

How about this as a process - I am assuming your SBS 2003
system will be on a new server:
1) add new server - load NT4 (I assume you have a legal
copy of this & other OS's)
2) DC promo to a BDC
3) turn off existing PDC (just in case it all goes pear
shaped)
4) BDC -> PDC
5) In place upgrade to W2K
6) In place upgrade to SSB 2003 as per :
http://www.microsoft.com/technet/prodtechnol/sbs/2003/Plan/
GSG/CHPTR3B.asp
or
http://go.microsoft.com/fwlink/?LinkId=16414

How does this sound?

From a licensing point of view, you would need a legit NT4
& W2K license for new system for use during upgrade
process, although a eval copy might be sufficient here and
there may be "downgrade" rights to NT4 from a W2K
license. Also W2K could be a copy of W2K3 I believe.

Potential issues:
1) I might have process wrong
2) NT drivers for new hardware might not exist

thanks

David

 

You can not have two machines on the network with the same
name.

I have given you a process in my other post that might
help get your users to SBS 2003 without them having to
change settings. If you then wanted to use resources on
the NT4 box in W2k mode, you would need to DCPromo the box
down to a member server, then upgrade to W2K(3) and then
DCpromo to join SBS 2003 domain.

thanks

David

 

Yes, it sounds much more complex,
the idea of upgrade NT4 to 2000 is usefull only if then is possible to
join the new SBS2003 to the 2000 AD.
Thank you .
Alex

 

The whole point is that SBS is not joining another domain,
but it is the root of the domain. One of the few rules of
SBS vs WIndows Server std.

By doing it this way, the PDC is the root of the NT4
domain, the new system becomes the new root of the NT4
domain and then is upgraded - all on the new system so SBS
is happy at being the root.

thanks

David

 

Hi There,

It has taken me ITRO 1 week to finish a "hot swap" of an
NT4 domain with Ex 5.5 to SBS 2003. With no real
experience of this, it has gone through ok and there are a
few little Admin niggles left to sort but nothing in terms
of users.

I completed this on my own in a 24/7 environment running a
separate SQL box and also changed the domain name (due to
the fact that the old domain name had NT in it)

The basic way I did it (depending on the no. of clients
you have (I had 25) and if you have a new server) was
quite a manual way but it worked:

1) dcpromo the new SBS2003 server keeping it off of the
existing network

2) Create all users in AD - ip ranges etc

3) Complete necessary updating

4) Create .pst files on the users computers for emails /
Public folders. Take old PDC offline. Make copies of
favs / desktop / docs and put in root of c: on client pcs.

5) join servers / PC's to new domain.

6) Set up desktops and reimport .pst


It took a approx. 8 full hours through the night to do the
above on my own and also I had to reset share permissions
and SQL security.
The bulk of it though was in the morning when the general
users queries came.

Don't forget to take the old PDC/BDC offline because it
repopulated the dns on the all the servers and I got
called in the day after at 0230 because nothing worked..
grr.

I was a satifying experience but very hard work yet
worthwhile now.

Hope that is ok but it is very brief,

Si