Exchange 2010 to Exchange 2013 Migration and Architect a resilient and high availability exchange setup

Hi,
I currently have a single Exchange 2010 Server that has all the roles supporting about 500 users. I plan to upgrade to 2013 and move to a four server HA Exchange setup (a CAS array with 2 Server as CAS servers and one DAG with 2 mailbox Servers). My
goal is to plan out the transition in steps with no downtime. Email is most critical with my company.
Exchange 2010 is running SP3 on a Windows Server 2010 and a Separate Server as archive. In the new setup, rather than having a separate server for archiving, I am just going to put that on a separate partition.
Here is what I have planned so far.
1. Build out four Servers. 2 CAS and 2 Mailbox Servers. Mailbox Servers have 4 partitions each. One for OS. Second for DB. Third for Logs and Fourth for Archives.
2. Prepare AD for exchange 2013.
3. Install Exchange roles. CAS on two servers and mailbox on 2 servers. Add a DAG. Someone had suggested to me to use an odd number so 3 or 5. Is that a requirement?
4. I am using a third party load balancer for CAS array instead of NLB so I will be setting up that.
5. Do post install to ready up the new CAS. While doing this, can i use the same parameters as assigned on exchange 2010 like can i use the webmail URL for outlook anywhere, OAB etc.
6. Once this is done. I plan to move a few mailboxes as test to the new mailbox servers or DAG.
7. Testing outlook setups on new servers. inbound and outbound email tests.
once this is done, I can migrate over and point all my MX records to the new servers.
Please let me know your thoughts and what am I missing. I like to solidify a flowchart of all steps that I need to do before I start the migration.
thank you for your help in advance

Hi,
okay, you can use 4 virtual servers. But there is no need to deploy dedicated server roles (CAS + MBX). It is better to deploy multi-role Exchange servers, also virtual! You could install 2 multi-role servers and if the company growths, install another multi-role,
and so on. It's much more simpler, better and less expensive.
CAS-Array is only an Active Directory object, nothing more. The load balancer controls the sessions on which CAS the user will terminate. You can read more at
http://blogs.technet.com/b/exchange/archive/2014/03/05/load-balancing-in-exchange-2013.aspx Also there is no session affinity required.
First, build the complete Exchange 2013 architecture. High availability for your data is a DAG and for your CAS you use a load balancer.
On channel 9 there is many stuff from MEC:
http://channel9.msdn.com/search?term=exchange+2013
Migration:
http://geekswithblogs.net/marcde/archive/2013/08/02/migrating-from-microsoft-exchange-2010-to-exchange-2013.aspx
Additional informations:
http://exchangeserverpro.com/upgrading-to-exchange-server-2013/
Hope this helps :-)

Similar Messages

Office 365 to Exchange 2010 Hybrid Mail Box Migration

I'm working on setting up a pilot for Office 365. We have Exchange 2010 SP3, in a DAG configuration (two front end, and 2 mail box servers). I have setup the hybrid configuration. All firewall ports are open.
Problem 1: We can move mail boxes up to office 365 with out a problem. When we try to move them back we get
"[email protected]
Status: Failed
[email protected] Skipped item details
Data migrated: Migration rate: Error: MigrationTransientException: The call to ‎'https://webmail.contoso.com/EWS/mrsproxy.svc City-ExchCAS1.contoso.local ‎(14.3.178.0 caps:05FFFF)‎‎' failed. Error
details: The server was unable to process the request due to an internal error. For more information about the error, either turn on IncludeExceptionDetailInFaults ‎(either from ServiceBehaviorAttribute or from the <serviceDebug> configuration behavior)‎
on the server in order to send the exception information back to the client, or turn on tracing as per the Microsoft .NET Framework 3.0 SDK documentation and inspect the server trace logs.. --> The call to ‎'https://webmail.contoso.com/EWS/mrsproxy.svc
City-ExchCAS1.contoso.local ‎(14.3.178.0 caps:05FFFF)‎‎' failed. Error details: The server was unable to process the request due to an internal error. For more information about the error, either turn on IncludeExceptionDetailInFaults ‎(either from ServiceBehaviorAttribute
or from the <serviceDebug> configuration behavior)‎ on the server in order to send the exception information back to the client, or turn on tracing as per the Microsoft .NET Framework 3.0 SDK documentation and inspect the server trace logs.. --> The
server was unable to process the request due to an internal error. For more information about the error, either turn on IncludeExceptionDetailInFaults ‎(either from ServiceBehaviorAttribute or from the <serviceDebug> configuration behavior)‎ on the server
in order to send the exception information back to the client, or turn on tracing as per the Microsoft .NET Framework 3.0 SDK documentation and inspect the server trace logs."
I know someone is going to say "Trun on IncludeExceptionDetailInFaults", please tell me how to do that. I'm not an exchange expert, or an IIS expert.
Problem 2: We can email to account in Office 365. Office 365 can't email to on-site exchange. We do have Mimecast as a spam filter, and I've been digging in that to see if that is a problem.
Just looking to see if anyone has an idea of thing to check for this.

