Exchange 2013 onprem problems

[vijayg]

Hello,

I would like some help please. we have onprem exchange 2013 in a hybrid setup.

 

1. we create a user on AD

2. User shows up on exchange and we assign them an email and assign them to storage database according too rights i.e student or staff

3. The user shows up on office 365 admin center we assign them a license

4. Auto discover point to our web mail address on-prem exchange server 2013

5. AD sync is used to sync users on hybrid setup

 

 

This is how it works in a nutshell. However ,recently we create a user on the AD and that user bypasses our on-prem exchange and gets created on office 365 . This give the user the office 365 web mail address online . The user can't see our on-prem address or send and receive emails. Any advice would be helpful.

 

Thank You.

[chaplic]

Hello,

I would like some help please. we have onprem exchange 2013 in a hybrid setup.

 

1. we create a user on AD

2. User shows up on exchange and we assign them an email and assign them to storage database according too rights i.e student or staff

3. The user shows up on office 365 admin center we assign them a license

4. Auto discover point to our web mail address on-prem exchange server 2013

5. AD sync is used to sync users on hybrid setup

 

 

This is how it works in a nutshell. However ,recently we create a user on the AD and that user bypasses our on-prem exchange and gets created on office 365 . This give the user the office 365 web mail address online . The user can't see our on-prem address or send and receive emails. Any advice would be helpful.

 

Thank You.

 

 

If you create an AD account (without a mailbox), have that synced to the cloud, and in the cloud it has an exchange license, it will create a mailbox

 

Back on prem, the AD account still doesn't have any mail attributes

 

 

Solution

 

1) Don't license the user for Exchange Online. No mailbox will be created

 

2) Create AD account and quickly enable-remotemailbox which will create the on-prem mail attributes and sync them to the cloud, all working as it should.

[psydii]

...or create the user using the new-mailbox command so mailbox properties are set at the same time the object is created.

 

This ensures that the on prem mailbox information is in place before the object properties sync to Office365. This should stop the automatic allocated Exchange Online licence creating a cloud mailbox for the user.

 

https://docs.microsoft.com/en-us/powershell/module/exchange/mailboxes/new-mailbox?view=exchange-ps

[psydii]

Hello,

I would like some help please. we have onprem exchange 2013 in a hybrid setup.

 

1. we create a user on AD

2. User shows up on exchange and we assign them an email and assign them to storage database according too rights i.e student or staff

3. The user shows up on office 365 admin center we assign them a license

4. Auto discover point to our web mail address on-prem exchange server 2013

5. AD sync is used to sync users on hybrid setup

 

 

This is how it works in a nutshell. However ,recently we create a user on the AD and that user bypasses our on-prem exchange and gets created on office 365 . This give the user the office 365 web mail address online . The user can't see our on-prem address or send and receive emails. Any advice would be helpful.

 

Thank You.

 

To fix it for this specific user (and any others in a similar state): Raise a support ticket through the admin portal - I've had this happen occasionally. They have a set of steps to follow, but the exact steps depend on the exact scenario and current state of the objects.

[vijayg]

Thank you for your reply. I have tried this unfortunately did not work for me.

 

Thank You.

[vijayg]

Thank you for your reply. How do I get help from admin please.

[chaplic]

Tried what, and how long did you wait?

 

Does the user account in question have MsExch attributes populated (things like MsExchRecipientDisplayType in attribute editor of AD users and computers

[vijayg]

Hi ,

I have tried creating a user and then enable remote mailbox and not licensed the user . Unfortunately that did not work . On your second question no those attribute do not show on the user AD account.

 

thank you

[vijayg]

Hi ,

I have checked account they don'y populate with things like MsExchRecipientDisplayType in attribute editor of AD users and computers ?

 

Thanks

[chaplic]

Hi ,

I have checked account they don'y populate with things like MsExchRecipientDisplayType in attribute editor of AD users and computers ?

 

Thanks

 

Okay

 

This is the root-cause of the problem, everything else is a symptom. To have a mailbox on prem, these attributes (MsExchRecipientDisplayType, proxyAddresses, msExchRecipientTypeDetails)

MUST be configured for you to have a mailbox

 

That all said, I have no idea what's up. I am assuming you have one active directory and exchange is NOT in its own resource domain. What happens in teh Exchange ECP when you create a mailbox from an existing AD Account?

[vijayg]

Hi we have three DC . DC01 replicate to two and three and one exchange server .

 

Thanks

[psydii]

How to raise a support ticket in Office365: https://www.bing.com/search?q=raise+a+support+ticket+office+365