question

GeorgeFang-8154 avatar image
0 Votes"
GeorgeFang-8154 asked KaelYao-MSFT commented

Outlook does not display free/busy info when booking meetings since we applied KB5000871 on exchange server 2016 on 08-Mar-2021.

After we apply KB5000871 to exchange server 2016 to address 0-day vulnerability of on-premise exchange server 2016, outlook does not display free/busy info any more. Instead, it says no free/busy information could be retrieved. Your server location could not be determined. Contact your administrator. Outlook also displays "We can't show Mailtips right now" message. It sometimes has error 0x00040820 or Errors in background synchronization. In order to apply the new patch on exchange 2016 running windows server 2016, we also had to apply cumulative exchange update 19 (it was on cumulative update 11) and install dot net framework 4.8 in the process. Another thing to note is that we have hybrid Azure online in our domain environment to get access to MS teams. Does anyone have this problem? Did the latest patch break outlook 2013? We just notice that the shared calendars are not working any more. It displays no connection at the top. I would say more things are broken. Thanks, George.

office-exchange-server-administrationoffice-outlook-itprooffice-exchange-hybrid-itpro
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

GeorgeFang-8154 avatar image
1 Vote"
GeorgeFang-8154 answered KaelYao-MSFT commented

This problem is finally resolved myself searching around hard. The issue turns out to be about ewsallowoutlook setting available from set-organizationconfig. In the past, that one is set to nothing or null and it is treated as true by outlook. Now after the update, it is treated as false by outlook. So to resolve the problem, we only need set it explicitly to true. Obviously I do not know through which CU update or the latest security update that this change or bug/feature is introduced. The problem is that end users are not informed about it and with no one helping resolve it, it is really very frustrating for the end users to trouble shoot these problems. BTW, googling around turns up nothing close to this issue. Hopefully my experience here could help others having the same problem.

· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Thanks for the sharing!
Glad to hear the issue finally get resolved.

0 Votes 0 ·
KaelYao-MSFT avatar image
0 Votes"
KaelYao-MSFT answered KaelYao-MSFT converted comment to answer

Hi, George.

Sorry I need to ask a few questions:
1.Does the problem happen to only a few users? Or it affects all users?
2.What is the affected Outlook version? Does the problem only occur on Outlook 2013?
3.Are the affected clients domain-joined or external clients? Are they using pop or imap to connect?

You may test with OWA and check if the free/busy information can be retrieved successfully.
If OWA is working fine, please recreate Outlook profiles and see if the problem persists.


If the response is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

GeorgeFang-8154 avatar image
0 Votes"
GeorgeFang-8154 answered GeorgeFang-8154 edited

Hi Kael,

The problem happens for all users. Outlook 2013 (we do not use others) is affected. Affected clients are domain joined. We only use the default connection protocol. POP or IMAP are disabled. OWA seems to work. But we tried to sign on to brand new workstations with brand new user profiles and outlook profiles and outlook 2013 does not work at all. While the meeting rooms calendar still seem to work, shared calendars do not. Also we cannot send shared calendar to anyone. After clicking send button, we get message "Error while preparing to send sharing message" dialogue box.

76941-image.png
All of these work before applying the new patch.
Thanks,

George.



image.png (4.7 KiB)
· 8
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Hi,George.

Sorry for the late reply.
I suppose OWA is working fine now without problem, while users can't share calendar via Outlook.

I tested in my lab(Outlook 2013 & Outlook 2016 with Exchange 2016 KB5000871)
And at first I run into the same problem when trying to share calendar via Outlook.
While after adding a user(who to share with the calendar) to the delegate access, I was able to share calendar.
Then I removed the delegate access permission and try to share calendar with other users, the problem didn't come back.

Besides, would you first test with sharing calendar via OWA?
If it works fine, please try to share calendar via Outlook to check if it works now.

0 Votes 0 ·

Hi KaelYao,

Sharing calendar works in Owa and it works well with all the features that I tested. In fact, I do not find a problem when using OWA. But in outlook 2013, calendar sharing does not work. Free/busy info is not available. If I add full access permission to mailbox of a user (through mailbox delegation in ecp), then I can access his mailbox, his calendar, free/busy info and all the rest.

