Exchange 2013 - OutlookAnywhere InternalHostname Change without Disruption

EXCH01 - All Roles
EXCH02 - All Roles
Three databases setup in DAG.

The problem is when the engineer setup these Exchange servers, he left the FQDN as the Internal Host and OutlookAnywhere address on each server. So if a server goes down, Outlook stops working for many people. I am looking to update all the Virtual Directories and OutlookAnywhere to use Normally I would have set this up from the beginning and wouldn't have to worry about it. I don't like making changes without knowing the impact. Right now if you look at the Exchange Proxy Settings in Outlook, everyone is either pointing to or

For one, do I need to update the Virtual Directories to use or can I just update OutlookAnywhere? Once I make these changes on the Exchange server, will it have any impact on the end users, or will Outlook automatically update with the next time they connect? The SSL certificate already has listed, but it is currently only being used for OWA via a firewall NAT policy. No External URLs have been setup as I believe they only want people using Outlook internally or through VPN.
Keith PratolaSenior Systems ArchitectAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

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.

Will SzymkowskiSenior Solution ArchitectCommented:
If you update your FQDN virtual directory internally you will also be required to ensure that Split DNS is also setup.

As for the clients there is a possibility that they will be disconnected. If everything is stable if the server do not go down, make this change after hours so you are not disrupting the business.

I have also create a HowTo for configuring the VD's and Split DNS


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
Keith PratolaSenior Systems ArchitectAuthor Commented:
Thanks. I am aware of the Split DNS. We have been pending approval to make that change for the past month. The client is very slow. OWA doesn't work internally because everyone is trying to use which isn't available yet inside the network. That is what started me taking a look and noticing that DAG won't even work properly because of the FQDN.
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

From novice to tech pro — start learning today.