Autodiscovery for Public Folder in co-existence not match (Network Steve Forum)

Autodiscovery for Public Folder in co-existence not match

Hi together,

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>01234567890@outside.com</Server>
        <ServerDN>/o=CORP/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=01234567890@outside.com</ServerDN>
        <ServerVersion>73C08414</ServerVersion>
        <MdbDN>/o=CORP/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=01234567890@outside.com/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

Max Kaiser

Edited by Max Kaiser Thursday, August 13, 2015 2:58 PM

August 13th, 2015 2:54pm

Hi Jim, Hi together,

OK, there is a part changed in migration to 2013. The path "migrate all user, afterwards the public folder" not meet 100% anymore. With CU5 there is a change in "Legacy Public Folder endpoint discovery", so without doing some preparations migrated users cannot access to legacy public folder,... this is reflected in the shown autodiscovery XML. More at TechNet "Configure legacy public folders where user mailboxes are on Exchange 2013 servers". Hope this helps others in the same situation.

Thanks a lot

Max

Marked as answer by Max Kaiser 20 hours 26 minutes ago
Edited by Max Kaiser 20 hours 25 minutes ago

Free Windows Admin Tool Kit Click here and download it now

August 14th, 2015 7:03am

Hi Jim, Hi together,

Thanks a lot

Max

Marked as answer by Max Kaiser Friday, August 14, 2015 11:02 AM
Edited by Max Kaiser Friday, August 14, 2015 11:03 AM

August 14th, 2015 11:02am

This topic is archived. No further replies will be accepted.