Exchange Online
-
free/busy not working between EOL and on premise Exchange
We had an issue after adding a new domain to our tenant using the Hybrid Configuration Wizard which removed the URI and URL strings in the availability settings in Exchange Online. That was resolved but 2 days later free/busy from Exchange Online to on premise Exchange users broke again. We had to add a new SAN in the certificate for Exchange and suspect that the Federation Metadata did not properly update. One of my colleagues found this article which pointed us to the problem and advised us how to resolve the issue. In short running: Test-FederationTrust -UserIdentity yourcredentials showed the issue. To resolve my colleague ran: Get-FederationTrust |…
-
Outlook not connecting to Exchange Online mailboxes
If you find that some Outlook clients stopped connecting to the Exchange Online mailbox but OWA and ActiveSync is still connecting then check if modern authentication has been disabled for your O365 tenant To check run: Get-OrganizationConfig | Format-Table Name,OAuth* -AutoIf you find it is set to False and all your Outlook clients are 2013 or newer then enable it by running:Set-OrganizationConfig -OAuth2ClientProfileEnabled $trueYour disconnected users should start connecting within a few minutes.
-
The InnerException message was ‘Maximum number of items that can be serialized or deserialized in an object graph is ‘2000000’.
This was quite an interesting error for a mailbox I tried to migrate from Exchange 2013 to Exchange Online. The mailbox synced to 95% and I received the below error after I tried completing the batch. Error details: The formatter threw an exception while trying to deserialize the message: There was an error while trying to deserialize parameter http://tempuri.org/:ISourceFolder_EnumerateChanges2Result. The InnerException message was ‘Maximum number of items that can be serialized or deserialized in an object graph is ‘2000000’. The key to this error is the object graph limit that is set in the MsExchangeMailboxReplication.exe config file. To resolve the issue do the following: Logon to your on premises Exchange…
-
Error: MigrationRecipientNotFoundException: A recipient was not found for “mailboxName”
If you received the error “Error: MigrationRecipientNotFoundException: A recipient was not found for “mailboxName”” when migrating a mailbox to Exchange Online (Office 365) then check for the below AD attributes. The error from the Exchange Admin Portal on Office 365: Open the on premises Exchange Management Console and search for the user. You should see the mailbox shows it’s a Linked Mailbox instead of a Remote Mailbox as expected: To rectify this, open AD Attribute Editor and browse to the msExchRecipientTypeDetails attribute. You should see the below: Change the Value of 2 to 1 for msExchRecipientTypeDetails as you need the mailbox to show as a user mailbox on premises before…