session tools question.

Hi,
By default, RDM does no do anything with your credential, it expect that your current user (logged Windows user) has the admin right. If you want to change it, you can specify it in the Tools tab page of the session properties.

Very cool, thank you for the quick response. I have corrected this on our system.

Now, one more question. Is there a way to limit access to session tools or sub-connections based on user groups? If i want a user to have access to only a sessions sub connection, but not the Root connection, which in my case is an RDP session... or maybe i should consider making the Root connection something other than the RDP session and making that a sub connection....
For example:

we have different levels of support staff accessing these machines and if someone were to be using RDM from say the data services department I may only want for them to access 1 of a systems sub connections and Definitely do not want that user to have access to session tools like term services manager etc, i wouldnt want servers being rebooted by people who should not have administrator access.

Sorry if i went off track a bit there, but I would really like to see a bit more granular security , I absolutely love almost everything about RDM, but i feel that it is lacking in security function / features.

SL

Hi,
I added a feature request, this should not be complicated to add for the sub connection, I just never thought of that. For the session tools, it's not a problem, but it's little more tricky.

Good idea.