Comments on: Exchange federated calendar sharing issue

By: Mike MacDonald

Mike MacDonald — Tue, 26 Jan 2021 16:48:21 +0000

Thank you so very much Peter. A well written, accurate post, that did indeed resolve my issue.

By: Avshalom

Avshalom — Sun, 28 Jul 2019 13:31:54 +0000

Great man, Perfect Solution, worked like a charm

By: simon dean

simon dean — Thu, 18 Jul 2019 10:48:25 +0000

Thank you for sharing. 2 hours and 40 minutes of looking, your command
Get-Federationtrust | Set-Federationtrust -Refreshmetadata
solved the issue on a ticket which has been open for 8 days. Thanks again

By: Peter

Peter — Thu, 23 Nov 2017 13:13:26 +0000

In reply to Christian Wilmot. You`re welcome!

By: Christian Wilmot

Christian Wilmot — Thu, 23 Nov 2017 12:48:38 +0000

Thank you so much for posting this article! This worked perfect for me!

By: Peter

Peter — Mon, 11 Sep 2017 13:23:41 +0000

In reply to Bob. You`re welcome Bob! And thanks for the information about the 401 unauthorized call error.

By: Bob

Bob — Mon, 11 Sep 2017 08:18:19 +0000

Thanks for the help! FYI, the above solution also works for a 401 unauthorized call.

“Autodiscover failed for email address user@mydomain.com with error System.Net.WebException: The request failed with HTTP status 401: Unauthorized.

By: Peter

Peter — Wed, 26 Apr 2017 11:17:43 +0000

In reply to Andy. You`re welcome! Glad to help :)

By: Andy

Andy — Wed, 26 Apr 2017 10:58:29 +0000

I cannot thank you enough for posting this fix. It worked perfectly for me after I had tried almost everything else.
Thanks!!

By: Peter

Peter — Wed, 29 Mar 2017 06:49:01 +0000

In reply to Corey. As far as I know you can only see free/ busy when setting up an appointment/ meeting or using the scheduling assistant. You are also limited in setting permissions in a cross-forest (hybrid) infrastructure. You cannot set permissions on user level cross-forest, so you have to change the default permissions to give cross-forest users a higher level of access to the calendar. It is best practice to move the users with access to each other mailbox (and shared mailboxes) in the same migration batch, to avoid this situation.