We have just moved Exchange 2010 to upgraded hardware however Outlook Anywhere connections are still dependent on the old server for authentication.
We have installed Exchange on the new server and moved all of the mailboxes into a database on the new server.
I have updated the server name on the database to the new server for RPC and any other instance where the old server name was listed.
I have updated the URLs to the new server for OWA, OAB etc.
FW ports and DNS have been updated to the new server.
Connectors have been duplicated.
Outlook Anywhere is enabled.
Server passes exchange connectivity tests (with both servers online).
However when I shut the old server down internal Outlook clients connect, OWA works, Activesync works but Outlook clients from off-site are repeatedly prompted for password and will not connect. When checking Outlook connectivity the server Outlook is connecting to is listed as the new server name. It seems the new server is proxying some aspect of Outlook Anywhere authentication over to the old server.
I have read a brief post saying that a CAS array would solve this issue however I do not see why an array would be necessary when all I want is one server active.
Is there perhaps a setting in AD which needs manually configured?
Network Monitoring is essential to ensure that computer systems and network devices are running. Use PRTG to monitor LANs, servers, websites, applications and devices, bandwidth, virtual environments, remote systems, IoT, and many more. PRTG is easy to set up & use.
The basic steps you have just learned will be implemented in this video. The basic steps are shown to configure an Exchange DAG in a live working Exchange Server Environment and manage the same (Exchange Server 2010 Software is used in a Windows Ser…
This video shows how to quickly and easily add an email signature for all users on Exchange 2016. The resulting signature is applied on a server level by Exchange Online.
The email signature template has been downloaded from: