New SBS 2003 Server

tommy2684

n00b
Joined
Oct 8, 2007
Messages
14
All,

A client currently has an old server running SBS 2003. We are upgrading them to a brand new server! How can I migrate the data (Exchange, BES, AD info) to the new server?

We are going to reuse the current SBS 2003 license and will have to install it onto the new server. I know that SBS 2003 does not play nice with other SBS 2003 server.

What can I do?
 
my company does it all the time.

Export each users exchange data into a .pst file
then on the new server just re-import it.

also for network shares use robocopy.

That's exactly how I did it for a customer going from SBS2000 to SBS2003 recently and it worked very well.
 
Another nod for the sbsmigration kit, well worth the $$

lots of tips and great instructions, plus he is available for help via email/phone

How much file server data do you have to move to the new server?
Can you move it and all the Exchange info over to the new server without interupting the business? (ie you export the exchange mailboxes to PST on Wednesday, then import it on Thursday to the new server, then spend xx hours moving file share data to the new server and then the PST's arent current.)

one thing to remember is you obviously cant have the same server name on both servers at the same time if they are on the same network.......

If you are keeping the same domain name and dont want to mess with fixing the users profiles on the workstations, the migration kit helps alot.
Plus if the server names end up being different...all the shortcuts that users had to \\server\share\file.ext wont work since the 'server' part would be different
 
Anything wrong with the old servers software setup? If not I'd consider moving the partitions over to the new server and getting everything resetup that way.

Other then that the swing method is pretty good. You can also just export the exchange database and move it over as others have said.
 
If it's a small enough network..all in one spot, easy way is what I'm doing this weekend...pull mail to PST...put PST file in neutral location on the workstations C drive...remove from old domain. Copy data from old server to new server. Join workstations to new server. Import PST file to Exchange.
 
If it's a small enough network..all in one spot, easy way is what I'm doing this weekend...pull mail to PST...put PST file in neutral location on the workstations C drive...remove from old domain. Copy data from old server to new server. Join workstations to new server. Import PST file to Exchange.

QFT

It's a huge PIA to do a migration properly. It almost generates more work than you are saving (and can cause it's own problems) and the work you are saving is at least easy in terms of brain power. Just boring and time consuming. I'd rather take boring and time consuming vs. possibly screwing up a complicated migration and having to start over again anyway.

Visiting all of the workstations is an easier job if you write up a checklist and split the workstations among several people. That gives you more time to work on server issues and any workstation snafus.

Just be careful when you unjoin the old domain, XP wipes the local accounts when you do that. Not a problem if you backup what you need first.

Make good notes on server shares too.
 
If it's a small enough network..all in one spot, easy way is what I'm doing this weekend...pull mail to PST...put PST file in neutral location on the workstations C drive...remove from old domain. Copy data from old server to new server. Join workstations to new server. Import PST file to Exchange.

One thing worth adding to this is when you demote the machine off the old domain rename the profile for the user on the machine to something elce. IE add a .old or .temp or something to it. That way when you add the user to the new domain it creates the profile in the same folder as the old one was in(asuming user names are the same). That way you can override it with the old profile and have it be in the same place(some programs will have to be resetup if you don't do this).
 
QFT

It's a huge PIA to do a migration properly. It almost generates more work than you are saving (and can cause it's own problems) and the work you are saving is at least easy in terms of brain power. Just boring and time consuming. I'd rather take boring and time consuming vs. possibly screwing up a complicated migration and having to start over again anyway.


How many times have you used the SBS Migration kit? I've done at least 15-20 servers that way and I can tell you for a fact that you will save a lot of customer downtime using it compared to exporting PSTs and touching every workstation to disjoin/rejoin to the domain. The overall time into the project isn't much lower doing the swing migration, the benefit is in the downtime for the client, or saving you from having to work on the weekend. I recently swapped out a server with only about 4 hours of downtime, and that included a major re-arranging of the area the server was setup in. I've also never had an issue with a migration that I couldn't fix with either 5 minutes of searching on google or checking the sbsmigration forums. The money for the migration kit is easily some of the best money my company has ever spent. The only time I wouldn't recommend it is if you've had a lot of problems with your current AD, then just start fresh.

Also if you are moving to an HP server they have a very nice migration tool that will image the old server to the new one and insert all the proper drivers for the new hardware. I think it runs $150-200 or so, which is much cheaper than using something like Acronis Trueimage with Universal Restore, which would also do the same sort of thing.
 
Also if you are moving to an HP server they have a very nice migration tool that will image the old server to the new one and insert all the proper drivers for the new hardware. I think it runs $150-200 or so, which is much cheaper than using something like Acronis Trueimage with Universal Restore, which would also do the same sort of thing.

Got any extra info on this and have you tried the tool? Sounds interesting.
 
Got any extra info on this and have you tried the tool? Sounds interesting.

412978-B21, that's HP's part number. You can purchase just the license and then download the software from their site. We've used it 3 times so far, and it's worked pretty well.
You have your old server and then the new hardware, and you install the software on a PC that acts as the middle man, and images the old server to the new.
 
Back
Top