Outlook 2016 user on Exchange 2010 cannot see other user availability

A few users are reporting issues with being able to see the availability of other users when the create appointments. They reported the problem after upgrading to Office 2016. They're mailboxes are on Exchange 2010 SP3 UR17 however we're going to migrate to Exchange 2016 first quarter next year. Are there client connectivity issues between Outlook 2016 and Exchange 2010? What can I do to mitigate or resolve this problem for now?
Bill BensonPrincipal ConsultantAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Michael LinkInfrastructure EngineerCommented:
Here is a list for the supported Outlook/Exchange Compatibility.

There should not be a problem connecting your 2016 client to the 2010 Exchange - especially on the SP you are on.

What availability can they see? Nothing? Free/Busy time?
Bill BensonPrincipal ConsultantAuthor Commented:
Hi Michael. Thanks for your response. The users can see availability for some users but not others. Availability is not blocked. See the attachment for details.
Let's see config of your environment:
(mask real domain, format as CODE, execute on Exchange 2016 EMS)
Get-OabVirtualDirectory | fl server, Name, ExternalURL, InternalURL, *auth*
Get-WebServicesVirtualDirectory | fl server, Name,ExternalURL, InternalURL, *auth*
Get-EcpVirtualDirectory | fl server, Name, ExternalURL, InternalURL, *auth*
Get-ActiveSyncVirtualDirectory | fl server, Name, ExternalURL, InternalURL, *auth*
Get-OutlookAnywhere | fl server, Name, *hostname*, *auth*
Get-OwaVirtualDirectory | fl server, Name, ExternalURL, InternalURL, *auth*
Get-ClientAccessService | fl Name,OutlookAnywhereEnabled, AutodiscoverServiceInternalUri
Get-ExchangeCertificate | fl FriendlyName, Subject, CertificateDomains, Thumbprint, Services, Issuer, *not*
Get-MapiVirtualDirectory | fl server, Name,ExternalURL,InternalURL, *auth*
Get-ClientAccessArray | fl
Get-ExchangeServer | fl *version*
Get-OrganizationConfig | fl *mapi*

Open in new window

Big Business Goals? Which KPIs Will Help You

The most successful MSPs rely on metrics – known as key performance indicators (KPIs) – for making informed decisions that help their businesses thrive, rather than just survive. This eBook provides an overview of the most important KPIs used by top MSPs.

Michael LinkInfrastructure EngineerCommented:
Judging by what you have attached, it certainly looks like there is a permissions issue potentially to the ones that cannot be seen.

This looks like the default view before permissions haven't been granted.

I would test changing permissions on one of the accounts - it is a lot easier with PowerShell to do this.
Bill BensonPrincipal ConsultantAuthor Commented:
I showed the user a workaround. I had her delete the name she was having trouble getting availability for from the nickname cache then pick it again from the GAL. That worked for her but I'll dig into this a bit more though.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Bill BensonPrincipal ConsultantAuthor Commented:
The reason @Michael Link I was concerned about compatibility between Outlook 2016 and Exchange 2010 was Outlook users MAPI over HTTP. That should work with Exchange 2010 using Outlook Anywhere settings. However I've seen articles where users complained about Outlook 2016 connecting to Exchange 2010.
Michael LinkInfrastructure EngineerCommented:
Great glad you found a solution - I hope moving to Exchange 2016 leaves you in good stead on a good steady platform!
Bill BensonPrincipal ConsultantAuthor Commented:
I fixed the problem myself and verified with the end user the issue was resolved.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.