Migration Exchange 2010 to Exchange 2013 with CAS Array and DAG

Dear All,
I am starting the migration of Exchange 2010 2 servers (CAS/Mailbox) with DAG no CAS Array to Exchange 2013 with 2 servers CAS array and 2 Mailbox servers with DAG. I read on some blogs that no requirement of CAS array on Exchange 2013. My concern how to
configure NLB on CAS servers for the client to connect.
Please guide and have any deployment guide for this, kindly share.
Thanks

Hi ,
As you said there is no use and meaning of having the cas array in exchange 2013 and also thanks a lot to Microsoft for introducing an single namespace facility in exchange 2013.
My suggestion and Microsoft recommendation should be to go with hardware load balancers for exchange 2013 rather than using the windows NLB and round robin method.
Why we need to go for HLB ?
Disadvantages
of some load balancing methods :
Windows
NLB :-
If you use Windows NLB then it can provide redundancy on server level failure and not on application level.
DNS
round robin :-
In case if we use the windows round robin method for load balancing then it wouldn't provide server level
and application level redundancy during the failures.At the Same time we need to manually adjust the DNS records during the server failure but on the client end dns caches will create the issues.
Configuring NLB for exchange 2013 :
http://msexchangeguru.com/2013/08/14/windowsnlb/
NLB configurations for exchange 2010 and 2013 will be same.
Configuring round robin for exchange 2013 :
http://exchangeserverpro.com/exchange-2013-client-access-server-high-availability/
Advisable method is to have the CAS and MBX roles on the same box if NLB not comes it to play.Because windows failover clustering and NLB cannot be configured on the same box.In exchange 2013 cas role is a stateless server role so there is no need to have
that role on a separate box.
Thanks & Regards S.Nithyanandham

Similar Messages

CAS Array and DAG Site Resiliency (2 Remote Sites via Point to Point Protocol)

Hi, we are planning to deploy Exchange HA and Site Resiliency but i had some troubles understanding some concepts.
Out current configurations settings:
Datacenter A:
1 MB/CAS/HT (MB01)
1 CAS (CAS01)
1 Point to Point link between Datacenter A and Datacenter B (We create a VLAN in the remote datacenter pointing to the Active Directory site where our Exchange server is).
1 Active Directory Site with 2 Domain controllers (with VLAN 192.1.3.x in Datacenter A and VLAN 192.1.20.x in Datacenter B)
Datacenter B:
We want to install a new Exchange CAS Server (CAS02) in VLAN 192.1.20.x, is it posible to create a CAS Array with this configuration considering the replication network for the cluster in the MS Windows Server NLB, so that our Virtual IP of the cluster points
to 192.1.3.x VLAN? What are the network considerations to the replication and MAPI network between VLANs? Does we need some third party NLB or this could be achieved with MWS2008R2?
Same configuration for the DAG, with a new server (MB02) just for the MB role. The idea is to remove the CAS role from MB01 and have 2 Exchange Mailbox servers members of the DAG and 2 Exchange CAS Servers members of the CAS Array, so in case of a disaster
in Datacenter A our clients automatically failover to Datacenter B in this case all of our clients will be pointing to the CAS Array in their Outlook.
Hope you can help me with this, i don't know if this is possible with our actual infraestructure.
Best Regards,
Gerardo

