Solved

Exchange Server 2010 to 2016 and load balancing

Posted on 2016-10-11
2
72 Views
Last Modified: 2016-10-11
Hi all!

I am setting up our Exchange 2016 environment next to the existing 2010 one. I have 3 servers up and running with a couple test mailboxes working properly. Now I am at the point where I would have to put these servers in the load balancing along with the 2010 CAS servers, but here I have a problem.

There is one namespace that points to the load balancing address, mail.ourcompany.com. But the old CAS servers have Windows NLB as a load balancing solution, which is something 2016 doesn't want to play with. For quite a while now, we also have a hardware load balancer running but the 2010 CAS servers never made it to this machine, and so remained on their Windows NLB.

Would it be best to move the 2010 CAS servers to the hardware load balancer first with their namespace, and then add the new 2016 servers to that array? Or would it be possible to leave the CAS servers as they are, and only have the 2016 servers in the hardware load balancer, with the original namespace mail.ourcompany.com, acting as a kind of proxy to these 2010 CAS servers? Would that even work, having all users on 2010..?

Thanks for helping us out!
0
Comment
Question by:SysUA
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
2 Comments
 
LVL 40

Accepted Solution

by:
Adam Brown earned 500 total points
ID: 41838383
Don't mix load balancing for 2016 and 2010. You'll want to keep the 2010 servers set up with NLB, since they'll be kicked off the reservation at some point anyway. Exchange 2016 servers will need to be set up in the Hardware Load Balancer and you'll want to change all of your normal client access DNS records to point to the VIP for the 2016 cluster. Exchange 2016 can handle proxy/redirect to the 2010 servers for client access, so you'll want to make sure all users are going through 2016 servers for client access *first*. Otherwise you'll end up with headaches.
1
 

Author Closing Comment

by:SysUA
ID: 41838427
Ah, so we can have the 2016 servers in the hardware NLB and leave the 2010 CAS servers as they are. Excellent, many thanks!
0

Featured Post

Office 365 Training for IT Pros

Learn how to provision tenants, synchronize on-premise Active Directory, implement Single Sign-On, customize Office deployment, and protect your organization with eDiscovery and DLP policies.  Only from Platform Scholar.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

A list of top three free exchange EDB viewers that helps the user to extract a mailbox from an unmounted .edb file and get a clear preview of all emails & other items with just a single click on mailboxes.
Unified and professional email signatures help maintain a consistent company brand image to the outside world. This article shows how to create an email signature in Exchange Server 2010 using a transport rule and how to overcome native limitations …
In this video we show how to create a Shared Mailbox in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Recipients >> Sha…
A short tutorial showing how to set up an email signature in Outlook on the Web (previously known as OWA). For free email signatures designs, visit https://www.mail-signatures.com/articles/signature-templates/?sts=6651 If you want to manage em…

739 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question