So I am about to do an upgrade from Exchange 2007 to Exchange 2010. All the clients are Outlook 2010.

I am hoping it will go okay without too many glitches. I know with this specific upgrade, you can do what's called an "online" migration of the mailboxes to the new server. That being said, what kind of down time should I plan on?

Please share your experience if you have done this upgrade before...thanks.

You really shouldn't have to worry about any. You may see some performance issues depending on how large of mailboxes and any public folders but that should be about it. As long as you have all your pre-checks in order it should go fine.

Here's a great walk through that can help with making sure your system is fully ready to upgrade.

You really shouldn't have to worry about any. You may see some performance issues depending on how large of mailboxes and any public folders but that should be about it. As long as you have all your pre-checks in order it should go fine.

Here's a great walk through that can help with making sure your system is fully ready to upgrade.

Just finished a 07 to 10 migration. It was fairly painless, but we did run into a few issues.

They were mostly due to us migrating from 2000 to 2003 to 2007 in the 10 years I've been here. There were/are some traces left behind by all the old installs.

Watch you log file size during the migration. I'd stagger the migration over a few days if I had to do it again.

The built-in anti-spam in 2010 isn't as good as in 2007 IMHO. Loads of false positives and not catching obvious spam. I just installed Vipre Exchange protection today and so far it is got us back to the spam detection rates I was seeing in our old setup, just not free anymore. ;)

I'm in the final strides of completing our 2007-2010 upgrade. I was pleased with how easy the transfer was. I only had a few issues:

- some older accounts that were needed for documentation but weren't being used and hadn't been logged into since the existence of the 2003 server. These accounts had some corrupt items in them (tasks, calendar entries, etc) that needed to be weeded out by hand before I could continue moving them to the new server.

- outlook 2003 needs sp3 to work with exchange 2010 and even still it's pretty buggy and requires some modifications of RCA settings at the server. I'd strongly suggest moving everyone to outlook2007/2010 as part of the strategy.

- a public folder store has to be created on the destination server and each and every subfolder has to be replicated to the new 2010 server before anybody gets transferred over. Public folders are starting to go the way of the do-do bird!

- we had custom forms (designed by a predecessor twice before me) in the public folders that were used to create contacts in a modified contact list and had existed since ex2003 days and for some reason did not transfer over properly. I'm currently in the process of moving it to sharepoint to get away from it.

- the BES server account need to be transferred to the new server and re-configured at the BES server before moving any BES enabled users.

Just a few of the headaches I tripped over and are VERY specific to our setup - but others may see the same things.

What should be done first: migrating the mailboxes to the new server and then changing the NAT statement on the firewall to point to the new server? Or changing the NAT statement first so the new server is now "online" and then migrating the mailboxes?

What should be done first: migrating the mailboxes to the new server and then changing the NAT statement on the firewall to point to the new server? Or changing the NAT statement first so the new server is now "online" and then migrating the mailboxes?

Either way, both servers will route the mail to the correct server. Personally, we moved to the new server right at the beginning to verify that mail flow was working through the new server to the old where my mailbox still was.

0

This discussion has been inactive for over a year.

You may get a better answer to your question by starting a new discussion.