Unable to save the user in the database
I still/also have this issue.
While in the phase of documenting RDM for the team, I deleted a user from the RDM - User And Security Management window.
When I tried to re-create the same AD-integrated user, I get the following error messages:
(Orange - Warning):
Unable to save the user in the database!
The server principal '<domain>\<username>' already exists.
(Red - Error):
Unable to save user
I have checked that the user is not already created under the "Security" 'folder' (for lack of better word, the icon is the same as a folder :)) on the SQL Server. He's gone..
I have tried connecting to the data source (SQL 2014, hosted in-house) with both my own credentials (created via. RDM User and Security Management - with admin rights), and with the service account I used while configuring the RDM database. Same results. :(
Let me know if you would like the application log, or if you have any ideas on how to solve this. It's a bit of a problem that a fifth of our team cannot connect because I deleted his account and now cannot create him again. :(
How to configure pass-through authentication?
Hi, quick question that I don't seem to be able to solve/find the solution to.
Software: Remote Desktop Manager Enterprise Edition
Version: 10.0.4.0 64-bit
Very simple; I want to create a Central Data Source on MS SQL, and have each connection use the users current Windows credentials, for pass-through to the server in question. Primarily for MS RDP connections, but also for SSH and VMware (if possible).
I've tried the different values in "Credentials", and of course the "Always ask for credentials" is NOT checked. I've also ensured that "Activate network level authentication (SingleSignOn)" is checked (have also tried unchecked).
Each time I connect to a remote machine (in this case a 2008 R2 server, that's NOT affected by any Terminal-Server specific group policies etc.), I get prompted for username/password.
I've never had this problem in mRemoteNG, but would really like to make the move to Remote Desktop Manager with a shared central configuration. :)
Thanks in advance
Simon