Centralised RDM

Hi,
I really don't know if it's possible because I never tested that. I really don't know if it will works because RDM launch other application and I don't know what will happen in RemoteApp. For example, if you open a Telnet session, Putty is executed. So, maybe if you try to open an RDP connection embedded it might work but I really don't know.

If you want to give it a try, I will be able to help you if you got an error message.

Just install a copy of RDM on a windows server and then remote into the server to access RDM. I currently do this in conjunction with our SSL-VPN in order to remotely access out clients assets from a public computer or a machine that is not running RDM. I can verify it will work with multiple user profiles at the same time as well so that should meet your needs. You would of course have to buy Remote Desktop Services licenses if you need more than 2 simultaneous sessions of this type.

Thanks for the replies. Will probably look at TS Gateway as well.

Thanks again. Great product.

Hello,
We do have try this: -> RDM installed on a server in a Mapped Drive. Every users have to go to the RDM folder on this drive and launch the app from the same link.
We can see all the global sessions as if it was executed from multiple hosts,still don't have any connexion/RemoteApp problems, everything is working fine actually.
RDM sees the good Windows (AD) credentials for each user logged on his local machine and the credentials/security groups also work fine.
The "other apps" are launched on the local computer from this mapped drive and multiple connections to the same host with the same Remote App. doesn't shown any problems.

It avoids massive deployment of RDM and all the users are using the same .cfg file. the only thing that we can see in the %appdata% (local) is the addon folder of RDM.

All this sounds/looks like HEAVEN, but, it leads us to a problem for which one I can't find any workaround. (certainly due to this way of working)
When people makes changes in the RDM General Options , the last closed instance of RDM will write the settings in .cfg (FOR EVERYONE as said before)
So, there is my point.... is there anyway to "lock" the general settings/options of RDM for all users while us, admins, will still be able to edit those settings?
We certainly need something else than apply permissions/restrictions on the .cfg file as workaround.

Best Regards,

By the way, you'll understand it in my language:

RDM est réellement un super programme qui (ça n'engage que moi) dépasse de loin ses concurrents gratuits ou non.
Vous faites un super boulot et cela nous permet d'économiser beaucoup d'heures du notre par la même occasion!!
J'espère que vos utilisateurs vous le rendent bien!
edited by Vauln on 3/18/2011
edited by Vauln on 3/18/2011

Quick edit: We work with an SQL Database source

Hi,
First of all, thank you for your comments. I have one question before, why are you sharing the cfg file? Is it only because you want to share the data source settings? I'm asking that because the could change the way we handle data source for future version. What I mean, maybe we should separate the data source config from all the other configuration. What do you think?

If it's not the case and you want to share some other setting the solution could be like you said to add a password for editing the settings.

For now, I have no solution but you answer will help me find out what we should do.

Merci:)

Hello,
We are sharing the config file for multiple reasons:
As you said, the first one is to share the datasource without having to apply this to all machines (moreless 100). It looks in the same way that the "non-deployment" (we are agreed that we still need a site licence fo this way of working!)
So it's an "ease of use" for us to install and maintain.
But the principal reason why we try to work this way, it's to lock the configuration of RDM as we can do with session settings.
There are many departments in our company that needs the same connections, developpers,IT admins,SQL Admins, and also some commercials(newbies that'll make me cry if they can configure something else than their OS toolbars).
So the final purpose is that only 3 peoples will have the opportunity to configure sessions / RDM and SQL data source.
The other ones can only start Remote sessions. We don't even want them to put the treeview on the right if we don't want to!

Sooo long thanks for your fast reply.
During this Weekend I'll give a try to some permissions/restrictions directly on the config file and'll see if it could be some workaround for us and give you a feedback during the next week.

To answer your question, I do think that it"ll be a good idea to separate datasource config and all ohers config and also to lock these configs with a password.
But, I'm kinda opportunist on saying that because it serves my needs of course!!

Best Regards!

PS: Mais derien c'est sincère, un beau produit, de la réactivité pour votre support et une implémentation rapide en fonction des besoins de votre clientèle... de quoi en faire pâlir plus d'un!!
Bon W-E à Devolutions!

Hi,

It works perfectly with these permissions.
The admins can change general settings if it is needed. [RWX]
The user can also changes these settings but when he restarts RDM, they are back to the default ones [RX]

So it fits our needs at perfection.