2/1/2012 6:12:43 AM
IQ_STWON
Posts: 3
|
Hiya,
with RDM Enterprise V 6.6.0.0 running in Windows 7 64Bit we have an issue with the session tools credentials.
We use MSSQL as backend and have several RDP connection configured, each without session credentials. Each user has user-specific credentials configured, indiviually for each connection. Session tools are configured to use the session credentials via the tools-tab, since the user running the RDM does not have administrative rights.
When running RDM in user context, the session tool configurations is completely ignored, RDM tries to use the local user (the one who started RDM) to connect to services, event log, etc.
When running RDM with (local) administrative rights on the same user, the general behaviour remains the same, only a specific credential configured in the tools tab works. User specific credentials are ignored, even when switching to "use session credentials" in the tools tab.
Since we need our technicians to use a local non-administrative account for every-day work and individual admin-accounts only when really needed, we would highly appreciate a solution.
regards
Ingo Quade
Studentenwerk OstNiedersachsen AöR
|
|
0
• permalink
|
2/1/2012 11:25:32 AM
David Hervieux
Administrator
Posts: 4248
|
Just for a quick test to help me, if you use the custom credential in the tool tab page, does it work?
--
David Hervieux
Devolutions inc.
|
|
0
• permalink
|
2/2/2012 1:43:04 AM
IQ_STWON
Posts: 3
|
Hi,
when RDM ist started with administrative rights, custom credentials work. If it's started in user context, they don't. Besides: If a connection attempt using the tools to one server was successful, it will continue to do so no matter what you change the settings to, or if RDM has administrative rights. So for testing you can only use one connection until authentication was succesful. This might be helpful for testing 
regards
Ingo
|
|
0
• permalink
|
2/2/2012 2:54:33 PM
David Hervieux
Administrator
Posts: 4248
|
Hi,
I'm not sure what we can do for that. I will investigate. I'm afraid that's a limitation of the UAC.
When a connection is successful, it's normal that Windows continue to use it. It's the same behavior than connecting to a network drive.
--
David Hervieux
Devolutions inc.
|
|
0
• permalink
|
2/3/2012 1:01:02 AM
IQ_STWON
Posts: 3
|
Hi,
Don't get me wrong, I could perfectly live with running RDM with local administrative rights. The only thing I would like, is the tools section using the user specific credentials, so that our technicians can manage services and event logs without them having to be domain admins. When I use the Windows computer management console to directly connect to a server and use custom credentials it works, so I assume this has nothing to do with UAC.
|
|
0
• permalink
|
2/3/2012 4:56:35 AM
David Hervieux
Administrator
Posts: 4248
|
You right about the user specific setting, I will verify this for sure and fix the bug. I think the application does not resolve the User specific setting before applying it.
--
David Hervieux
Devolutions inc.
|
|
0
• permalink
|