Upgrading a hosted Exchange 2007 to Exchange 2013

We have a hosted Exchange 2007 environment that is hosting Exchange for several clients.  We used this guide to setup the environment so that each client is isolated with their own mailbox database, GAL, OAB, etc.:  http://www.msexchange.org/articles-tutorials/exchange-server-2007/migration-deployment/shared-hosting-exchange-2007-part1.html

We are looking to upgrade from Exchange 2007 to Exchange 2013.  Is there anything that we need to do differently from a standard upgrade seeing as our environment is setup this way?  I just want to make sure that when we upgrade it isn't going to revert any of the permissions we have set on the GALs, OABs, etc.

Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

AmitIT ArchitectCommented:
Follow standard upgrade process. Use tool like Exchange deployment assistant. I personally prefer to test upgrade in Test environment with prod users, mostly  IT team members and let them test for few days and document the result. Finally role out in Prod. I suggest, never roll out any test server in Prod, one the biggest mistake made by admins and later they struggle to remove it. Remember, First Exchange server need to be Prod server and should not be removed.

Also, remember client end requirement. You need to plan client end upgrades also related to Outlook or Office in Advance. Finally, Certificates, that plays major role in Exchange. Well plan your cert requirement will save you lot of issues with quick deployment.
sdc_expertAuthor Commented:
Right, this will be performed in a test environment beforehand.  I just wanted to make sure before I started messing around with it that there wasn't anything I should know before starting and wasting time.  Thanks for the input.
AmitIT ArchitectCommented:
There are two things you needed:

1) Product Expertise
2) Environment Expertise.

If you know both above, then you won't face much issues. Environment knowledge is key, as you know better than anyone else. what will best works for your users. Exchange can be deployed in several ways, however end of the day, cost/user experience is key.
Austin RobCommented:
Use this checklist to upgrade from Microsoft Exchange Server 2007 to Exchange Server 2013

Upgrade from Exchange 2007 to Exchange 2013

Steps for Exchange 2007 to 2013 migration:

-Firstly install new server with Windows Server 2012 and Exchange Server 2013
-then move all users to new server
-after that migrate public folders to new public folder mailboxes
-and at last after successful migration uninstall Exchange 2007

Your hosted Exchange email prep guide: http://searchexchange.techtarget.com/guides/Guide-Prepping-for-a-move-to-hosted-Exchange-email

Hope it helps you!

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
sdc_expertAuthor Commented:
Thanks for the assistance guys.  I really just wanted to make sure there wasn't anything I was overlooking before I began testing this upgrade.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.