Changing this setting results in end-users getting pop-ups in Outlook stating that an Exchange Administration has changed settings and that Outlook must be closed in re-opened. Set-MailboxDatabase –Identity “” –RPCClientAccessServer “” So we fixed this name issue with below cmd. RPC Client Access Arra/Server and the internal Outlook Anywhere names were the same, that caused a routing loop once we switched over the default namespace to Exchange 2016. Get-MailboxDatabase | Select Name, RPCClientAccessServer.Checked RpcClientAccessServer is set on the Exchange 2010 Mailbox Databases.Checked the name from the CAS Array on your Exchange 2010 with following Cmd:. ![]() ![]() Get-OutlookAnywhere -Identity “exch2016-01\Rpc (Default Web site)” | select InternalHostname.Checked the name from the internal access point for Outlook.We have checked outlook anywhere configuration which seems to be fine.But OWA and Active sync was working fine. Configured the Exchange 2016 Virtual directories, We were testing the Outlook anywhere and found that the internal Exchange 2010 users are unable to connect to Exchange while new created Exchange 2016 users could connect fine with there Outlook clients. We installed Exchange 2016 for Co-Existence with Exchange 2010. I have a user who is losing connectivity from their Outlook 2010 client (Windows 7 PC) to the Exchange 2007 server (Server 2008) every couple of days.
0 Comments
Leave a Reply. |