AvailabilityOnly Calendar permission not working

Article
2020-04-01

Question

_{Wednesday, April 1, 2020 8:16 PM}

I am in the process of migrating from 2010 to 2016. I have 1 site already moved over and working without issue but the next site I am attempting to use has a peculiar problem.

I have moved a small number of users at the 2nd site to 2016 servers for testing to make sure everything was good. The issue they uncovered is the inability to see the availability of users still on 2010 and vice versa. 2010 users are unable to see the availability for the 2016 users. After testing various items I have discovered that when set to AvailabilityOnly, users cannot see across versions but if the permissions get set to 'Reviewer' or anything with more access than that the calendar information comes across. This change works both ways. If 'Default' is set to reviewer 2010 users can see 2016 and 2016 users can see 2010

What am i missing? What should I be checking for?

All replies (16)

_{Tuesday, April 28, 2020 3:38 PM ✅Answered}

Found the issue. A new security GPO had been pushed out to disable TLS 1.0 and 1.1 and enable 1.2. This is what broke it.

The fix was to set the registry key that tells .NET to use TLS 1.2

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NETFramework\v4.0.30319]
"SystemDefaultTlsVersions"=dword:00000001

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\NETFramework\v4.0.30319]
"SystemDefaultTlsVersions"=dword:00000001

Once the keys were in place and the server rebooted, everything started working normally again. Thanks for the help!

_{Thursday, April 2, 2020 2:45 AM}

Hi,

What's the detailed version of your Exchange 2010 and 2016?

What errors do you get when check calendars of users on different Exchange server with the default setting (AvailabilityOnly for Default)? You can post the screenshot here, and don't forget to cover your personal information.

What's the version of the Outlook? If you check with Outlook cached mode, please try to use Outlook online mode and OWA to see if the issue can be reproduced.

Please go to IIS Manager, try to recycle MSExchangeAutodiscoverAppPool and MSExchangeServicesAppPool on Exchange 2010 and 2016 to check if there is any difference.

Regards,

Lydia Zhou

Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact [email protected].

_{Tuesday, April 7, 2020 1:06 PM}

Exchange 2010 Update Rollup 30

Version 14.3 (Build 123.4)

Exchange 2016 Cumulative Update 15

Version 15.1 (Build 1913.5)

Calendar View

I have checked the permissions for the calendars from the Exchange side. Also checked the versions of Outlook

Here is what the connection status shows for the shared mailboxes. The bottom one is a user in the working site. the 2 above that one are non-working users in the new site.

_{Tuesday, April 7, 2020 1:08 PM}

Sorry, meant to reply to your post and not my own. Trying in Cached or Uncached mode has the same result.

I have checked using OWA and it is the same.

I have recycled the IIS pools on both sides and got the same results. no change. I have even restarted servers on both ends.

_{Wednesday, April 8, 2020 7:03 AM}

Can users see F/B information of the mailbox on the same Exchange server at present?

Use the following command to check the urls of EWS virtual directory. Make sure the FQDN is pointing to the correct Exchange server. If you set to use the same url for Exchange 2010 and 2016, please make sure it points to the IP of Exchange 2016:

Get-WebServicesVirtualDirectory|fl Id,InternalUrl,ExternalUrl

Regards,

Lydia Zhou

Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact [email protected].

_{Wednesday, April 8, 2020 1:33 PM}

URL's appear correct.

https://<FQDN of server>/ews/exchange.asmx

Users on 2016 at the new site can see each others F/B, but not other users in the same site who are still on 2010.

Users on 2010 at the new site can see each others F/B, but not the 2016 users.

_{Wednesday, April 8, 2020 2:16 PM}

I seem to be having this issue after having applied RU30 this weekend on the 2010 mailbox servers.

_{Thursday, April 9, 2020 9:18 AM}

You can post the screenshot or the copy the command output here, we need more details about EWS urls for Exchange 2010 and 2016. And don't forget to cover the real domain name.

Did you try to reset the AvailabilityOnly for Default? Does it work?

Please try to set Reviewer for Default for one mailbox on Exchange 2016, add AvailabilityOnly for a user on Exchange 2010. Then check what can be checked by this 2010 user.

Go to IIS Manager > Default Web Site > EWS, check Authentication and make sure only Anonymous Authentication and Windows Authentication are enabled for EWS on Exchange 2010 and 2016.

Regards,

Lydia Zhou

Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact [email protected].

_{Thursday, April 9, 2020 1:02 PM}

Setting permissions for 'Default' as 'Reviewer' does allow viewing of the calendar, but it shows details instead of Free/Busy. I tried having the user switch the 'Default' Reviewer permission from 'Full Details' to 'Free/Busy time, subject, location' while leaving all other permissions the same. We could no longer view the F/B info. Also setting permissions back to availabilityOnly for 'Default' resulted in not seeing F/B information.

