Still celebrating National IT Professionals Day with 3 months of free Premium Membership. Use Code ITDAY17

x
?
Solved

Exchange Server 2010 to 2016 and load balancing

Posted on 2016-10-11
2
Medium Priority
?
99 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 42

Accepted Solution

by:
Adam Brown earned 2000 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

Free Tool: ZipGrep

ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.

One of a set of tools we're offering as a way to say thank you for being a part of the community.

Question has a verified solution.

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

In-place Upgrading Dirsync to Azure AD Connect
There are times when we need to generate a report on the inbox rules, where users have set up forwarding externally in their mailbox. In this article, I will be sharing a script I wrote to generate the report in CSV format.
In this video we show how to create an Accepted Domain 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 Mail Flow >> Ac…
The video tutorial explains the basics of the Exchange server Database Availability groups. The components of this video include: 1. Automatic Failover 2. Failover Clustering 3. Active Manager

722 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