Move Exchange 2003 mailboxes to Exchange 2007

Your only option if the server isn't operational is a 3rd party tool that will extract the EDB file to PST's, I use Kernel EDB: http://www.kerneldatarecovery.com/buy-edb-email-recovery.html

Another option, if the clients were using cached Exchange mode, and you have not removed them from the old domain, is to go to each client's machine, open Outlook and export the Outlook User data to a .pst file. You can then copy to the new profile and import using Outlook.

I guess it depends on how many clients your talking about if that's a viable option r not?

It's a manual process whereas the 3rd party tool will do them all at the same time centrally.

Personal preference I guess?

Hi,
Since Email is imp, use Swing Migration to setup new server, it would take couple of hours and you will be set. Refer: http://www.amset.info/exchange/migration.asp
Once that server is up and running, move them to Exchange 2007. Pretty simple.
Cheers
Nitin

demazter I would have to agree the 3rd party tool is the better and more efficient option, just if there are not that many users, the export method is free. How do you like Kernel EDB, I am not familiar with that one and the price is much better than others at which I have looked.

gupnit, no original server available from which to do a swing migration.

See, Ex: Refer to this link http://technet.microsoft.com/en-us/library/aa997176(EXCHG.65).aspx start from point No 3.....!!!

Kernel is very good, I looked at other products for my "toolkit" but they were all stupid prices.  I also have Kernel OST

gupnit that link still requires the original server.

demazter, thanks I'll look into that. It would be handy to have.
Cheers!
--Rob

Thanks for all the replies.  The new server was installed on Tuesday and workstations and users have been added to the domain.  We are working on getting our customer's business software on-line first and then will address the Exchange issue.  The customer set the priority on which application to startup on the new server.  We should be able to get to Exchange today.

Thanks again for you the replies.  

If they have already been joined to the new domain then the chances are you have lost your OST files or at least lost  access to them so the Kernel EDB is your best bet.

Some more detail on the customer's Exchange:

There are 12 employees in the company.  Although we have not looked at every computer, each person we have checked has a PST file on their computer.  One user expressed more concern about lost contacts/addresses than lost messages.

Any options or suggestions on working with the local PST file?  I think this is in line with the comment from RobWill.  More detail would be appreciated.

Thanks again.

More details:

The customer uses two outside companies for domain and website.  Messages appear to be received by HostA, forwarded to HostB where they can be accessed using a web client.  The customers old Exchange used the POP3 connector to download messages into Exchange.  Exchange in SBS2008 does not appear to support the POP connector.  I think we can move messages from HostA to the local Exchange server but I'm not sure of the setup that will be required on the local server.

What information do I need to have to get mail delivered directly to Exhcange?   As I stated in my initial post, the setup of this new server was scheduled for a later time but hardware failures changed the timing and nature of the new install.  As we try to get applications back on-line, we are finding issues such as the POP that could have been addressed if we had the time to prepare.  

Thanks for any information and suggestions.

Our customer has decided to go with the direct feed to SBS.  I will contact HostA who manages the external DNS to get the MX records changed.  

This is our first Exchange2007 installation.  I have found documentation on using the setup wizard in TechNet but the documentation does not indicate how to start the wizard from SBS2008.  (The document is based on using a setup disk.)  My study prior to this week had focused on using the SBS2003 to SBS2008 migration documentation.  All that changed when the server died.  Any suggestion on accessing the Exchange2007 wizard?

The direction in this series of messages has changed from my initial question due to a change in priority by our customer and the additional facts we did not know about the customer's site.  As mentioned earlier, they do have e-mail access thru HostB's web client so we have the time to configure Exchange without losing complete e-mail service.

Thanks for your replies.  The replies have helped relieve some concerns about this project.

Is there anything else we can help you with?

Can or how do I start the setup wizard?  I know this is a basic question but I'd rather ask the question and be sure.  I think we are heading in the right direction with getting Exchange back on-line but we are a little hesitant to jump into the setup without confirmation, especially since we have not had this situation before.  Our preparation for this project was to use the migration paths between the servers but that could not happen.

Thanks.

There are to do tasks in the Windows SBS console, but as mentioned earlier all the wizards are located by opening the Windows SBS console and going to network | connectivity. Some are on the left and some on the right.

We have not forgotten about this question.  We had more hardware issues that had to be resolved before returning to the Exchange and Outlook issue.  We plan to get back to this issue this week.  The customer is able to use the web-based access as a short term solution.

Thanks for all the replies and suggestions.  The customer's server and e-mail is operational.  Recovering messages from EDB is requested and can now be addressed since the priority of getting the server back on-line is complete.  A third party solution is being discussed.