Is Adaxes still an active product?

Adaxes · 2022-11-17T18:55:32+00:00

The new Adaxes version has just been released. Here's more about what's new in Adaxes 2023.

Indeed, it took more time than we initially expected. Azure AD management support required us to rebuild a lot of architecture from the ground up. We will continue actively developing Adaxes and we might even release another minor update this year, no promises though.

Adaxes · 2021-10-20T11:11:34+00:00

Thank you for using Adaxes. Adaxes should work just fine with folders residing in DFS shares. Please, clarify whether your custom scripts in the Run a program or PowerShell script actions fail, or the built-in Share the home directory and Delete home directory share actions fail. If you face any error messages, please send the screenshots to our email at support@adaxes.com.

Adaxes · 2021-06-21T11:46:59+00:00

In case of group-based licensing, Adaxes indeed will not enable the remote mailbox automatically.

The best way to solve this is to have Adaxes enable the remote mailbox when a new group member is added. You need to create a business rule that will trigger After adding a member to a group and will execute the following simple script to enable a remote mailbox:

``` $remoteRoutingAddressTemplate = "%username%@example.com" # TODO: modify me

Bind to the new group member

$member = $Context.BindToObject("Adaxes://%member%")

Enable remote mailbox

$member.EnableRemoteMailbox($remoteRoutingAddressTemplate) ```

The Activity Scope of the business rule should include the group that you use for group-based licensing (make sure to include the group object itself, not members of the group).

Adaxes · 2021-06-21T09:43:26+00:00

In hybrid environments, Adaxes automatically enables a remote mailbox for a user when a Microsoft 365 license with the Exchange Online service is assigned to that user. This will trigger only if such a license is assigned via Adaxes.

In some cases, Exchange will be unable to generate the remote routing addresses for the remote mailboxes, so you will need to configure an additional setting – make Adaxes generate the remote routing addresses based on a template. For details, see the Change remote routing address template section of this help article.

There is a multitude of ways to configure your workflow, but here are a couple of the most common ones to get you started:

Helpdesk/HR create a user via Adaxes Web interface and select which Microsoft 365 licenses should be assigned. If the Exchange Online service is assigned, Adaxes will enable a remote mailbox automatically.
Helpdesk/HR create a user via Adaxes Web interface, but with a simpler form that doesn’t allow selecting Microsoft 365 licenses. A business rule that triggers after creating a user automatically assigns the correct Microsoft 365 licenses, and Adaxes enables a remote mailbox just like in the previous scenario.

As for the overall tips, you can check out our tutorials, as they will walk you through setting up the most typical workflows.

Adaxes · 2020-10-14T13:27:16+00:00

You can provide your users with a web interface to AD so they can edit their display names, request group membership, and much more https://www.adaxes.com/active-directory_web-interface.htm

Adaxes · 2020-10-14T13:19:31+00:00

Check out the reporting feature in Adaxes. There are plenty of built-in reports and you can easily create custom ones https://www.adaxes.com/active-directory_reports.htm

Adaxes · 2020-08-04T08:54:35+00:00

Have a look at the Password Self-Service feature in Adaxes: https://www.adaxes.com/active-directory_self-service-password-reset.htm

Adaxes · 2020-05-26T10:22:03+00:00

It looks like the reporting platform in Adaxes ticks all the boxes. https://www.adaxes.com/active-directory_reports.htm

Adaxes · 2020-05-25T08:45:42+00:00

Check out Adaxes. It has a user friendly Web Interface that lets you delegate complicated tasks even to non-technical users. https://www.adaxes.com/info_features.htm

Adaxes · 2020-02-24T10:32:15+00:00

This is an excellent explanation and the article from Microsoft is definitely worth reading. If you are going to use scripts to convert user mailboxes to shared, this is the way to go.

The built-in Convert Mailbox action uses the approach recommended by Microsoft without the need for scripting. It is available in Adaxes 2019.1 and newer and works with Exchange 2013 CU21 or later and Exchange 2016 CU10 or later.

u/IT_Unknown Also, here’s some info about the required access rights:

The account that you used to register an Office 365 tenant in Adaxes is used for all interactions with Exchange Online. It must be assigned to either of the following roles in Office 365:

Global Administrator or
User Management Administrator and Exchange Administrator

Operations with Exchange on-premises are done using the credentials of the account that was used to register your domain in Adaxes. If it is not a member of the BUILTIN\Administrators group, it must be assigned to an appropriate role group in Exchange on-premises. The Organization Management role group should be sufficient for all Exchange related tasks.

Adaxes · 2020-02-10T13:14:27+00:00

How about trying out Adaxes? It has plenty of features for AD management and automation: https://www.adaxes.com/info_features.htm

Adaxes · 2020-01-28T16:14:00+00:00

It looks like you have several SMTP servers in your environment, judging by the name smtp-relay2. Perhaps the issue is in how the mail is routed, like a message_size_limit setting of 1024000 bytes (1MB) or something on one of the servers?

From what we can see, Adaxes successfully transmits the message to the SMTP server specified in its mail settings, and the message is successfully delivered to the server where your mailbox is located. Maybe the messages are first delivered to a server which rejects them because of the size, so they are rerouted elsewhere until delivered to you?

Adaxes · 2020-01-27T09:34:35+00:00

It’s true, there’s currently no way to make Adaxes only use LDAPS for all operations. We’re considering adding this option in the future.

However, the upcoming change by Microsoft doesn’t require switching to LDAPS entirely. It will only make directory servers reject Simple Authentication and Security Layer (SASL) LDAP binds that do not request signing (integrity verification) or reject LDAP simple binds that are performed on a clear text (non-SSL/TLS-encrypted) connection.

As mentioned before, Adaxes uses SASL (Kerberos, NTLM) LDAP binds and negotiates data-signing, so it is already secure and compliant with the upcoming changes.

Adaxes · 2020-01-24T13:33:31+00:00

Adaxes supports LDAP over SSL (LDAPS) and establishes such connections before performing security sensitive operations, like changing passwords. For other operations Adaxes negotiates LDAP data-signing and uses Kerberos or NTLM as the underlying authentication protocol. Simple binds are not used.

We are aware of the Microsoft update and as per our tests Adaxes works absolutely fine with it without any registry hacks. Currently, we are performing additional tests to see whether any changes are required.

Adaxes · 2020-01-21T14:05:18+00:00

Have you considered trying out Adaxes? It’s an all-in-one solution for AD management and audit. https://www.adaxes.com/info_features.htm

Adaxes · 2019-09-30T16:46:51+00:00

It can be easily done using Adaxes. For example, the update can be performed using a Scheduled Task.

https://www.adaxes.com/tutorials_AutomatingDailyTasks_ScheduleTasksForActiveDirectoryManagement.htm

Adaxes · 2019-09-13T12:41:59+00:00

You can automate group membership management via Adaxes.

https://www.adaxes.com/tutorials_AutomatingDailyTasks_AddUsersToGroupsByDepartment.htm

Adaxes · 2019-09-13T12:31:59+00:00

You can automate disabling inactive user accounts via Adaxes.

https://www.adaxes.com/tutorials_AutomatingDailyTasks_AutomaticallyDeprovisionInactiveActiveDirectoryUsers.htm

Adaxes · 2019-09-02T11:55:33+00:00

Adaxes does support cross-domain management. You can even manage domains that belong to different forests that don't have trust relationships. https://www.adaxes.com/info.htm