Exchange CAS & NLB - license

Hi,

We would like to leverage on NLB and preconfigure the CAS for DR purpose at DR site

Once setup the Windows NLB, will use
get-outlookanywhere -server $server |select internalhostname (set internal hostname to tcluster’s FQDN)

After that, we will shutdown the the Exchange server @ DR site.

Using this DR method, do we require additional exchange license.
Keng0499Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Simon Butler (Sembee)ConsultantCommented:
No one on this site can give you an answer on licencing questions - only Microsoft can.
Therefore you need to call Microsoft, ask them and get the answer in writing.

However, the Exchange product team does not recommend WNLB for use with Exchange, mainly because it sucks quite badly.

Furthermore, Exchange expects all servers to be active, and if you shutdown the remote server then it will complain. I presume that you have the mailbox role already in your DR site? If so, just add the CAS role to that server. In the event of a site failure, change the DNS records.
If you have a short TTL time on the DNS records then the change will be effective very quickly.

Simon.
0
Keng0499Author Commented:
Thank. Yes - we have all in-one installation @ DR site. If we use DNS, understood that the Exchange management console can not run.
0
Simon Butler (Sembee)ConsultantCommented:
Not in my experience.
The console will connect to the local machine.

Which version of Exchange are you talking about? If Exchange 2013, then https://localhost/ecp should work.

However in the designs that I do, I always have site specific URLs, as well as the generic URL. Then the problem doesn't occur anyway.

Simon.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

Keng0499Author Commented:
Yes. It is Exchange 2013. Understood that DNS method for DR purpose only have issue with Exchange 2013 and not prior version.

Our understanding was that using DNS method - the management console and Mobile device will have problem (we dont have mobile in our case).

Will check out.
0
Keng0499Author Commented:
Thanks for helping
0
Simon Butler (Sembee)ConsultantCommented:
I have never seen a problem with management console connection using the DNS methods. You can eliminate any chance of a problem by having a unique site URL for each server then having a general URL.
WNLB isn't really going to help anyway, as it doesn't work well over cross site.

Simon.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.