Output from command

Id : EX2016\EWS (Default Web Site)

InternalUrl : https://EX2016.domain.com/ews/exchange.asmx

ExternalUrl :

Id : EX2010\EWS (Default Web Site)

InternalUrl : https://EX2010.domain.com/EWS/Exchange.asmx

ExternalUrl:

Authentication from IIS

_{Friday, April 10, 2020 6:32 AM}

I mean set the set Reviewer for Default, and set AvailabilityOnly for a specific user on other Exchange. Then check if the user can see F/B information. These command can help you check and add permissions:

Get-MailboxFolderPermission username:\Calendar
Add-MailboxFolderPermission username:\Calendar -User username -AccessRights <right>
Remove-MailboxFolderPermission username:\Calendar -User username 
Set-MailboxFolderPermission username:\Calendar -User username -AccessRights <right>

For example, user22 is on Exchange 2016, user02 is on Exchange 2010. I add additional permission for user02, then check if user02 can check F/B information of user22:

Regards,

Lydia Zhou

Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact [email protected].

_{Friday, April 10, 2020 2:27 PM}

Same result. Tried changing Default and Default and Anonymous to reviewer with user having availability only.

Still same result. Calendar view "Could not be updated" Scheduling view "/////////"

_{Monday, April 13, 2020 9:08 AM}

It's really wired, if the AvailabilityOnly permission doesn't work, it should affect all users in the organization, instead of only mailboxes on different servers. Since Exchange 2010 will reach end of support on October 13, 2020 and Exchange 2016 works well on your side, it's suggested to move all mailboxes to Exchange 2016 as soon as possible.

Regards,

Lydia Zhou

Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact [email protected].

_{Thursday, April 16, 2020 8:17 AM}

Here is a brief summary for replies above. Hope this can help people with similar issues.

Issue Symptom:

I am in the process of migrating from 2010 to 2016. I have 1 site already moved over and working without issue but the next site I am attempting to use has a peculiar problem.

After testing various items I have discovered that when set to AvailabilityOnly, users cannot see across versions but if the permissions get set to 'Reviewer' or anything with more access than that the calendar information comes across. This change works both ways.

Possible Cause:

AvailabilityOnly permission doesn't work.

Troubleshooting Steps so far:

Please go to IIS Manager, try to recycle MSExchangeAutodiscoverAppPool and MSExchangeServicesAppPool on Exchange 2010 and 2016 to check if there is any difference.

Get-WebServicesVirtualDirectory|fl Id,InternalUrl,ExternalUrl

Please try to set Reviewer for Default for one mailbox on Exchange 2016, add AvailabilityOnly for a user on Exchange 2010. Then check what can be checked by this 2010 user.

Go to IIS Manager > Default Web Site > EWS, check Authentication and make sure only Anonymous Authentication and Windows Authentication are enabled for EWS on Exchange 2010 and 2016.

Next Step:

Since Exchange 2010 will reach end of support on October 13, 2020 and Exchange 2016 works well on your side, it's suggested to move all mailboxes to Exchange 2016 as soon as possible, to make sure AvailabilityOnly permission works for all users.

Regards,

Lydia Zhou

Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact [email protected].

_{Friday, April 17, 2020 8:09 PM}

New wrinkle. Something i hadnt tested before: The 2016 users in the working site (Site A) can NOT see the availability of users in the non-working site (Site B)

Site A users are ALL on Exch 2016 but cannot see Site B, also on 2016 and vice versa. I am at a loss.

_{Monday, April 20, 2020 9:22 AM}

Before starting addressing this issue, please understand that as per our process, we focus on a single issue per post. For your new issues about cannot see cross-site F/B information, you can create a new thread to discuss it.

Hope your issue can be solved soon.

Regards,

Lydia Zhou

Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact [email protected].

_{Wednesday, April 29, 2020 1:30 AM}

That's great and thanks for your sharing. Here is a brief summary for this solution.

Issue Symptom:

I am in the process of migrating from 2010 to 2016. I have 1 site already moved over and working without issue but the next site I am attempting to use has a peculiar problem.

Cause:

A new security GPO had been pushed out to disable TLS 1.0 and 1.1 and enable 1.2. This is what broke it.

Solution:

The fix was to set the registry key that tells .NET to use TLS 1.2

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319]
"SystemDefaultTlsVersions"=dword:00000001

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\.NETFramework\v4.0.30319]
"SystemDefaultTlsVersions"=dword:00000001

Once the keys were in place and the server rebooted, everything started working normally again.

Regards,

Lydia Zhou

Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact [email protected].

Share via

AvailabilityOnly Calendar permission not working

Question

All replies (16)

Additional resources