What's inside an .rdi file for Custom Installer?

Published 13 years ago

Hi RDM Support

I have looked around on both this Forum and Online Help, and I can't find an answer to this question.

What is included in an .rdi file for the Custom Installer?

I have just successfully completed my first deployment to a workstation using a custom installer generated from an .rdi file, and to my surprise, I found that it included more settings than I was expecting as follows :

1) License Key - I did expect this - OK
2) Data Source - I did expect this - OK
3) All options - I wasn't expecting this
4) Quick Connect History - I certainly wasn't expecting this!
5) Search settings - I wasn't expecting this
6) Window position and size - I wasn't expecting this

These are the things I noticed, so it started me wondering - what else is included in the .rdi file that ultimately becomes part of the package?

I woud like to know so that I can control the contents of the package more accurately.

Thanks
Des

All Comments (2)

David Hervieux

Published 13 years ago

Hi Des,
The custom installer is generated from the file remotedesktopmanager.cfg located in %LocalAppData%\Devolutions\RemoteDesktopManager

We will update the rdi file in optionally include or not those options

David Hervieux

ceo_rdm

Published 13 years ago

Hi David

Thanks for the prompt reply. Does the entire .cfg file get used - verbatim? If so, I am quite alarmed by that, because I have just been browsing through the contents of the .cfg file and have found quite a few entries on my PC (the PC I used to generate the .rdi) that are unique to my workstation, or me, and I certainly don't want them included in a mass-deployment package!, eg :

1) CustomInstallationPathArray - this would be unique to a PC
2) DefaultProxy - this seems to have my proxy credentials saved under the SafePassword property - certainly don't want this distributed!
3) ErrorCompany - this is probably OK for us, I suppose, because I'm distributing to other people within the same company, but may not suit everybody
4) ErrorEmail - This is my Email address - shouldn't be included
5) FilezillaInstallationPath - like 1) above - come to think of it - shouldn't this be part of 1) above?
6) FilterArray
7) GoogleChromeInstallationPath - like 5)
8) PlacementArry - would depend on the screen geometry of the target PC
9) QuickConnectArray
10) RegistrationEmail - I know we want the package to be "ready-registered", but would it work if we excluded this field, and just put in RegistrationSerial?
11) Ditto for StandardRegistrationDate, Email and Tag

There must be others as well, these are just the ones that I've customised on my PC, and were therfore easy to find.

Regards
Des