New user not imported with Group Synchronization
I have a new user that has not been added to RDM automatically as expected. A new user in April was imported automatically so this appears to be a recent issue. We have not made any setting changes in quite some time, but we did apply an update since that last user started. Diagnostics shows it can see the account and when pulling members for the group it shows the new user. Devolutions is just not adding him the user group.
All Comments (5)
Hello,
Thank you for your feedback.
Could you provide the RDM version and the data source you are currently using? If it's Devolutions Server, what version are you using?
Best regards,
Érica Poirier
Hello,
Thank you for your feedback.
Could you provide the RDM version and the data source you are currently using? If it's Devolutions Server, what version are you using?
Best regards,
I use RDM and Devolutions interchangably since my users recognize RDM but not Devolutions. The on prem Devolutions server is running 2025.1.9
Hello,
Thank you for your response! Could you kindly provide us with the following information:
- The configuration of your "Auto create on first login" under "Automatic user creation".
- Are you using Domain authentication?
- If you're using domain authentication, could you please follow this helpful topic to get a diagnosis of the authentication?
https://docs.devolutions.net/server/kb/troubleshooting-articles/domain-group-not-retrieved/
Once we have this information, we will be better equipped to diagnose and resolve the issue.
Best regards,
Maxim Robert
Auto Create
- User Type: User
- Only from this group: RDM_UsersGroup
- Username format: UPN
Please note that the user in question is a member of the specified group
Domain Authentication: Yes
No issues running the diagniostics. From the document, step 11, I changed the strategy for Get groups by user from Default (LDAP) to Directory entry token group
This previous setting using Default (LDAP) was working. Since I have manually added this user, I will have to wait for thre nexct user to see if that change resolves the issue.
The previous update was on March 27 so the version would have been 2025.1.4.0. until May 21st when i upgraded to 2025.1.9 The last user that imported automatically was in later part of April. IF this corrects the issue, then one of the releases since 2025.1.4 would have made it necessary.
I reviewed your release notes.
2025.1.5 - Core - Added a fallback mechanism when the Preferred Domain Controller is not available
We did not have a preferred DC set but did set the primary which is located in the same data center as the Devolutions server, buit it made no difference
I saw no other items in the available release notes that could have impacted, but the release notes are just a summary. Something did change and hopefully the new setting has resolved it for the next new user.
Close the case, i will reopen at such time we see this again.
Hello,
Thank you for your feedback. I will now mark this thread as resolved.
If you reencounter the issue, please let us know.
Elevate your learning - Join the Devolutions Academy!
Best regards,
Maxim Robert