• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 212
  • Last Modified:

adding windows 2003 server to nt 4.0 network

I've been reading that adding a windows 2003 server to NT 4.0 network isn't a good idea.

I have a Windows Small Business Server 4 (which has windows NT 4 and Exchange 5.5) with about ten Windows XP professional workstations. And DDS-4 tape backup with Veritas software.

The server hardware is pretty old so we want to upgrade to brand new server hardward with lots of power and also to Windows Small Business Server 2003, rather than the 4.0.  And it also has DDS-4 tape backup drive with newer version of the Veritas backup Exec.

We also have a DSL internet service.

Now, what is the best plan of action to install the SBS 2003 and take down the SBS 4.0 and not lose any data and Exchange information.

I would like to find out the best step by step method for smooth transition.

Thanks,
0
dagatorman
Asked:
dagatorman
  • 2
2 Solutions
 
luv2smileCommented:
"I've been reading that adding a windows 2003 server to NT 4.0 network isn't a good idea."

Well it is not only just a bad idea...it is IMPOSSIBLE.  Windows server 2000/03 can't join an NT domain...it just won't work. Instead of doing an upgrade...you are talking about a migration.

Now.....you are talking about SBS which gets even more tricky.  SBS 2003 MUST be the FIRST domain controller in the domain....so you can't add SBS to any other existing domain. You must create a NEW domain for the SBS.

As for transfering your data, your best bet is to use the ADMT.

Here is the documentation you'll need from Microsoft:

http://go.microsoft.com/fwlink/?LinkId=16415
0
 
dagatormanAuthor Commented:
So,
1)  I would have to install SBS 2003 on a new domain name
2)  Add the SBS 2003 to the network.
3) Migrate the workstations to the new domain.
4) use ADMT to migrate the exchange files and other data files

Am I missing any steps?
0
 
luv2smileCommented:
Well...in a nutshell you are installed SBS with a new domain name and then migrating your data.  However, you will need to pay close attention to the microsoft link above and follow those step by step instructions exactly so you don't forget any important steps.  You'll need to use the Exchange Migration Wizard to migrate user mailboxes as stated in the above link.
0
 
Netman66Commented:
Windows 2000 and Windows 2003 servers can certainly join the domain - as members only, not as DCs.

Your best option...is to install SBS 2003 clean on the new hardware as a new domain, then copy over your shares and other data.  Recreate your users and rejoin the workstations to this new domain.  It's the cleanest method and gives you the opportunity to fix what you don't like.

You can then install Exchange and move the mailboxes from the 5.5 installation using any number of articles to help.

Here are a few:

http://www.msexchange.org/tutorials/Migrating_Exchange_5_5_to_2003.html
http://www.microsoft.com/technet/community/events/exchange2003/tnt1-100.mspx
http://itresearch.forbes.com/data/detail?id=1074104560_869&type=RES&src=TOPRES

Since you only have 10 users this (IMHO) is the approach I would take.  Its' called a parallel implementation.

Hope this helps.
0

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now