Hi @pwbguy ,
Thanks for your reply and sharing.
Great to know that you've already thought of solution and really appreciate it for your sharing!
By the way, since the Microsoft Q&A community has a policy that "The question author cannot accept their own answer. They can only accept answers by others." and according to the scenario introduced here: Answering your own questions on Microsoft Q&A, I would make a brief summary of this thread:
[Exchange 2019 : Internal User shared calendar not syncing]
Issue Symptom:
- This certificate pops up on all internal LAN outlook clients every time they open since the internal .local name of the exchange server is not on the SSL cert.
- Even though mail flow is working fine desktop/mobile both internally and externally, the internal user who we reset the profile now is not syncing on shared calendars. But OWA works
Verified permissions to the calendar correct by adding same permissions to another user that accesses shared calendar externally and they can sync well.
The Solution:
- The final fix for the certificate popup was ensuring all VirtualDirectory internal URL/Uri's pointed to the same external, as well as setting the external site record for DNS to the internal server (not internal to external as might be assumed)
- The issue where internal users can access shared calendars, but no changes/update reservations is resolved with the following steps
- Reinstalling Outlook (and/or resetting profiles)
- Removing all Outlook AppData (both Roaming and Local)
- Removing Autodiscover Registry entries
- Removing all .xml autodiscover files from User Outlook folder (where .pst/.ost files live)
You could click the "Accept Answer" button for this summary to close this thread, and this can make it easier for other community member's to see the useful information when reading this thread. Thanks!
If an Answer 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.