O365 Hybrid Remote Mailboxes

Question

Hello,

I am trying out Adaxes right now and currently want to automate the steps after creating a user, more specifically O365.

FYI, we have a hybrid environment and are also using dirsync to sync our on-prem with it.

I want to set it up so that help desk can create the user account through their portal, and Adaxe will assign the O365 license plus create a remote mailbox for them.

I have the licensing part working but I am encountering various problems with the remote mailbox part like "WinRM client sent a request to an HTTP server...", "Cannot validate argument on parameter 'Id'", and "Cannot validate argument on parameter 'Session'".

Can someone please help me get the right script for this operation?

Comments

Hello,

For troubleshooting purposes, could you specify what version of Adaxes you are currently using?

To check that, do the following:

1. Launch Adaxes Administration Console.
2. Right-click your service.
3. Click Properties in the context menu.
   
4. Adaxes version is displayed on the General tab.
   

---

Hello,

I am using version 3.8.14823.0

Answer 1

Hello,

Starting from Adaxes version 2016, when you assign an Office 365 license that includes the Exchange Online service to a user, Adaxes automatically creates a remote mailbox. You do not need to use any scripts.

Comments

Hi,

How about shared mailboxes?
Do you have any advice for Hybrid setup to create a shared mailbox directly in the cloud?

---

Hello,

Have a look at the following script from our repository: https://www.adaxes.com/script-repositor ... e-s160.htm.

---

Awesome, any idea how long it takes? I've created a new user, and dirsync has run yet there is no mail contact on my local 2010 Exchange.

I've tested this by emailing that account internally, and externally. Internally, it works. Externally, I get an undeliverable message.

---

Hello,

I've tested this by emailing that account internally, and externally.

Could you specify what exactly is meant?

Externally, I get an undeliverable message.

For troubleshooting purposes, could you post here or send us (support[at]addaxes.com) a screenshot of the error message you get?

---

Hello,

I've tested this by emailing that account internally, and externally.

Could you specify what exactly is meant?

If I send an email to this address from another email of the same domain (internal), it works fine. If I send an email from another domain to it, it bounces back because a remote mail contact was not created automatically by Adaxes.

"Delivery has failed to these recipients or groups:

MJackson@optrust.com (MJackson@optrust.com)
The e-mail address you entered couldn't be found. Check the address and try resending the message. If the problem continues, please contact your helpdesk."

---

Hello,

For troubleshooting purposes, could you check if enabling remote mailboxes is turned on. To do so, use the View Current Settings script from the following help article: https://www.adaxes.com/help/?HowDoI.Per ... boxes.html.

If the feature is disabled, use the Enabling Remote Mailboxes script from the same help article to enable it.

If enabling remote mailboxes is turned on, check Adaxes Event log for the error that looks like the following:

Softerra.Adaxes.BackgroundThreadException: Exchange 2010 PowerShell API: Failed to execute the following operation: Enable remote mailbox for 'MJackson (example.com)' ---> System.Management.Automation.RemoteException: The address "@example.mail.onmicrosoft.com" is invalid: "@example.mail.onmicrosoft.com" isn't a valid SMTP address. The domain name can't contain spaces and it has to have a prefix and a suffix, such as example.com.

For information on how to view the Event log have a look at the following help article:
http://www.adaxes.com/help/ServiceAdmin ... ntLog.html.

The error means that remote routing address template is not properly configured on your Exchange Servers. To configure the remote routing address template, use script Changing Remote Routing Address Template from the help article mentioned above.

---

Awesome, I've configured it accordingly and now it's working as expected!