I have a problem...
We have integrated our RDMS Enterprise with our Active Directory, and created roles pointing to our AD Groups..
If I start RDM and log on to our RDMS datasource using only my username (user1), I will get a new user in RDMS called: ad.contoso.com\user1
It will find my groups from AD, and work as expected..
If I then start RDM and log on to our datasource using CONTOSO\user1, I will get a new user in RDMS called: CONTOSO\user1
It will also find my groups from AD, but the Private Vault sessions, and all User Settings are now different, because I now have 2 users...
So how do I merge these 2 users, so that they have the same user settings and Private Vault, and how do I avoid this situation in the future?
Roughly half of my 200 users have duplicate accounts, and I have no idea, which one is the "active" one, with the users personal settings.
Besides that, I haven't tested it, but I'm pretty sure an attempt with user1@contoso.com will also be correct, but will result in a third user...
Hello,
You are running in the issue that I've wanted to fix for a long time, but we weren't able to start this before now.
We even mention that issue in http://helpserver.devolutions.net/management_automaticaccountcreation.htm
In our next minor iteration of DVLS (3.1 or maybe 3.5 because it's a major departure from earlier), we will correlate with either the UPN or the ObjectSID for the domain account, but we'll let you authenticate with what you prefer (domain\user, domain.com\user, user@domain, etc). This will ensure we have a single account per user.
To reduce the impact of the issue, it's best to always use the full DOMAIN\USER when authenticating, both in the data source definition and in the web portal.
Since the private vault has been initialized by the account defined in the data source, there shouldn't be many duplicated accounts that both have a private vault.
To fix your duplicate user accounts, there is not easy way right now, we would have to perform account renames in SQL.
Let me know if you have duplicated accounts that both have private information, as well as if you want to go ahead with SQL statements. Our next release should have a tool to handle user renames
Best regards,
Maurice
Hello Maurice
So if I understand you correctly, you are working on a solution for this problem. Great, looking forward to it.
I understand your statement about always using DOMAIN\USER, but my users aren't...
I'm almost certain that my duplicated users don't have private info in both accounts, but I have no idea which one they are using. Hope you can see that with some SQL queries.
I would like to go ahead with some SQL command to remove my duplicate accounts.
Let's set up a remote session after christmas, so we can get this sorted out.
Kind regards,
Brian Aborg Weje
Norriq
Can I have an update on this issue. You never came back to me, with regards to the SQL statements.
Is the fix and the rename tool available in the latest release?