Unfortunately after I remove the access, the calendar sharing stopped working again. Surprisingly for no apparent reason, for a user having domain administrator rights, if full rights to mailbox of another user is granted to him and later removed, the administrator user can still access the removed user calendar info and free/busy info. But this is not the case for regular users. Does your test user also have domain administrator rights?

Thanks,

George.

0 Votes 0 ·

Actually later I see that the option for calendar permission level is changed to reviewer for administrators for some unknown reason and that is why administrators can still view free/busy time. Basically if the option for calendar permission level for a user is changed to reviewer, then the free/busy info becomes available to that user. For some reason, the default permission level free/busy time is not enough for free/busy info any more. Regardless there is no way to get the automatic reply to work in outlook 2013.

0 Votes 0 ·

Hi KaelYao,

Our users also discover that the automatic replies button does not work in outlook 2013. If one clicks it, one get the following:

79382-image.png

My guess is that more things are broken by the patch and they are yet to be revealed by our users. BTW, the message displayed on the dialogue is wrong and misleading. I have to say that it is crazy to think they do not know that and need to ask actual end users question "Was this information helpful?". Too many times, they know the issue but they do not want and/or do not plan to resolve it for some reasons that they do not tell. Instead they ask users silly questions what and/or where the problem is.


George.


0 Votes 0 ·
image.png (7.0 KiB)

Hi, George.

Thanks for the update!

I was testing with both domain admin and normal user accounts, both worked fine and I was not able to reproduce the problem.

Since besides Free/Busy and Shared calendar, the automatic reply doesn't work as well.
I suppose the problem may be with the EWS virtual directory on Exchange server, which is responsible for Free/Busy, Shared calendar and OOF(automatic reply).

Please run these commands via EMS to recreate the EWS virtual directory and see if it works for you:

 Get-WebServicesVirtualDirectory -Server <servername> | fl Server, Name, InternalUrl, ExternalUrl
    
 Remove-WebServicesVirtualDirectory -identity "servername\EWS (Default Web Site)"
    
 New-WebServicesVirtualDirectory -Server <servername> -InternalUrl <internalUrl> -ExternalUrl <externalUrl>
0 Votes 0 ·

Hi KaelYao,

Thank you very much for the message. I assume that this needs resetting IIS. As I mentioned before, we also have Microsoft 365 hybrid configuration wizard run in our environment. I had a hard time getting MS Teams calendar synchronized with our regular outlook 2013 calendar so that meetings created in teams calendar show up in outlook 2013 calendar and vice versa. Will recreating this EWS virtual directory affect any of that operation? As far as 365 is concerned, we only use teams online and Azure AD connect on-premise authentication through seamless single sign-on together with pass-through authentication.

Cheers,

George.

0 Votes 0 ·

Hi KaelYao,

I tried recreating EWS virtual directory as you directed. After resetting iis with no improvement, I restarted exchange server. No progress is seen. Then I rerun hybrid configuration wizard (speaking of which, I have to say that wizard does not run on ms server 2016 and it only runs from IE not edge nor chrome, too tricky for end users). It looks major functions are fine still. But known problems related to free/busy info, sharing calendar, automatic replies and others are broken for outlook 2013 with no difference though they still all work using owa.

Thanks,

George.

0 Votes 0 ·
Show more comments
GeorgeFang-8154 avatar image
0 Votes"
GeorgeFang-8154 answered KaelYao-MSFT commented

Hi KaelYao,

I run Test-WebServicesConnectivity -TrustAnySSLCertificate | fl on the exchange server and here are some error results:

Scenario : AutoDiscoverSoapProvider
ScenarioDescription : Autodiscover: SOAP Provider
Result : Failure
Latency : 41
Error : System.Net.WebException: The remote server returned an error: (401) Unauthorized.
at System.Net.HttpWebRequest.GetResponse()
at
Microsoft.Exchange.Management.SystemConfigurationTasks.ServiceValidatorBase.InternalInvoke()
at Microsoft.Exchange.Management.SystemConfigurationTasks.ServiceValidatorBase.Invoke()

ServiceEndpoint :
Scenario : EwsGetFolder
ScenarioDescription : EWS: GetFolder
Result : Skipped
Latency : 0
Error : Skipped testing Exchange Web Services because the Autodiscover step failed.
Verbose :
MonitoringEventId : 5053

