Hi @WalterHof,
@WalterHof said in Outlook 2016 and Outlook 2019 error:
The autodiscover of Outlook 2016 worked with Z-Push until recently. Since a few days we observe that the autodiscover of Outlook 2016 writes the same errors in the autodiscover.log as Outlook 2019. Is there any information that Microsoft has changed the autodiscover of Outlook 2016 in the last days with a patch?
There was an Outlook update in September, but Microsoft didn’t detail what has changed: https://support.microsoft.com/en-us/help/4484511/september-1-2020-update-for-outlook-2016-kb4484511.
How can I make the autodiscover of Outlook 2016 and 2019 compatible with Z-Push?
First some information on autodiscover and what is implemented in Z-Push. First of all Z-Push only implements POX (plain old xml) autodiscover because it’s what the mobile devices use.
In the autodiscover request there’s AcceptableResponseSchema tag. For ActiveSync accounts its value is “http://schemas.microsoft.com/exchange/autodiscover/mobilesync/responseschema/2006”. For an exchange account its value is “https://schemas.microsoft.com/exchange/autodiscover/outlook/responseschema/2006a”.
Z-Push only processes the request and returns a valid response if the client requests mobilesync schema.
Z-Push doesn’t return a valid response for outlook schema because it’s not an exchange server (see https://docs.microsoft.com/en-us/exchange/client-developer/web-service-reference/pox-autodiscover-response-for-exchange how such a response looks like).
So, if the client (a mobile device or Outlook) doesn’t request mobilesync as AcceptableResponseSchema, Z-Push autodiscover won’t work and the user has to configure the account manually.
Manfred
