0 votes

Hi all,

we switched from an exchange hybrid model to online only. So we turned off our on-prem exchange server. After some tries we faced the following problem:

After assigning a Microsoft 365 license to a new created user Adaxes shows the following error:

"Failed to create a remote mailbox for the user. Connecting to remote server ###oldonpremserver### failed with the following error message : WinRM cannot complete the operation. Verify that the specified computer name is valid, that the computer is accessible over the network, and that a firewall exception for the WinRM service is enabled and allows access from this computer. By default, the WinRM firewall exception for public profiles limits access to remote computers within the same local subnet."

But still the mailbox will be created and everything works fine. Is there still a problem we donĀ“t think about? Or is it just visual? Will Adaxes recognize that there is no on-prem anymore?

Thank you for helping us!

by (100 points)

1 Answer

0 votes
by (232k points)

Hello Robin,

The error means that Adaxes is configured to enable remote mailboxes after a Microsoft 365 license with access to Exchange Online is assigned to a user. To remedy the issue, you need to disable the corresponding feature. For details, have a look at section Change when remote mailboxes are enabled and disabled of the following help article: https://www.adaxes.com/help/EnablingDisablingRemoteMailboxes/#change-when-remote-mailboxes-are-enabled-and-disabled. In your case, the corresponding variables should be set as follows:

$enableRemoteMailboxSetting = $False
$disableRemoteMailboxSetting = $False
0

Thank you very much. Helped to fix this "issue".

Related questions

0 votes
0 answers

When attempting to assign licenses during the "after creating a user" rule we're reciving the following error. Failed to create a remote mailbox for the user. The address ' ... mail attribute to the proper format that isn't the onmicrosoft.com domain as well.

asked Sep 2, 2021 by zorps (20 points)
0 votes
1 answer

Hi I'm trying to product a report to show the users with either E3, F3 or F5 licenses. If I add the Adaxes "Microsoft 365 Licenses" attribute directly to the report then ... from the user and show a nice "Microsoft E3" etc value. Is this possible? Thanks

asked Sep 27, 2021 by chappers77 (1.3k points)
0 votes
1 answer

I'm trying to retrive the Microsoft 365 License product name in a report as the 'Office 365 License' attribute in Adaxes shows each individual licensed product e.g. ... 365 F3"} } $productnames = $productnames -join ", " $Context.Value = $productnames

asked Jul 27, 2020 by richarddewis (260 points)
0 votes
1 answer

I'm trying to use "Before Modify Office 365" event to request approval for changes. It seems to be kicking off for the "After Create User" event. How do I request ... for default settings but if admins want to make a change then it goes out for approval.

asked Jul 20, 2020 by ComputerHabit (790 points)
0 votes
1 answer

Our Adaxes Microsoft 365 Tenant was created before we copmpleted the "app registration" in Azure. Which means that in the instructions for "Register Adaxes as an app in ... M365 tenant, would that affect any of our custom commands that we have created?

asked Feb 17 by Tfarmer (140 points)
2,870 questions
2,591 answers
6,730 comments
111,650 users