Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Tuesday, October 17, 2017 7:28 PM
Hi,
I suddenly started to get this errors.
I have Exchange 2016 Hyper. When I look for a mailbox on onPrem Exchange get-remotemailbox xxx I get his error.
This error is only happening on some mailboxes, not all. The user is created in Office365 online and I can use
get-remotemailbox xxx there for this user with no problem. I have cheked AD replication and every thing is ok there.
I can do get-aduser xxx with no problem in the same PS cmd. The user has license and i can use webmail ad look at his mailboxs user with no problem.I have two Exchange 2016 servers onprem and it is the same on both.
Any ideas ?
Thans
Erro
All replies (4)
Friday, October 20, 2017 1:02 PM ✅Answered | 2 votes
It means you've created the mailbox on-line but not done anything on-premises to make on-premises Active Directory/Exchange aware of it.
When you run the Get-Mailbox/Get-RemoteMailbox cmdlets in Exchange on-premises, it's querying Active Directory for users with certain values in msExchRecipientDisplayType, msExchRecipientTypeDetails, and (sometimes) msExchRemoteRecipientType. It is NOT querying Exchange Online directly.
To fix your problem, for the users returning that error, run Enable-RemoteMailbox -Identity <user> -RemoteRoutingAddress <address ending in @tenant.mail.onmicrosoft.com\> in your on-premises Exchange environment. That will populate the appropriate msExch* details fields and the user's on-premises targetAddress.
For example, if your tenant name is mytenant.onmicrosoft.com, your custom domain is mydomain.com, and you created user JohnD in Active Directory and enabled his user account [email protected] with a license directly in Office 365, what you'll want to do in your Exchange On-Premises environment:
Enable-RemoteMailbox -Identity JohnD -PrimarySmtpAddress [email protected] -RemoteRoutingAddress [email protected]
You'll need to check your user's proxy Addresses in Office 365 to make sure you are selecting a routing address that is actually stamped on his mailbox. At that point, you'll be able to run a Get-RemoteMailbox against JohnD and have it return values.
Tuesday, October 17, 2017 9:30 PM | 1 vote
Hi,
I suddenly started to get this errors.
I have Exchange 2016 Hyper. When I look for a mailbox on onPrem Exchange get-remotemailbox xxx I get his error.
This error is only happening on some mailboxes, not all. The user is created in Office365 online and I can use
get-remotemailbox xxx there for this user with no problem. I have cheked AD replication and every thing is ok there.
I can do get-aduser xxx with no problem in the same PS cmd. The user has license and i can use webmail ad look at his mailboxs user with no problem.I have two Exchange 2016 servers onprem and it is the same on both.
Any ideas ?
Thans
Erro
If you log on to the EAC on-prem do you see the Office365 Mailbox?
What are the values of the following attributes on the AD Accounts:
msExchRecipientDisplayType
msExchRecipientDisplayTypeDetails
msExchRemoteRecipientType
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread
Wednesday, October 18, 2017 5:09 AM
Hi,
yes I can see All Office365 mailbox, included the one I am having problem with. I am also having problem with other mailboxes. The one I am working on I hve recreated that twice. Bothe my on-prem Exchange servers have been restarted.
msExchRecipientDisplayType <not set>
msExchRecipientDisplayTypeDetails <not set>
msExchRemoteRecipientType <not set>
thanks
Erro
Wednesday, October 18, 2017 9:04 AM
Hi Erro,
In general, it's recommended to create a remote mailbox on on-premise Exchange via "New-RemoteMailbox" command, instead of creating mailbox in exchange online directly. You can refer to the following article to create a mailbox again and check if there is the same issue:
Creating an Office 365 Mailbox in a Hybrid Configuration
Why Use These Methods to Create an Office 365 Mailbox?
It’s possible to simply create the Office 365 account in Active Directory, wait for AD Connect to sync the user to Office 365 and license the account. But creating new mailboxes this way never fills in the correct Exchange attributes on the user’s AD account, which causes them to not display in the local EAC. This could also potentially cause the inventory of both the on-premises AD Connect domain and the Azure AD domain to end up with incorrect data and conflicts.
Please note: Since the website is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information. And the changes made in the above blog is not supported officially by Microsoft.
Best Regards,
Niko Cheng
TechNet Community Support
Please remember to mark the replies as answers.
If you have feedback for TechNet Subscriber Support, contact [email protected].