Fixed
1. Connect to the Office 365 Portal http://portal.microsoftonline.com
2. Click “Admin” in the upper left hand corner and go to “Exchange”
3. Click “migration”
4. Click “+” and then “Migrate from Exchange Online”
5. Click “+”
6. Add the users that you need to move back to Exchange on site at Dedicated Computing
7. Click “next”
8. Click “next”
9. Put any name for “*New migration batch name:”
10. Put <your email domain> for “*Target delivery domain:”
11. Put GUID of target database in for “*Target database:”
Commands for Exchange Management PowerShell to find GUID
i. Get-MailboxDatabase
ii. Get-MailboxDatabase <insert database name from last command> |fl
12. Click “next”
13. Make sure both radio buttons for Automatically are check, and click “new”

Exchange 2013 - can no longer move mailboxes from Exchange 2010 to Ex 2013.

Migrating to Exchange 2013 from Exchange 2010. Created Ex 2013, moved some mailboxes OK. Then could no longer move mailboxes. No errors. The Migration email says complete. Synced: none, Total Mailboxes: none.
Tried several mailboxes. Same result.
Ex 2010 is SP3 RU6, (at least it says RU6 is installed in Programs/Features. The build is for SP3 w/o RU6???)
Ex 2013 is SP1 aka CU4.
How to proceed???
john11

After many attempts to fix the issue (move remaining 4 mailboxes from Exchange 2010 to Exchange 2013) I contacted Microsoft and we resolved the issue. Here's how.
btw - Thanks for the suggestions from Ed. However, they did not seem to move us forward.
What did work:
1. On the Exchange 2010 box, create a new database. (Someone else suggested this also). Then move the remaining Exchange 2010 mailboxes to this new db. Then after that, move the 4 mailboxes to Exchange 2013 using the GUI on Ex 2013. This only worked for one
of the four mailboxes. The other 3 failed.
2. Apparently, we need to restart the Microsoft Exchange Mailbox Replication service on the Exchange 2013 after several failed move attempts to clear cache related to the moves.
3. Then on the Exchange 2013 box, use this Exchange shell command:
New-MoveRequest -identity "[email protected]" -TargetDatabase "Exchange 2013 DB name" -BadItemLimit '500' -verbose
This moved the remaining 3 mailboxes including the Discovery mailbox. It took some time. But we could check the progress using
Get-MoveRequest
The MS Tech was terrific. Really knew his stuff. And all mailboxes are on Exchange 2013. Well, the last one is still moving, but I am optimistic.
Thanks for the suggestions. I had to get this done and the MS Tech made that happen.
john11

Latency leads to full system Failure in Exchange 2010 - Resolved in 2013?

My work encountered a bug - and for no lack of trying - I could not find any bug submission for Ex2010 anymore. Since Most programming relies on the foundation of the past - if replication service was implemented the same in 2013 than it could leave
to a full system failure.
The issue is something happened in REPLICATION service in such a fashion that it accepted a connection, and in the programming it set a variable to a LARGE NUMBER (fail closed) to replace for "Copy Queue
length" in the ball park of 922 quadrillion.
The service never updates this value because of its quasi-state and some timeout occurs and now the GOOD servers think their copy is ludicrously behind. This causes the GOOD servers to attempt to fail-over - as they believe their copy from the BAD
server has failed or perhaps another check fails...
[6 DAG pieces on 3 servers, 4 pieces per server]
In my scenario Server 3 holds:
1 part of server 2 <= Tells server 2 you're bad - don't fail over
1 part of server 1. <= Tells server 1 you're bad - don't fail over
2 parts its own <= "good" - though dead replication service
As I do not know if this exploitable by simply placing a listener in place of replication service to accept and do not respond to connections - I do not know. However, there is a "bug" or flaw in my opinion to allow 1 bad server to superceed
two good servers based on a partial service crash. Simply stopping replication service on Server 3 allowed Server 1 / 2 to take over with out issue - I then restarted replication service and no issue since.
Since i wasted an hour looking where to submit this - this forum will hopefully do - I am very much a white hat - but I am dislike the non-simple way before me to disclose said information to the creator. I want my hour back for their non-intuitive
process, or maybe the simply don't care about Exchange 2010.
- Dan

