asked on EXCHANGE and WNLB
Hi Experts,
I am in the phase of upgrading from EXCH2007 to EXCH2013.
Now in EXCH2007 we use a windows NLB with the HUBCAS servers.
Now in EXCH2013 this is not supported anymore.
My new EXCH2013 consists of 3 multi role servers.
I am also preparing a coexistense for my migration.
Can you show me the way to change over without the NLB ?
What kind of steps are important ?
I am in the phase of upgrading from EXCH2007 to EXCH2013.
Now in EXCH2007 we use a windows NLB with the HUBCAS servers.
Now in EXCH2013 this is not supported anymore.
My new EXCH2013 consists of 3 multi role servers.
I am also preparing a coexistense for my migration.
Can you show me the way to change over without the NLB ?
What kind of steps are important ?
ExchangeWindows Server 2008Windows Server 2012
Last Comment
Peter Hutchison
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
ok thanks so far. I will use the new DNS record LATENCY for the old NLB setup.
ASKER
the users of my old EXCH2007 cluster have the clustername as accesspoint -> CLexch2007
But the new DAG has another name -> NAME-DAG
What happens when we do the migration, what happens with all the clients?
Does Autodiscover knows the Client Access name ?
But the new DAG has another name -> NAME-DAG
What happens when we do the migration, what happens with all the clients?
Does Autodiscover knows the Client Access name ?
SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
as you said, it is not supported anymore.
You could change Outlook Anywhere internal namespace to be the same, on all 3 machines, and in that case clients would user DNS round robin to connect to it. It takes around 20sec for clients to go from one server to another, in case of failure.
If not that, then you would need load balancer.
For first solution, here is a use full link: http://exchangeserverpro.com/exchange-2013-client-access-server-high-availability/
Regards,
Ivan.