Thanks Ed,
So in that case we will need at least 4 servers in Datacenter A (2 MB members of DAG and 2 CAS/HUB members of the CAS Array) to get a decent HA solution, Am I correct?
What about the other server in Datacenter B for DR, it will be a passive node or just another multirole server. So in case of DR (Let's say our Datacenter A is totally wrecked) I will need to switchover manually with my DB backups and switchover the user
mailbox and outlook clients to point to the DR server? I didn´t get the point of the DR server in Datacenter B, can you explain a little bit more?
I'm totally agree with you about the false positive failovers because our network doesn't meet that requeriments at all.
Hope you can help me to clear my mind.
Best Regards,
Gerardo

Exchange 2010 all mail clients with internal cached and internal non-cached mode users having connection status issues, login prompt -- external is fine either way

Hello,
I'm seeing an issue that started this past Monday with no recent change to our environment.
External Outlook Anywhere users and Mobile users, OWA users are unaffected.
Internal Users are affected when using Outlook of any version, 2010 or 2013.
-Internal Users normally log into their workstation with their ad credentials, domain joined machines. Outlook opens without credentials prompting ideally.
1 . Using Cached Mode:
a. Login Prompts, slowness - Since Monday, users are getting prompted to login. The prompt goes away after logging in at startup. It is also causing high CPU
on the workstations.
b. Free/Busy, Out of Office doesn't work. I can, however complete auto-setup for a new user, so autodiscover is not completely down for internal users.
c. Checking Connection Status shows connecting status on highlighted entry below without ever establishing connection (just goes away).
The outlook icon in the system tray says "Outlook is requesting data from the server":
2. Using Non-cached mode
a. No Login Prompt at startup, business as usual
b. Free/Busy, Out of Office works fine. Autodiscover is fine.
c. Checking Connection Status shows normal except, it has "casarray URL, then status is referral" it seams to flicker this constantly then go away intermittently.
d. Main issue in non-cached mode is, sometimes a user will log into windows, open outlook and it will not open and says "server is unavailable. Retry, work offline, or cancel" I can try re-opening, same message.
Only after logging out of windows, logging back in, I can get back into outlook. This is not every time, or consistent with specific users, but random.
3. Lync Pop up for credentials often, though entering the password.
URLs are correct. Autodiscover, EWS, etc.
Already tried bypassing our loadmaster load balancer with host files on clients. same issue regardless of casarray node.
Not sure what is going on.
Josh

You have a hybrid configuration with Office 365, right? You didn't provide this valuable piece of information.
In Exchange Online PowerShell run this command:
Get-OrganizationConfig | FL PublicFoldersEnabled
If the value is "Remote" then users with Exchange Online mailboxes are looking to on-premises public folders. Be sure that you have legacy pubic folder interoperability properly configured.
http://technet.microsoft.com/en-us/library/dn249373(v=exchg.150).aspx
Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

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 :-)

Planning a migration from Exchange 2010 to Exchange 2013

Hello,
I am planning a migration from Exchange 2010 to Exchange 2013 and I was wondering if there was a good guide on the UM migration. I haven't found one that isn't confusing as heck.

Hello,
Is there any update?
If
you have any feedback on our support, please click here
Cara Chen
TechNet Community Support

Exchange 2010 to Exchange 2013 mail flow?

We are planning to migrate Exchange 2010 to Exchange 2013.
I understand that we need to upgrade the CAS to 2013 for Internet Facing.
What about mail flow. Currently, Internet mail flows to Exchange 2010 (single site). Can I keep it for sometime after introducing 2013 and do the cutover of HUB once all the mailboxes are moved to 2013? Or I have to get the mail flow to 2013 first.
Also, how does HUB 2010 transfer mail or receive mail from 2013? Does it get from the CAS proxy in 2013 or from HUB?
Thanks!!!

Yes, you can. But my preference is to move the mail routing early in the migration, usually even before moving mailboxes, because I believe it reduces the risk of a service interruption.
I believe it goes through the front-end transport on the CAS, since that is the TCP port 25 service.
Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Exchange 2010 to Exchange 2013 Public Folder Problem

Dear Experts,
I am in a face of migrating Exchange 2010 to Exchange 2013. Below are my infrastructure details,
1) Parent Domain in Site A (abc.com)
2) One Child domain in Site A named child1.abc.com and Exchange 2007 is running in Site A child domain
3) One Child domain in Site B named me.abc.com and currently Exchange 2010 is running in Site B.
I have installed Exchange 2013 in Site B in coexistence scenario now Exchange 2013 users in Site B trying to attempt connection with a public folder store in the Site A Exchange 2007 servers instead of Site B Exchange 2010 servers.
Anyone help will be highly appreciated.
Thanks & Regards,
ZB

so you want users to access the PF in site B.
Check the setting of Databases in Exchange 2013 and find out what is default Public Folder setup for those Database. You will basically need to change the default Public Folder in Exchange 2013 from Site A PF to Site B,, the way you have explained the scenario.
run this for Exchanger 2013 DA
Get-mailboxDatabase -Identity Exchange2013DBNAME | fl
Get-MailboxDatabase -Identity e15-db1 | fl *PublicFolder*
Where Technology Meets Talent

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

Exchange 2010 to Exchange 2013 work order