Please note "LATENCY" in my topic is not network but inter-process on a single host, and is used as saying a timeout occurs without value.

Upgraded to Exchange 2010 now outlook 2013 can't connect externally

Outlook 2013 used to connect to my exchange server via our TMG before upgrading to 2010. At first the clients were changed back to NTLM all the time but I fixed that and we now see basic with SSL. Now we get repeated logon.
I have used rpc connectivity analyser and it tells me that my (self issued) certificate doesn't chain properly - but the signing certificate is loaded on the client (by Enterprise CA policy) and looking at the mail server certificate in the certificate manger
reports the certificate to be good and correctly shows the chain (so is this a problem in the anyalyzer or does outlook constrcut its certificate chain using a different code library than say IE?).
Oddly Windows 8.1's mail cient works flawlessly when outlook 2013 goes into loops?
Any suggestions?
ICHC

Hi ICHC,
Just as Ed said, we should create new rule on TMG during the upgrading.
Found an blog for your reference:
Upgrade from Exchange 2007 to Exchange 2010 - Part II
https://www.simple-talk.com/sysadmin/exchange/upgrade-from-exchange-2007-to-exchange-2010---part-ii/
Disclaimer:
Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software of information found there. Please make sure
that you completely understand the risk before retrieving any suggestions from the above link.
Thanks
Mavis
Mavis Huang
TechNet Community Support

Exchange 2010 to office 365 migration lab

I am looking out for free migration lab if any available online from Microsoft or any vendor related to migrate from exchange 2010 to office 365 . Please suggest ?
Aditya Mediratta

Hi,
Unfortunately, there’s no related lab for use.
We can Microsoft Exchange Server Deployment Assistant to generates a custom step-by-step checklist that will help you deploy different versions of Exchange Server for different types of scenarios. For your reference:
https://technet.microsoft.com/en-us/office/dn756393.aspx
Thanks
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Allen Wang
TechNet Community Support

Unable to send to Exchange 2010 Public Folder after migration

Hi ,
We have migrated exchange 2003 server to 2010 and we migrated all public folders to new exchange 2010 server. But when attempting to send an e-mail to public folder 's e-mail address It says #550 5.2.0 RESOLVER.PF.Invalid; misconfigured public folder mailbox
##. Have you got any idea ? We can see all public folders in outlook client and owa.
Regards.

Hi,
First, please verify if the public folders have replicated successfully, check item counts between replicas. You can use the get-publicfolderstatistics command.
Besides, I recommend you try to mail-disable it and then mail-enable back to check the result.
Best regards,
Belinda
Belinda Ma
TechNet Community Support

Decommissioning Exchange 2010 Casarray (contains 2013 Mailbox Servers?)

I'm in the process of decommissioning exchange 2010. I went to remove the 2010 casarray and see that my 2013 mailbox servers are a part of the array? Can I still remove the array? Do I leave it?

Hi,
Please have a look in to the below mentioned article especially the reply from Off2work
http://social.technet.microsoft.com/Forums/office/en-US/c10550fa-b735-48ee-ad52-a75f0176e1de/cas-array-in-exchange-2013?forum=exchangesvrdeploy
As an additional info , as per my knowledge there is no use of cas array in exchange 2013 and at the same time exchange 2013 servers will not make use of it even though if it is an member of an casarray in exchange 2010.
Please reply me if you have any queries .
Regards
S.Nithyanandham
Thanks S.Nithyanandham

Microsoft Exchange 2010 / Office Pro 2013 - Contact Issues

Good Morning Everyone.
We are running MS Exchange 2010 and have recently upgraded all our clients to MS Office 2013 Pro from Office 2007.
We've had problems with people being able to access previously accessible share folders etc. but we've managed to resolve them. What we are having problems with are peoples personal contacts....
Within Outlook If we click "New Email", then we click "To", choose address book and select "Contacts" (Personal contacts) we receive the error:
"The Address list cannot be displayed. The contacts folder associated with this address list could not be opened; it may have been moved or deleted, or you do not have permissions. For information on how to remove this folder from
the outlook address book, see Microsoft Outlook Help"
The unusual thing is, if we go to the people tabs at the bottom (Mail, Calender, People etc") Then we can access the address book without issue?
Any help would be appreciated, this problem is on every single client...
Regards
Steve Skingle

Hi,
Please make sure the Contact folder is enabled as an email address book in Outlook. We can check this by right-clicking on the personal contact folder, select
Properties, then Outlook Address Book tab.
Check if the “Show this folder as an email Address Book” option is ticked. If not, tick it and restart Outlook to check the result.
Please let me know the result.
Steve Fan
TechNet Community Support

Office 2010 vs. 2013 - migrating from XP to W7

I have a client with >200 PCs, and about 50 already run W7 with Office 2010. The remaining 150+ XP PCs are currently being migrated to W7, and the client wants to stay with Office 2010, as they have already purchased 50 or so licenses for their existing
W7 PCs.
I am finding Office 2010 licenses harder and harder to find, and much more expensive since Office 2013 was released. The client also has plans to add 50+ PCs during Q4 2014 when a new location is opened. I am hesitant to proceed with their direction,
if 2010 licenses become no longer available. I know that MS has discontinued sales, and vendors will only be allowed to continue to sell 2010 until their inventory is depleted. My client is aware of this, but they do not want to standardize on 2013 because
they feel they would then have wasted their money buying the roughly 50 copies of 2010. And they do not want a mishmosh of 2010/2013 in their company, they want to be all on the same version.
Any advice?I do not want to move them away from Office (to openoffice, Corel, or worse!) but if I can't get them standardized on 2010 they may be forced to move to another platform or worse decide to find a new IT consultant. They understand this is not
my fault per se, but they blame me for not anticipating this during the last few years when I recommended Office 2010 for their new W7 PCs. No good deed goes unpunished as they say.

Hi
Since it is hard to purchase Office 2010, you can take Office 2013 and downgrade to Office 2010.
However downgrade rights are only available for volume licenses.
Check the following article:
http://www.microsoft.com/licensing/about-licensing/briefs/downgrade-rights.aspx
Tylor Wang
TechNet Community Support

Lync 2010 to Lync 2013 migration - Dialin conferencing

While migrating from Lync 2010 to Lync 2013, i have stopped all services on the Lync 2010 servers to make sure all is okay and everything is working fine with Lync 2013.
Nevertheless, when someone on Lync 2013 schedule a meeting, and someone dial one of the PSTN Dialin conference number and enter the conference ID, this scenario is not working.
If i start the Lync 2010 front end services, then the previous scenario works.
So i did something else. I have scheduled a meeting and i change the meeting options to get a new conference ID. this makes the conference work over dial in pst number while Lync 2010 services are down.
This means:
- When someone (Lync 2013 user) schedule a meeting, the default conference ID that is generated, requires the existence of Lync 2010 services for a PSTN Dial in user to connect
-When someone (Lync 2013 user) schedule a meeting and change the meeting options to get a new conference ID, then the PSTN Dial in user can connect even if all Lync 2010 services are down.
Any clue?
ammarhasayen

i have found it. moving the conference directories from Lync 2010 to Lync 2013 solves the whole thing.
ammarhasayen

Exchange 2010 onprem to 2013 on prem cross forest LARGEITEMLIME issue

ok i have started migrating some of our users over, however some are failing due to large files.
I know that i can use the -LargeItemLimt switch to have the migration "SKIP" those files. (there seems to be alot of misconception that this will actually COPY the files & the value that you define is the MB limit. this is incorrect,
& this switch just tells the migration that it is ok to skip X (the value you define) amount of messages.)
Ok so now that that is out of the way
how or where would one configure to ALLOW mailboxes to be migrated over that contain large files? Is it in the transport/send/receive connectors size limits? is it else where?
I rather temp allow large files to complete my migrations & copy those files over, rather then skipping those files, & essentially loosing them for ever.

Now here is the thing, "AllowLargeItemLimit" is still mystery (to me at least)
But you can update the size of Send and Receive Connector on 2013 and should work
Set-TransportConfig -MaxSendSize 100MB -MaxReceiveSize 200MB
Get-ReceiveConnector | Set-ReceiveConnector -MaxMessageSize 200MB
Get-SendConnector | Set-SendConnector -MaxMessageSize 200MB
http://www.msexchange.org/articles-tutorials/exchange-server-2013/mobility-client-access/exchange-2013-local-mailbox-moves-part1.html
Cheers,
Gulab Prasad
Technology Consultant
Blog:
http://www.exchangeranger.com    Twitter:
  LinkedIn:
   Check out CodeTwo’s tools for Exchange admins
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

Auto-Mapping with Full Access Mailboxes-not working in exchange 2010 clients outlook 2013

hello, I have exchange server 2010, the clients are running outlook 2013, I set an mailbox for automapping (full access) but when i restart client it does not appear in the client. i also did the command in the exchange shell, no errors. how can i fix this.

no sp info shows with the
Get-ExchangeServer | Format-List Name, Edition, AdminDisplayVersionName
Edition : Enterprise
AdminDisplayVersion : Version 14.0 (Build 639.21)
chart says
Exchange Server 2010 November 9, 200914.00.0639.021
is that the issue need sp 1?

Proper way to install windows update on Exchange 2010 DAG with one mailbox server in Head Office and 1 mailbox server in DR site both are members of 1 DAG

Hi Guyz,
I have this setup in my exchange environment.
1 DAG with 2 members
- One member is located in Head Office and the other member is located in DR site. All of the mailbox databases are located only in HO (Plan to add additional second member in HO soon). Now what is the proper way to install windows patches on the
member in HO? I don't want to move the databases to DR site as much as possible.
Appreciate your feedback and Many thanks in advance guyz..
More power to all!
Regards,

Hi,
To update the DAG members with new patches, the update process should be managed to prevent all of the DAG members from being offline at the same time.
To do this, I recommend you move the active mailbox databases off a particular server so that it can be patched, and if necessary rebooted, without causing any downtime for mailbox users on that database.
For detailed steps, here is an article for your reference.
How to Install Updates on Exchange Server 2010 Database Availability Groups
http://exchangeserverpro.com/how-to-install-updates-on-exchange-server-2010-database-availability-groups/
Note: Microsoft is providing this information as a convenience to you. The site is not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please make
sure that you completely understand the risk before retrieving any suggestions from the above link.
Hope it helps.
Best regards,
Amy Wang
TechNet Community Support

TFS 2010 to TFS 2013 Migration stuck at step 13

Hi,
We've been trying to migrate our TFS 2010 collections to TFS 2013, but we always get stuck at Step 13 of 793. We tried 3x already. For the first try we waited around 8 hours, and decided to just restart. On the second try, we waited for more
than 13 hours and still no joy. And the third try is still going.
We are using Windows Server 2012 R2 for both Application Tier and SQL Server. Windows 2008 R2 for Sharepoint Server. SQL Server 2012 with SP1 Standard for the SQL Server.
Our TFS 2010 is a single server setup (Windows 2008 R2). And we are migrating now to a tiered architecture (a separate machine for sharepoint, another for SQL Server and another for the application tier). Could this be what's causing the 'stuck'?
I've followed the ALM rangers document, followed the requirements (i.e. Windows version, SQL Server version, etc), read articles from forums and I think we've done everything that we need to. Note that we tried migrating to TFS 2012 ages ago and it did
migrate successfully, but we're thinking TFS 2013 is available now so might as well go to TFS 2013. Do we need to migrate to TFS 2012 first? But that's what the documents say, TFS 2010 can be a direct migration to TFS 2013, right?
There are four collections in our TFS 2010, and the other three migrates fine. It's the DefaultCollection that is getting stuck. The default collection is around 170GB in size. When we did the migration to TFS 2012 before, it was 150GB in
size and finished in around 5 hours.
Can anyone let me know or point me to the right direction on how to address this issue? I've looked at the logs and can't see anything that stands out; no errors mentioned. Is there anything else that I could look at? Or is ther any profiling
that I can enable to see what might be causing the issue? I've searched google and only found a couple forums that has the same issue. One was resolved because of the Max Parallelism and we did that one as well but still no joy.
Appreciate any ideas. Thanks heaps.
Kindest regards,

Hi,
Thanks for your post.
What's the result of your third try?
What's the document are you following?
From TFS upgrade requirements, You can upgrade TFS 2013 from Team Foundation Server 2010 directly.
If you’re using SQL Server 2012 with SP1, we recommend you also apply
cumulative update 2 on top of SP1 to address a critical SQL Server bug around resource consumption. This isn’t a hard requirement because the bug only affects a small number of instances, but we wanted you to be aware of it. If you don’t apply CU2, you
should apply a SQL Server hotfix (KB2793634) to addresses another (different) issue where SQL Server 2012 with SP1 might request an excessive amount of restarts.
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Exchange 2010 to Exchange 2013 Migration and Architect a resilient and high availability exchange setup

Similar Messages

Maybe you are looking for