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

Migrating OS (2000 to 2003), Exchange (2000 to 2003), and changing domain name, new hardware. Need advice!

I have a single-server LAN that would like to upgrade to the latest Microsoft has to offer.  I know it is going to be a multi-step procedure, but I am not sure what order to do them in and if there is preparation that needs to be done ahead of time, aside from the obvious backup :)

The current server is:
Windows 2000 SP3
Exchange 2000 SP3

I would like to set up a totally new server with SBS 2003 and move the all the users over to the new server.  For an extra layer of complexity, I need to change the domain name.

After everything is moved, the old server will still be utilized, but for less intensive work -- (print server, ftp, etc.).   Should I recommend an upgrade of the old server to 2003?  Should I do a clean install or upgrade?  

You don't need to detail procedures that I can find at MS and here, but pointers to the appropriate articles would be nice, as there are so many it's difficult to sift through them.

0
AbsentMindedProf
Asked:
AbsentMindedProf
  • 2
1 Solution
 
HousenetCommented:
Hello,
I havent used SBS 2003 yet but if its anything like all the other crappy sbs versions, there are many limitations. For example it must be the FSMO master and cannot be added as a second domain controller.

Since you would like to get a fresh start with a new NOS, domain name and exchange this is what I would do.
1. Setup the SBS server and exchange on the new server.
2. Use exmerge to export all the exchange items out of the 2000 server.
3. Export the user accounts using a resource kit utility. I would use ideal migration because it will include the passwords and is very easy to use.
4.Use exmerge to import all the exchange stuff into 2003 exchange.
5. Create an x500 address that matches the old 2000 info in the 2003 recipient policy so when users reply to old emails to each other, it works.
0
 
AbsentMindedProfAuthor Commented:
I know I will have to update the domain on each workstation.  Will this pose any difficulties with Outlook?  

I would also like to rename the workstations (the names they have now follow no convention) but that may be adding too many variables to the stew.

I don't think #5 is necessary in my case as outside email gets transferred to the Exchange server by means of a POP3 downloader (POPCon) and I can reconfigure that easily to point to the new server and new email addresses.  I realize EX2003 has that built in, but the frequency it checks for new mail is no less than every 15 mins.  POPCon is configurable down to a minute and the users need this kind of instant communication.  POPCon is one of the services I plan to leave on the old server.

What about the old server?  Should I upgrade it to 2003?  Since it is set up as a DC with a different domain name, what should I do to it?  Should I shut down or remove the DC on the old server?

AMP

PS:  I checked out Ideal Migration and it looks like a very useful tool.  I will probably get it.

0
 
HousenetCommented:
Hello.
Unfortunatly #5 is needed.  Popcon is fine as a means of collecting internet email.. Here is what Im talking about...

Exchange 2000 User1 send internal email to user2....great...
-You transfer everything to exchange 2003... no problem.
NOW: User2 decides, I want to reply to that old message user1 sent him.. he hits reply BLAM! problem... Why? Because Exchange uses x400 addressing to determine, locale, site, server, user. When the user hits reply the X400 Address details will be wrong because it was specific to the old exchange.
EASY Solution= create an x500 address that contains the old info... There are MS articles that walk you through step by step... its pretty simple.

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