If you need other details, please let me know so that I can send you via email or some other channels.

Thanks,

George.

· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Hi,George.

Would you please run Test-WebServicesconnectivity -Identity mailbox@contoso.com -MailboxCredential (Get-Credential) -TrustAnySSLCertificate | fl to test with a existing user mailbox instead of using the test account?
Check if it will return different error messages.

And please also run a Test E-mail Autoconfiguration via an Outlook client.
Check the results under the "Results" and "Log" tags.

0 Votes 0 ·
GeorgeFang-8154 avatar image
0 Votes"
GeorgeFang-8154 answered GeorgeFang-8154 edited

Hi Kael,

The result from

Test-WebServicesconnectivity -Identity mailbox@contoso.com -MailboxCredential (Get-Credential) -TrustAnySSLCertificate | fl

looks exactly the same and here it is:

Scenario : AutoDiscoverSoapProvider
ScenarioDescription : Autodiscover: SOAP Provider
Result : Failure
Latency : 45
Error : System.Net.WebException: The remote server returned an error: (401) Unauthorized.
at System.Net.HttpWebRequest.GetResponse()
at
Microsoft.Exchange.Management.SystemConfigurationTasks.ServiceValidatorBase.InternalInvoke()
at Microsoft.Exchange.Management.SystemConfigurationTasks.ServiceValidatorBase.Invoke()

ServiceEndpoint :
Scenario : EwsGetFolder
ScenarioDescription : EWS: GetFolder
Result : Skipped
Latency : 0
Error : Skipped testing Exchange Web Services because the Autodiscover step failed.
Verbose :
MonitoringEventId : 5053


The xml output from autoconfiguration is included below. The actual server address is replaced by generic one. I have to say that there is no easy way to copy and paste from results or log tab except xml tab. Why they make it so is beyond me, not to mention that the window size is small with no way to resize. Anyway here is the xml result that you guys may have a way to parse it:


