0 votes

Good Morning,

Interesting issue, newly created users created in Adaxes don't show AD group membership when viewing in Adaxes but the groups show normally in AD.

Users previously existing before we implemented Adaxes show group memberships fine in both AD and Adaxes.

Users being compared are in the same OU, any idea why users crearted in Adaxes cannot see the groups while other users appear fine?

by (210 points)
0

Hello,

What exactly do you mean by don't show AD group membership? Does it happen in the Web interface or in the Administration console? Please, describe the issue in all the possible details with live examples and screenshots. If there is something you cannot post here, please, send the details to support@adaxes.com.

0

When viewing a user in the web interface for a recently created user (user was created yesterday), Adaxes shows only 1 of 5 AD Group Memberships.

When viewing existing users in AD made prior to Adaxes, all AD Memberships show in the Web Interface.

Both users in question share the same OU and similar groups also stored in similar OU's.

Groups show normally for both users in the Console.

0

Hello,

Thank you for clarifying. Do we understand correctly that the two users are members of the very same groups, but when you go Adaxes Web interface for one of the users you see only 1 group in the Member Of section?

For troubleshooting purposes, please, log in with the credentials of the Adaxes service account (specified during the software installation). Does the issue persist then?

0

I was able to figure this out, even though the users had permissions to the OU where the groups were, we had the view configured in Adaxes to make the users OU we use as the "top node".

Since the groups OU and Users OU are laterally on the same AD level, I had to show the domain root instead of the OU and set permissions to deny user creation in the Groups OU to prevent accidental creations.

Thanks for the help!

Please log in or register to answer this question.

Related questions

0 votes
1 answer

I'm evaluating Adaxes. I have no business rules enabled. When I create a new user in the web interface the account is disabled after creation. Is this normal for Adaxes? In the management console it is not disabled by default.

asked Aug 7, 2020 by ComputerHabit (790 points)
0 votes
1 answer

We have been using Business Rules for newly created/changed active directory objects successfully for sometime now. In our current environment, most of our user objects are being ... Or is this better handled by a scheduled task to process newly created users?

asked Mar 25, 2015 by cmcgrath (70 points)
0 votes
1 answer

I have a Business Rule in place that after a new user is created, will create an Exchange mailbox for the user, set the Retention Policy for the user, then send them a ... the correct email address for the user. Is this maybe just a timing issue or something?

asked May 16, 2014 by RickWaukCo (320 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, 2022 by Tfarmer (160 points)
0 votes
1 answer

Automation of user creation based on ServiceNow ticket creation.

asked Jan 24, 2022 by tdetmer (20 points)
3,351 questions
3,052 answers
7,791 comments
545,102 users