Outlook Clients unable to connect to Exchange 2010 new Client Access Server after Client Access Server Role is Moved.
After installing new Client Access Server on your environment or If you uninstalled the old Client Access Server you will see outlook still trying to reach your old Client Access Server.
Even if you put the new Client Access Server FQDN/IP address in to the server name field, it will automatically resolve the old CAS server FQDN.
Server Description | Server Name | IP Address | Operating System | Application |
Domain Controller | dc.doitfixit.local | 192.168.1.100 | Windows Server 2008 R2 SP1 Standard Edition |
|
Exchange CAS/HUB server (Old Server) |
cas.doitfixit.local | 192.168.1.101 | Windows Server 2008 R2 SP1 Standard Edition |
Exchange Server SP2 |
Exchange CAS/HUB server (New Server) |
cas2.doitfixit.local | 192.168.1.105 | Windows Server 2008 R2 SP1 Standard Edition |
Exchange Server SP2 |
Exchange Mailbox Server | ex1.doitfixit.local | MAPI: 192.168.1.102 Replication: 10.1.10.10 |
Windows Server 2008 R2 SP1 Enterprise Edition |
Exchange Server SP2 |
Exchange Mailbox Server | ex2.doitfixit.local | 192.168.1.103 Replication: 10.1.10.11 |
Windows Server 2008 R2 SP1 Enterprise Edition |
Exchange Server SP2 |
I have installed new Client Access Server named “CAS2” in my Exchange 2010 environment. Let’s check the RPC Client Access Server by Exchange Management Shell.
Get-MailboxDatabase | fl name,*rpc*
As shown on above image after installing new Client Access Server, I have added cas2.doitfixit.local as a server name, but its automatically resolve old server name.
Now I am uninstalling old client access server (cas.doitfixit.local) and again check the RPCClientAccessServer. See now It has no value. (See the below image)
In this moment if you trying to configure outlook with auto configuration you will receive below error.
An unknown error occurred, error code: 0x80070057
In the same time you will receive below error in your new Client Access Server as well.
Log Name: | Application |
Source: | MSExchange Autodiscover |
Event ID: | 1 |
Level: | Error |
Task Category: | Web |
Computer: | <New CAS FQDN> |
General: | Unhandled Exception “User setting ‘PreferredSite’ is not available.” Stack trace |
If the Client Access server role was moved from cas.doitfixit.local to cas2.doitfixit.local, you can assign the mailbox databases with new RPC Client Access service by running below command.
Set-MailboxDatabase -Identity “DB01” -RpcClientAccessServer cas2.doitfixit.local
Again I executing Get-MailboxDatabase | fl name,*rpc* command to view current RPCClientAccessServer. CAS2.doitfixit.local is now associated with DB01 database.
Also we can perform this action for all Mailbox Databases on the server by running below command.
Get-MailboxDatabase -Server ex1.doitfixit.local | Set-MailboxDatabase -RpcClientAccessServer cas2.doitfixit.local
Get-MailboxDatabase -Server ex2.doitfixit.local | Set-MailboxDatabase -RpcClientAccessServer cas2.doitfixit.local
Lets check the RPCClientAccessServer
Now Outlook will connect to new Client Access Server successfully.
To view the connection status hold down the Ctrl key and click outlook icon in tray. And click connection status.
Now you can see outlook is connected to new Client Access Server.
Leave a Reply