Hi ,
Can anyone help me on below points.
I have installed exchange 2013 , and able to view all mail box form existing server 2010.
And move successfully some mail box from 2010 to 2013.
My question are :
Pls let me know the sequence for below reimaging task……
Move all mailbox from 2010 to 2013
Change connectors (received /Send)
NAT the IP in Router (private to Public)
Change the IP address in service provide site. ( OWA for external users)
Need to create or change MX record in internal DNS as well ?
How to change MX record for external DNS.
Note: 2010 is exchange 2010 & 2013 is exchange 2013.
Regards,
Dilip T

Hi,
Based on my experience, here are the steps of migration from Exchange 2010 to Exchange 2013:
Exchange 2013 Deployment
Digital Certificates Configurations
Configure Exchange-related virtual directories
Configure offline address book (OAB)
Move Internet mail flow from Exchange 2010 to Exchange 2013
Move Client Access from Exchange 2010 to Exchange 2013
Move mailboxes from Exchange 2010 to Exchange 2013
Move public folder data from Exchange 2010 to Exchange 2013
Decommissioning Exchange 2010
Thanks,
Angela Shi
TechNet Community Support

Comparing-the-differences-between-anti-spam-agents-from-exchange-2010-to-exchange-2013

http://social.technet.microsoft.com/wiki/contents/articles/23582.comparing-the-differences-between-antispam-agents-from-exchange-2010-to-exchange-2013.aspx
Sathish

Hello,
This forum is for discussions and questions regarding profiles and Microsoft's recognition system on the MSDN and TechNet sites. It is not for products/technologies.
As it's off-topic here, I am moving the question to the
Where is the forum for... forum.
Karl
When you see answers and helpful posts, please click Vote As Helpful, Propose As Answer, and/or Mark As Answer.
My Blog: Unlock PowerShell
My Book: Windows PowerShell 2.0 Bible
My E-mail: -join ('6F6C646B61726C40686F746D61696C2E636F6D'-split'(?<=\G.{2})'|%{if($_){[char][int]"0x$_"}})

Copy UM settings and prompts from Exchange 2010 to Exchange Online

When I migrated UM from Exchange 2007 to Exchange 2010, there is a script called "MigrateUMCustomPrompts.ps1"
that would copy over all the customized greeting files.
We are now migrating from Exchange 2010 to Exchange Online and will be using Exchange Online UM. Is there a similar script to copy over the files just like
the on-prem?

Sorry, I don't share code examples in most cases because they're generally one-off customer-specific scripts and I'm not in a position to answer lots of follow-up questions about them.
Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Moving from Exchange 2010 to Exchange Online: AD issue

Dear All,
Our company will moving from Exchange 2010 to Exchange Online and we have a on-premise WinSer 2008R2 for AD.
Currently, user have to login to our domain and use the same ID and PW to access their outlook.
1.If we move to Exchange online, do we have to do anything with our on-premise AD server?
2.If user prefer using only one ID and PW for PC to access domain and Exchange online, what should we do?
3.Is there any point or do we still need current on-premise AD server after we moved to Exchange Online?
Thank you so much for your attention and help!
Best regards,
Shiloh

Hi,
There are a lot of corrupted items. You can try raising the baditemlimit to 999 to workaround this issue
Get-PublicFolderMigrationRequest | Set-PublicFolderMigrationRequest -baditemlimit 100
To resumed the PublicFolderMigrationRequest
Get-PublicFolderMigrationRequest | Resume-PublicFolderMigrationRequest
Thanks,
Please remember to mark the replies as answers if they help and unmark them if they provide no help.
Simon Wu
TechNet Community Support

OST corrupt when moving Mailbox from Exchange 2010 to Exchange 2010

Anyone come across this?
Moving a mailbox on Exchange 2010 to Exchange 2013 - the outlook client wont connect, if you remove the OST and allow outlook to recreate it comes good again.
outlook client knows the mailbox has moved as it connects to the new server
Not happening to every mailbox
thak=nks

Hi,
After you move mailbox from Exchange 2010 to Exchange 2013, Outlook should still work.
Is there any error message when these affected users try to connect? If there is, please post here for further analysis.
I saw someone failed to connect to the new Exchange server after they moved mailbox, then they restarted the Microsoft Exchange Information Store service and restarted Outlook, it worked.
If you haven't tried this, you can restart the Microsoft Exchange Information Store service to check the result.
Best regards,
Belinda
Belinda Ma
TechNet Community Support

