Question Locked

Replacing an Exchange Server (SBS 2003) - possible pitfalls?

0 helpful
6 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Okay, I need some advice. Back in the late 90's early 00's, I worked in IT and I was NT 4.0 certified, but I left the IT world around the time Active Directory started really appearing at my workplace, so I only have limited understanding of changes since Server 2000. So, I know enough to really screw everything up! I need help though:

I have a single server domain running MS Small Business Server 2003 and running Exchange 2003 with a static IP address. I need to replace/upgrade the server so the hardware is totally different.

What I want to do is:

1-Build the new server and join it to the domain (I have already done this part)
2-make the new server the Domain controller (I already read on here how to do this - but I have questions)
3-migrate our proprietary database over to the new server (I can handle this too)
4-migrate exchange over (HELP!)
5-give the new server the old server's static ip address and shut down the old server.

I really, really want to avoid having to re-create the user profiles and, consequently, reconfigure all the clients because that is really time consuming and we lost peoples data last time this happened.

Thing that I want to try: I want to try doing a clean install of Exchange on the new server and then just copy over the settings and files from the old server, essentially just overwriting the settings. Things like that used to work in the old days, will it work with Exchange '03?

Thing that scares me: All our user's desktops and documents are stored on the server, will this migrate automatically when I make the new server the Domain controller or does all that have to be done manually?

Also: should I rename the new server to the old server's name once all is said and done?

6 replies

by cg it

though you can have a stand alone Exchange Server you would be better off to do a migration to new hardware.

Microsoft Technet has a # of articles on how to migrate an existing SBS installation to new hardware.

Use ADMT and Exmerge and have users save everything to PST files then after the move, import via Outlook.

Added: you can migrate from one server to another server if you do NOT use the same netbios name [but you can use the same domain name]. the 2 SBS servers will see each other via netbios and you can use the ADMT and Exmerge to move users over to the new server [but it can take a long weekend to do if you don't get users to save stuff, like their emails, contacts, calenders, and my documents stuff to CDs DVDs Flash Drives]. It is extremely important to the success of the move to have everything backed up.

by jcovington

Thanks for the tip, I found a great walkthrough on Technet for moving from one SBS server to another. Everything went fine except for one thing: the user accounts won't migrate over to the new server!

The exchange mail does (and works fine), but the user accounts themselves continue to live on the old Domain Controller (I have them both as Domain Controllers for the migration - which Tech Net indicated would function fine)

Will ADMT move user accounts between Domain Controllers on the same domain? Is there another way, within AD to move them myself?

by cg it

One question, how did you move mailboxes without having user account created before the move?

Mailboxes are associated with user accounts in Active Directory. you can't have a mailbox without an AD account.

The best way to migrate to new hardware is to move user accounts first with ADMT and not use ADMT for moving mailboxes. Then use Exmerge to move mailboxes. Have users save everything to PST on a flash drive or CD. The restore PST via outlook.

You could try the swing migration method. It's foolproof. just google SBS swing migration and get the tool kit. Believe it's about $195.00 USD

by jcovington

I will look into Swing Move immediately - $195 is certainly worth my sanity!

Well, I think the mailboxes worked because the new Domain Controller and the old Domain Controller are online together and in the same domain(which according to Tech Net can be done for 7 days), so the mail accounts were still associated with user accounts, just on different servers.

I had backed-up the mail-files to pst, as you recommended, in case it didn't work (and will do so again)

by cg it

at least one part of swing, which allows both to exist and work together.

Swing migration is a real painless, easy way to go to new hardware. Done a bunch of them, as well as using ADMT and Exmerge.

This discussion is closed to new replies.