Manual SBS 2003 to SBS 2008 Exchange Transition (Migration?)

25 pts.
Microsoft Exchange 2003
Microsoft Exchange 2007
SBS 2003
SBS 2008

We are running a small (10 user) SBS 2003 network.  We recently installed a new SBS 2008 server and decided (by recommendation) not to use the migration tool.  The new server is on the same IP address subnet, but has a different local domain name.

All the server installation tasks are complete and a test client has been set up and verified that exchange is working on the new server (receiving and sending mail).  The final tasks are to move public folders and mailboxes from the SBS 2003 to SBS 2008 machine and move the clients to the new server.

Can you please advise in a basic step-by-step process how best to achieve the above?  (hopefully this won't be re-install using the migration tool :-) )

Many thanks in advance


Answer Wiki

Thanks. We'll let you know when a new response is added.

Sorry Denis, you missed the step-by-step process by not using the migration white paper procedures. There is no basic after the fact easy step-by-step process. What about the company website? User data? Fax? Printers? How do your two SBS servers like fighting over DHCP?
When you say, move the clients to the new server, are you referring to the users or computers or both? Were you expecting to use the SBS2008 connect computer wizard? If so, have you tried that on a workstation that was previously a member of the SBS 2003 domain?
IMHO, You were given very bad advice.

Discuss This Question: 4  Replies

There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.
  • Sbsconfused
    Thanks for the feedback. Although I have both SBS on the same subnet, they are separated by a VLAN (achieved through the firewall/router) so no DHCP issues yet (although as our network is very small we use static IPs for the client machines). I have taken one XP client machine from the 2003 domain and moved it to the 2008 domain without any issues. we don't use companyweb or fax. I have tested the printers on the new server (by temporarily disconnecting the sbs 2003). User data and third party software can be transferred manually. If re-installation is the only option then I suppose I'll have to steel myself, but it's a real pity as moving to the 64-bit 2008 configuration did present some issues that we've been able to solve so far (although I have notes of how we solved them first time around). There are tools such as Exmerge - will these work? (I have no experience with this admin tool)
    25 pointsBadges:
  • Dwiebesick
    Denis, they what I would do is look at some articles on migrating from Exchange 2003 to 2008. There are numerous ones including white papers. Is Exchange migration your only show stopper at this time?
    2,235 pointsBadges:
  • Sbsconfused
    Okay, I seriously considered the re-installation route but rejected it as I was too far down the line. Exchange migration is the only outstanding problem. I rejected the transition solution as these involve AD tinkering using dcpromo and I really cannot afford the operational sbs 2003 server to fail. So for any other unfortunates who find themselves in the same position, the solution was as follows: 1. install exchange 2003 management tools, adminpak.msi and exmerge on two xp clients (one on each sbs network). 2. transfer user's mailboxes (this works very well) 3. using one client mailbox, elevate user's permissions for all public folders (had to install PFDAVAdmin on the 2008-network client as I don't like cmdlets). 4. copy public folders to client mailbox 5. exmerge utility export (used a batch file to cope with non-standard folder names) 6. exmerge utility import 7. and finally move the information in to the new public folders. Hardly the most elegant fix, but it did work! Although I haven't tested the MS migration tool, surely it's simpler than that? Thanks for the help. Denis
    25 pointsBadges:
  • Willybst
    Maybe not very bad advice but possibly bad advice, although for 10 users doing it your way is a good alternative (I had 26). The migration wizard can have issues if it runs into problems, which is why you need to prepare ahead. Your problem was that you had to ask after you started what you had to do, where you should have known that ahead of time. But you got there in the end which is really what it's about, so congratulations. I had to migrate from a win2k AD/Exchange server to SBS2008. I was able to do a restore of our server into a virtual machine (VirtualPC; wouldn't work in HyperV). From there I was able to upgrade to SBS2003 (using downgrade rights). When I had that running right, I attempted migrations to the new server using the wizard (on a separate network). It was a nice challenge fixing everything but once fixed, it worked, and then the real migration went well too. I pondered doing what you did too since migrating from win2k wasn't supported but I had to keep disruptions to a minimum and using the migration wizard, I don't think anyone even noticed (except for when ForeFront started chewing up attachments; can I get a "I hate ForeFront"?). I realize I probably had a certain amount of luck in the process, though backed by preparation and testing and knowing my limitations. I guess what I'm trying to say is that I wouldn't advise other people to kinda improvise like you did, even if they have your skills. There is a lot of information and help out there: SBS2008 Unleashed book, newsgroup, website, etc. Hope that helps someone. Regards, Wilco.
    155 pointsBadges:

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

Thanks! We'll email you when relevant content is added and updated.


Share this item with your network: