Exchange 2010 to 2013 migration quetions
Have a few questions about doing an Exchange 2010 to 2013 migration. Currently a single server Exchange 2010 deployment at a colo. Looking to set up a sinigle Exchange 2013 in the office as the boss is not happy with speed. Eventually want to just have the single Exchange 2013 machine.
Do I need to do anything different when installing Exchange 2013 in a different AD Site than my existing 2010 server?
If I start moving mailboxes from 2010 to 2013, will ActiveSync continue to work? The new server won't be internet facing at first.
Is there a good migration guide for Public Folders? I swear Every time I do a 2003 to 2010 migration, I think the public folders are replicated and moved....turn off 2003 and public folders disappear for the users. I end up doing a PST export/import.
Do I need to do anything different when installing Exchange 2013 in a different AD Site than my existing 2010 server?
If I start moving mailboxes from 2010 to 2013, will ActiveSync continue to work? The new server won't be internet facing at first.
Is there a good migration guide for Public Folders? I swear Every time I do a 2003 to 2010 migration, I think the public folders are replicated and moved....turn off 2003 and public folders disappear for the users. I end up doing a PST export/import.
Do more with
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Yes you can install Exchange 2013 in another site and can migrate users on it. but it should be internet facing if you have exchange 2010 internet facing. As when you will open Exchange 2013 users in OWA/OA/AS you won;t be able to open. Even while migration you will have to have both setup internet facing with silent re-direction. You can provide new OWA URL to all users.
If you are installing Exchange on single machine so please consider capacity planning article by Microsoft, you will have all information about mailbox size calculation, client access and bandwidth calculation etc.
For Public folder migration please follow this guide from MS, it will give you some scripts to download and having procedure to perform export and import public folder database. It is sought of Serial migration
If you are installing Exchange on single machine so please consider capacity planning article by Microsoft, you will have all information about mailbox size calculation, client access and bandwidth calculation etc.
For Public folder migration please follow this guide from MS, it will give you some scripts to download and having procedure to perform export and import public folder database. It is sought of Serial migration
I'm putting my checklist together, want to keep the impact on the users to a minimum. This is what I have so far....
Exchange 2010 server A in subnet A
Exchange 2010 server B in subnet B (had issues with 2013 so went with 2010)
All active users are still on Exchange A
Few inactive users on Exchange B
Assume I can enable Outlook Anywhere on the new server with the new name once I get a legit certificate installed. I only have a single name cert on my existing server.
When someone has their mailbox moved and ActiveSync checks in, there is a silent redirect from https://servera to https://serverb?
Exchange 2010 server A in subnet A
Exchange 2010 server B in subnet B (had issues with 2013 so went with 2010)
All active users are still on Exchange A
Few inactive users on Exchange B
Assume I can enable Outlook Anywhere on the new server with the new name once I get a legit certificate installed. I only have a single name cert on my existing server.
When someone has their mailbox moved and ActiveSync checks in, there is a silent redirect from https://servera to https://serverb?
If you have same version of Exchange on both sites then you can use CAS Proxy, in this case you will have to publish only one site on internet.
Publish Internet URLs on new site and configure proxy on old site. Follow the guide for understanding of CAS Redirection and Proxy.
It will have minimum downtime and you will not have to buy another certificate with new name. You can use existing name.
Publish Internet URLs on new site and configure proxy on old site. Follow the guide for understanding of CAS Redirection and Proxy.
It will have minimum downtime and you will not have to buy another certificate with new name. You can use existing name.
I hope Amit clarifies you concern to get this job done. Moreover, If you wish you may also have a look on below given informative resources which might me helps you.
To complete a migration from Exchange 2010 to Exchange 2013, you need to introduce Exchange 2013 into your existing Exchange environment, then migrate your content: http://www.petenetlive.com/KB/Article/0000788.htm
Migrating from Exchange Server 2010 to Exchange Server 2013
After moving all mailboxes from Exchange Server 2010 to 2013 we can turn our attention to the public folder migration: http://exchangeserverpro.com/exchange-server-2010-2013-migration-moving-public-folders/
Migrating Public Folders to Exchange 2013
Hope it helps you!
To complete a migration from Exchange 2010 to Exchange 2013, you need to introduce Exchange 2013 into your existing Exchange environment, then migrate your content: http://www.petenetlive.com/KB/Article/0000788.htm
Migrating from Exchange Server 2010 to Exchange Server 2013
After moving all mailboxes from Exchange Server 2010 to 2013 we can turn our attention to the public folder migration: http://exchangeserverpro.com/exchange-server-2010-2013-migration-moving-public-folders/
Migrating Public Folders to Exchange 2013
Hope it helps you!
Premium Content
You need an Expert Office subscription to comment.Start Free Trial