<?xml version="1.0" encoding="utf-8"?>
<Autodiscover xmlns="http://schemas.microsoft.com/exchange/autodiscover/responseschema/2006">;
<Response xmlns="http://schemas.microsoft.com/exchange/autodiscover/outlook/responseschema/2006a">;
<User>
<DisplayName>George Fang</DisplayName>
<LegacyDN>/o=ContosoCorp/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=gfang</LegacyDN>
<AutoDiscoverSMTPAddress>gfang@contoso.com</AutoDiscoverSMTPAddress>
<DeploymentId>83af523a-74ca-431e-9c9d-1f6b532f1490</DeploymentId>
</User>
<Account>
<AccountType>email</AccountType>
<Action>settings</Action>
<MicrosoftOnline>False</MicrosoftOnline>
<ConsumerMailbox>False</ConsumerMailbox>
<Protocol>
<Type>EXCH</Type>
<Server>91365a04-0f90-4716-b8b0-86fe805ed032@contoso.com</Server>
<ServerDN>/o=ContosoCorp/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=91365a04-0f90-4716-b8b0-86fe805ed032@contoso.com</ServerDN>
<ServerVersion>73C18880</ServerVersion>
<MdbDN>/o=ContosoCorp/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=91365a04-0f90-4716-b8b0-86fe805ed032@contoso.com/cn=Microsoft Private MDB</MdbDN>
<PublicFolderServer>email.contoso.com</PublicFolderServer>
<AD>Bcontrol.ContosoCorp.local</AD>
<AuthPackage>Anonymous</AuthPackage>
<ASUrl>https://email.contoso.com/EWS/Exchange.asmx</ASUrl>;
<EwsUrl>https://email.contoso.com/EWS/Exchange.asmx</EwsUrl>;
<EmwsUrl>https://email.contoso.com/EWS/Exchange.asmx</EmwsUrl>;
<SharingUrl>https://email.contoso.com/EWS/Exchange.asmx</SharingUrl>;
<EcpUrl>https://email.contoso.com/owa/</EcpUrl>;
<EcpUrl-um>?path=/options/callanswering</EcpUrl-um>
<EcpUrl-aggr>?path=/options/connectedaccounts</EcpUrl-aggr>
<EcpUrl-mt>options/ecp/PersonalSettings/DeliveryReport.aspx?rfr=olk&amp;exsvurl=1&amp;IsOWA=&lt;IsOWA&gt;&amp;MsgID=&lt;MsgID&gt;&amp;Mbx=&lt;Mbx&gt;&amp;realm=contoso.com</EcpUrl-mt>
<EcpUrl-ret>?path=/options/retentionpolicies</EcpUrl-ret>
<EcpUrl-sms>?path=/options/textmessaging</EcpUrl-sms>
<EcpUrl-publish>?path=/options/calendarpublishing/id/&lt;FldID&gt;</EcpUrl-publish>
<EcpUrl-photo>?path=/options/myaccount/action/photo</EcpUrl-photo>
<EcpUrl-tm>options/ecp/?rfr=olk&amp;ftr=TeamMailbox&amp;exsvurl=1&amp;realm=contoso.com</EcpUrl-tm>
<EcpUrl-tmCreating>options/ecp/?rfr=olk&amp;ftr=TeamMailboxCreating&amp;SPUrl=&lt;SPUrl&gt;&amp;Title=&lt;Title&gt;&amp;SPTMAppUrl=&lt;SPTMAppUrl&gt;&amp;exsvurl=1&amp;realm=contoso.com</EcpUrl-tmCreating>
<EcpUrl-tmEditing>options/ecp/?rfr=olk&amp;ftr=TeamMailboxEditing&amp;Id=&lt;Id&gt;&amp;exsvurl=1&amp;realm=contoso.com</EcpUrl-tmEditing>
<EcpUrl-extinstall>?path=/options/manageapps</EcpUrl-extinstall>
<OOFUrl>https://email.contoso.com/EWS/Exchange.asmx</OOFUrl>;
<UMUrl>https://email.contoso.com/EWS/UM2007Legacy.asmx</UMUrl>;
<OABUrl>https://email.contoso.com/OAB/9f81713a-e508-4f5b-a1ae-f8b826acc93b/</OABUrl>;
<ServerExclusiveConnect>off</ServerExclusiveConnect>
</Protocol>
<Protocol>
<Type>EXPR</Type>
<Server>email.contoso.com</Server>
<SSL>On</SSL>
<AuthPackage>Basic</AuthPackage>
<ASUrl>https://email.contoso.com/ews/exchange.asmx</ASUrl>;
<EwsUrl>https://email.contoso.com/ews/exchange.asmx</EwsUrl>;
<EmwsUrl>https://email.contoso.com/ews/exchange.asmx</EmwsUrl>;
<SharingUrl>https://email.contoso.com/ews/exchange.asmx</SharingUrl>;
<EcpUrl>https://email.contoso.com/owa/</EcpUrl>;
<EcpUrl-um>?path=/options/callanswering</EcpUrl-um>
<EcpUrl-aggr>?path=/options/connectedaccounts</EcpUrl-aggr>
<EcpUrl-mt>options/ecp/PersonalSettings/DeliveryReport.aspx?rfr=olk&amp;exsvurl=1&amp;IsOWA=&lt;IsOWA&gt;&amp;MsgID=&lt;MsgID&gt;&amp;Mbx=&lt;Mbx&gt;&amp;realm=contoso.com</EcpUrl-mt>
<EcpUrl-ret>?path=/options/retentionpolicies</EcpUrl-ret>
<EcpUrl-sms>?path=/options/textmessaging</EcpUrl-sms>
<EcpUrl-publish>?path=/options/calendarpublishing/id/&lt;FldID&gt;</EcpUrl-publish>
<EcpUrl-photo>?path=/options/myaccount/action/photo</EcpUrl-photo>
<EcpUrl-tm>options/ecp/?rfr=olk&amp;ftr=TeamMailbox&amp;exsvurl=1&amp;realm=contoso.com</EcpUrl-tm>
<EcpUrl-tmCreating>options/ecp/?rfr=olk&amp;ftr=TeamMailboxCreating&amp;SPUrl=&lt;SPUrl&gt;&amp;Title=&lt;Title&gt;&amp;SPTMAppUrl=&lt;SPTMAppUrl&gt;&amp;exsvurl=1&amp;realm=contoso.com</EcpUrl-tmCreating>
<EcpUrl-tmEditing>options/ecp/?rfr=olk&amp;ftr=TeamMailboxEditing&amp;Id=&lt;Id&gt;&amp;exsvurl=1&amp;realm=contoso.com</EcpUrl-tmEditing>
<EcpUrl-extinstall>?path=/options/manageapps</EcpUrl-extinstall>
<OOFUrl>https://email.contoso.com/ews/exchange.asmx</OOFUrl>;
<UMUrl>https://email.contoso.com/ews/UM2007Legacy.asmx</UMUrl>;
<OABUrl>https://email.contoso.com/OAB/9f81713a-e508-4f5b-a1ae-f8b826acc93b/</OABUrl>;
<ServerExclusiveConnect>on</ServerExclusiveConnect>
<EwsPartnerUrl>https://email.contoso.com/ews/exchange.asmx</EwsPartnerUrl>;
<GroupingInformation>Default-First-Site-Name</GroupingInformation>
</Protocol>
<Protocol>
<Type>WEB</Type>
<Internal>
<OWAUrl AuthenticationMethod="Basic, Fba">https://email.contoso.com/owa/</OWAUrl>;
<Protocol>
<Type>EXCH</Type>
<ASUrl>https://email.contoso.com/EWS/Exchange.asmx</ASUrl>;
</Protocol>
</Internal>
<External>
<OWAUrl AuthenticationMethod="Fba">https://email.contoso.com/owa/</OWAUrl>;
<Protocol>
<Type>EXPR</Type>
<ASUrl>https://email.contoso.com/ews/exchange.asmx</ASUrl>;
</Protocol>
</External>
</Protocol>
<Protocol>
<Type>EXHTTP</Type>
<Server>email.contoso.com</Server>
<SSL>On</SSL>
<AuthPackage>Negotiate</AuthPackage>
<ASUrl>https://email.contoso.com/EWS/Exchange.asmx</ASUrl>;
<EwsUrl>https://email.contoso.com/EWS/Exchange.asmx</EwsUrl>;
<EmwsUrl>https://email.contoso.com/EWS/Exchange.asmx</EmwsUrl>;
<SharingUrl>https://email.contoso.com/EWS/Exchange.asmx</SharingUrl>;
<EcpUrl>https://email.contoso.com/owa/</EcpUrl>;
<EcpUrl-um>?path=/options/callanswering</EcpUrl-um>
<EcpUrl-aggr>?path=/options/connectedaccounts</EcpUrl-aggr>
<EcpUrl-mt>options/ecp/PersonalSettings/DeliveryReport.aspx?rfr=olk&amp;exsvurl=1&amp;IsOWA=&lt;IsOWA&gt;&amp;MsgID=&lt;MsgID&gt;&amp;Mbx=&lt;Mbx&gt;&amp;realm=contoso.com</EcpUrl-mt>
<EcpUrl-ret>?path=/options/retentionpolicies</EcpUrl-ret>
<EcpUrl-sms>?path=/options/textmessaging</EcpUrl-sms>
<EcpUrl-publish>?path=/options/calendarpublishing/id/&lt;FldID&gt;</EcpUrl-publish>
<EcpUrl-photo>?path=/options/myaccount/action/photo</EcpUrl-photo>
<EcpUrl-tm>options/ecp/?rfr=olk&amp;ftr=TeamMailbox&amp;exsvurl=1&amp;realm=contoso.com</EcpUrl-tm>
<EcpUrl-tmCreating>options/ecp/?rfr=olk&amp;ftr=TeamMailboxCreating&amp;SPUrl=&lt;SPUrl&gt;&amp;Title=&lt;Title&gt;&amp;SPTMAppUrl=&lt;SPTMAppUrl&gt;&amp;exsvurl=1&amp;realm=contoso.com</EcpUrl-tmCreating>
<EcpUrl-tmEditing>options/ecp/?rfr=olk&amp;ftr=TeamMailboxEditing&amp;Id=&lt;Id&gt;&amp;exsvurl=1&amp;realm=contoso.com</EcpUrl-tmEditing>
<EcpUrl-extinstall>?path=/options/manageapps</EcpUrl-extinstall>
<OOFUrl>https://email.contoso.com/EWS/Exchange.asmx</OOFUrl>;
<UMUrl>https://email.contoso.com/EWS/UM2007Legacy.asmx</UMUrl>;
<OABUrl>https://email.contoso.com/OAB/9f81713a-e508-4f5b-a1ae-f8b826acc93b/</OABUrl>;
<ServerExclusiveConnect>On</ServerExclusiveConnect>
</Protocol>
<Protocol>
<Type>EXHTTP</Type>
<Server>email.contoso.com</Server>
<SSL>On</SSL>
<AuthPackage>Basic</AuthPackage>
<ASUrl>https://email.contoso.com/ews/exchange.asmx</ASUrl>;
<EwsUrl>https://email.contoso.com/ews/exchange.asmx</EwsUrl>;
<EmwsUrl>https://email.contoso.com/ews/exchange.asmx</EmwsUrl>;
<SharingUrl>https://email.contoso.com/ews/exchange.asmx</SharingUrl>;
<EcpUrl>https://email.contoso.com/owa/</EcpUrl>;
<EcpUrl-um>?path=/options/callanswering</EcpUrl-um>
<EcpUrl-aggr>?path=/options/connectedaccounts</EcpUrl-aggr>
<EcpUrl-mt>options/ecp/PersonalSettings/DeliveryReport.aspx?rfr=olk&amp;exsvurl=1&amp;IsOWA=&lt;IsOWA&gt;&amp;MsgID=&lt;MsgID&gt;&amp;Mbx=&lt;Mbx&gt;&amp;realm=contoso.com</EcpUrl-mt>
<EcpUrl-ret>?path=/options/retentionpolicies</EcpUrl-ret>
<EcpUrl-sms>?path=/options/textmessaging</EcpUrl-sms>
<EcpUrl-publish>?path=/options/calendarpublishing/id/&lt;FldID&gt;</EcpUrl-publish>
<EcpUrl-photo>?path=/options/myaccount/action/photo</EcpUrl-photo>
<EcpUrl-tm>options/ecp/?rfr=olk&amp;ftr=TeamMailbox&amp;exsvurl=1&amp;realm=contoso.com</EcpUrl-tm>
<EcpUrl-tmCreating>options/ecp/?rfr=olk&amp;ftr=TeamMailboxCreating&amp;SPUrl=&lt;SPUrl&gt;&amp;Title=&lt;Title&gt;&amp;SPTMAppUrl=&lt;SPTMAppUrl&gt;&amp;exsvurl=1&amp;realm=contoso.com</EcpUrl-tmCreating>
<EcpUrl-tmEditing>options/ecp/?rfr=olk&amp;ftr=TeamMailboxEditing&amp;Id=&lt;Id&gt;&amp;exsvurl=1&amp;realm=contoso.com</EcpUrl-tmEditing>
<EcpUrl-extinstall>?path=/options/manageapps</EcpUrl-extinstall>
<OOFUrl>https://email.contoso.com/ews/exchange.asmx</OOFUrl>;
<UMUrl>https://email.contoso.com/ews/UM2007Legacy.asmx</UMUrl>;
<OABUrl>https://email.contoso.com/OAB/9f81713a-e508-4f5b-a1ae-f8b826acc93b/</OABUrl>;
<ServerExclusiveConnect>On</ServerExclusiveConnect>
</Protocol>
<PublicFolderInformation>
<SmtpAddress>Mailbox1@contoso.com</SmtpAddress>
</PublicFolderInformation>
</Account>
</Response>
</Autodiscover>



Thanks,

George.

· 2
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Hi, George.

Do you currently have any other Outlook connecting issues?

Please check the authentication settings of the Autodiscover and EWS virtual directories in Default Web Site and Exchange Back End in IIS manager.
And compare the settings with the default settings.
Default settings for Exchange virtual directories


0 Votes 0 ·

Hi Kael,

I checked all the permissions carefully and they all have default values as far as I can see. Besides all were working before the upgrade. So I do not really know what is changed to cause these problems. These issues cannot just happen like this. Seems very mysterious to me. Going through all of these settings, options and parameters, I have to say that the system seems way too complex and error prone to work reliably. Incredibly, outlook seems to work fine otherwise so far.

Thanks,

George.

0 Votes 0 ·