SessionTools
when i attempt to access terminal sessions via session tools , weather or not i can actually make the connection , RDM stops responding for about a minute with a blank screen. Can not operate at all until it completes attempting to connect, and there is no failure message it just leaves a blank terminal sessions window open.
Don't know if there is a way to prevent this type of behavior or not, but I find it to be a little annoying.
I've tried tweaking timeout values and have had no luck, duration of application not responding seems to remain consistent regardless of timeout config.
EW
Linux Client?
what would the likelyhood be of there ever being client that either runs natively or using WINE under linux?
SL
session tools question.
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
session tools question.
i'm wondering what credentials the session tools use by default, i've got a number of servers set up with openvpn tunnels that are constantly open so i should have access to all ports on these machines... but when i attempt to use session tools, for example, terminal services manager, so i can boot some folks off of a machine to get on myself.... it fails due to invalid credentials.
are my local host credentials the ones being used here, or is it the sessions credentials
ew
v6.0, RDP sessions hang RDM upon disconnect
First off let me say I think you offer a fine product. My company is now on it's second year of global / site license. Your product has saved countless man hours and is worth every penny and more than what you are even asking for. Kudos to Devolutions.
Now for the business....
It seems that after upgrading to v6.0 , and upgrading my data source to V6.0 as well, now when i have 5 or 6 RDP sessions opened up, when i log off, or attempt to close a tab RDM stops responding all together for a minute or 2 before it becomes able to interact with again.
This happens both when i try to start/log off , or if i just close the tab.
I can recreate it every time on my machine. curious if this has been reported yet or if you have possibly seen this behaviour yourself?
thanks,
EW
edited by SLuMLoRd on 2/25/2011