in a exchange co-existence scenario we are currently struggling with values the internal autodiscover provides to the clients. The internal url for OWA,AS,etc. configured to the services with mail.internal.net, the XML show this for the most parameters.
The parameter PublicFolderServer show mail.outside.com and we found no setting to configure this?
Further background, mail.outside.com as new namespace for the Exchange2013 platform. Public folders are still on the legacy Exchange 2007, the old namespace is legacy.outside.com. The current value mal.outside.com lead clients to certificate errors :-(
There is a problem with the proxy server's security certificate. The name on the security certificate is invalid or does not match the name of the site 'mail.outside.com'. Outlook is unable to connect to this server.
<Protocol> <Type>EXCH</Type> <Server>firstname.lastname@example.org</Server> <ServerDN>/o=CORP/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Serversemail@example.com</ServerDN> <ServerVersion>73C08414</ServerVersion> <MdbDN>/o=CORP/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Serversfirstname.lastname@example.org/cn=Microsoft Private MDB</MdbDN> <PublicFolderServer>mail.outside.com</PublicFolderServer> <AD>corpdc12.internal.net</AD> <ASUrl>https://mail.internal.net/ews/exchange.asmx</ASUrl> <EwsUrl>https://mail.internal.net/ews/exchange.asmx</EwsUrl> <EmwsUrl>https://mail.internal.net/ews/exchange.asmx</EmwsUrl>
Were this PublicServerSetting comes from and how can we modify it to meet clients requirements?
thanks a lot
- Edited by Max Kaiser Thursday, August 13, 2015 2:58 PM