Exchange server 2013 Outlook Anywhere has new feature which can able to connect the outlook internally and from the internet. Exchange server 2013 uses two EXHTTP nodes which get generated xml file automatically. The complete detail on how it works with powershell command and scenario based explained in the enclosed attachment.
Exchange 2013 Outlook Anywhere – RPC Over HTTP
Exchange server 2013 Outlook Anywhere is used to connect the outlook internally and from the internet. Exchange server 2013 uses two EXHTTP nodes which get generated xml file automatically. Please find the below XML generated for the user account.
Output of Outlook AnyWhere in Exchange 2013 CAS Server
[PS] C:\Windows\system32>Get-OutlookAnywhere -Server CASSRV1
RunspaceId : 0a620a85-b852-46de-ab5c-f7396685e7d9 ServerName : CASSRV1 SSLOffloading : True ExternalHostname : webmail.mail.com InternalHostname : webmail.mail.com ExternalClientAuthenticationMethod : Ntlm InternalClientAuthenticationMethod : Ntlm IISAuthenticationMethods : {Ntlm} XropUrl : ExternalClientsRequireSsl : True InternalClientsRequireSsl : False MetabasePath : IIS://CASSRV1.MAIL.COM/W3SVC/1/ROOT/Rpc Path : E:\Program Files\Microsoft\Exchange Server\V15\FrontEnd\HttpProxy\rpc ExtendedProtectionTokenChecking : None ExtendedProtectionFlags : {} ExtendedProtectionSPNList : {} AdminDisplayVersion : Version 15.0 (Build 775.38) Server : CASSRV1 AdminDisplayName : ExchangeVersion : 0.20 (15.0.0.0) Name : Rpc (Default Web Site) DistinguishedName : CN=Rpc (Default Web Site),CN=HTTP,CN=Protocols,CN=CASSRV1,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=Mail,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=AD,DC=MAIL,DC=COM Identity : CASSRV1\Rpc (Default Web Site) Guid : 101e738e-9dc5-48d1-9516-ff6ac7a01859 ObjectCategory : AD.MAIL.COM/Configuration/Schema/ms-Exch-Rpc-Http-Virtual- Directory ObjectClass : {top, msExchVirtualDirectory, msExchRpcHttpVirtualDirectory} WhenChanged : 1/22/2014 10:38:54 AM WhenCreated : 9/18/2013 11:39:02 AM WhenChangedUTC : 1/22/2014 5:08:54 AM WhenCreatedUTC : 9/18/2013 6:09:02 AM New Feature in Exchange 2013 Outlook Anywhere
Inorder to achieve the HTTP connection for internal outlook client and HTTPS connections for the outlook client connection over the internet .Then we need to have follow the below rule.
Separate hostname for the internalhostname and externalhost should be different
The Internalhostname should not be published in the internet ISP DNS
The InternalClientsRequireSsl should be set as false and ExternalClientsRequireSsl should be set as true.
Powershell Command
Get-OutlookAnywhere | Set-OutlookAnywhere -InternalHostname "Outlook.mail.com" -InternalClientsRequireSsl $false -ExternalHostname "webmail.mail.com" -ExternalClientsRequireSsl $true
How it works ….
By default always the first HTTP part taken by the outlook to get the details of the url if it fails it goes to the next HTTP part of XML file. In the XML file under the protocol of EXHTTP you can able to view the SSL is off and internalhostname as Outlook.mail.com for the first part HTTP protocol used to connect the internal outlook client. If it fails then it moves to the next part of HTTP part to get connected for the internal outlook client
In the XML file under the protocol of EXHTTP you can able to view the SSL is off and externalhostname as webmail.mail.com. Since the first name is unable to resolve fqdn over the internet hence it gets connected to second part of the EXHTTP part. Hence it move to SSL connection
In Exchange server 2013 public folder will be get connected by using the below piece of XML file
Note: On performing the above change in co-existence mode of Exchange 2007/2010 with Exchange 2013 there will no impact for the legacy exchange user mailbox. Since it connect using RPC/TCP for MAPI connectivity
XML File - Generated on Email Test Configuration in Outlook