Some help with migrating exchange 2010 to exchange 2013 + installing another exchange 2010 to be edge-forefront-proxy server

Hi guys (and girls)!
Hear me up. The idea is like this:
A friend of mine has currently Exchange 2010 SP3 in his environment with Forefront Protection installed on it. As we all know Forefront Protection is discontinued in Exchange 2013 environment because Exchange 2013 on-premisses is using integrated tool for
doing that, but a friend of mine would really like to stick with Forefront Protection because it is "much better tool" then integrated stuff in 2013.
Ok, so here's the idea. Exchange 2010 SP3 with Forefront is installed on Phisical machine (so, not virtualized) on 2008 r2 std OS. We decided to move to Exchange 2013 because we wanted to achieve DAG on Exchange 2010 but we realized that is not possible
because 2008 R2 STD OS does not support failover-clustering functionality, but you are able to achieve that on newer OS for example 2012? Ok, so we bought another server, where we are planing to install Vmware Esxi and put two virtual machines on it.
One Will be 2012 r2 STD OS with Exchange 2013 on it, the other Will be 2008 r2 STD with Exchange 2010 Edge role + Forefront on it. We are planing to move Exchange 2010 production server to virtual machine Exchange 2013, and newly virtual machine
with Exchange 2010 edge server will only be "a kind of Proxy server with Forefront functionality". What concers me?
Should we install Exchange 2010 edge transport 1st, or Exchange 2013? I think I have read somewhere after you put Exchange 2013 in production you are "unable" to install any previous Exchange versions is that true?
One more question about what happens after you install another Exchange 2010 with Edge role in production enviroment? Does installation effects a production enviroment, let's say we do just a clean installation of Exchange + ran updates?
Which roles do you need to install on Exchange 2010 to achive Edge role? Do you need to have all the roles install for having Edge server (mailbox, hub,cas?).
bostjanc

Should we install Exchange 2010 edge transport 1st, or Exchange 2013? I think I have read somewhere after you put Exchange 2013 in production you are "unable" to install any previous Exchange versions is that true?
already answered by PS CL above
One more question about what happens after you install another Exchange 2010 with Edge role in production enviroment? Does installation effects a production enviroment, let's say we do just a clean installation of Exchange + ran updates?
No it does not as long you don't make any changes on send/receive connector and do the EdgeSubscription. As soon as you do the Edge subscription there will be send/receive connector created, so pay attention how to setup the Edge Server.
Which roles do you need to install on Exchange 2010 to achive Edge role? Do you need to have all the roles install for having Edge server (mailbox, hub,cas?).
Just install the Edge Transport Server and make sure you install ADLDS services.
as you have mentioned you are doing to install both Mailbox and Edge server on the same VMware - it is a single point of failure.
Where Technology Meets Talent

Exchange Migration 2007 2010 to Exchange 2013

Let me lay it all out. We are running an Exchange 2007 environment with 2-CAS, 2-HT's and 2-MBX's clustered. We started a migration to Exchange 2010 and after starting the migration it was decided that we would instead got to Exchange 2013. In Exchange 2010
we have 3-CAS, 2-HT's and 2-MBX's. We have moved our external connections over to Exchange 2010 and only have test mailboxes on 2010 and that's where we stopped.
We installed Exchange 2013 3-CAS, 2-MBX's. We are testing out 2013 installation. We can access 2013 Web App with the 2013 test accounts. I can access 2013 test mailbox with outlook 2010 by configuring outlook for rpc/https. I am not getting free/busy
form 2007 or 2013 when logged into my 2013 test mailbox. My virtual directories are configured as the following:
Exchange 2007 - mail2007.domain.com\
Exchange 2010 - mail.domain.com\
Exchange 2013 - mail2013.domain.com\

Hello,
Please check internalurl of the Exchange 2007 and 2010 EWS virtual, you can use:
Get-WebservicesVirtualDirectory | select internalurl
If they are not set to their own FQDN, please change it back and restart the IIS services.
Thanks,
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Simon Wu
TechNet Community Support

Migration Exchange 2010 to Exchange 2013 with CAS Array and DAG

Similar Messages

Maybe you are looking for