Silent install RD Gateway / RD services
Disabled
Hi,
I am following these instructions to get RDM installed on a terminal/RD Services server:
https://help.remotedesktopmanager.com/index.html?installation_custominstallerservice.htm
Everything works great, except if a pre-requisite (redistributable) is not available the /Quiet /Passive does not work for those pre-requisites and an UI prompts for installing those. I am building the actual infra as code in AWS and this kind of block the automatic installation of the whole thing. I can, of course, pre-install the redistributables in the machine, but chances are that over time these will change so we need to keep testing and updating these over several months/years and this is typically that thing that falls throught the cracks until it breaks. The automatic install of the redistributables is great.
Now: is there any swithces or parameters there that can be used to pass so that these redistributables installation are done silently too?
I tried looking at the logs using "msiexec /log logfile.txt /i <rdminstallfile>.msi", but cannot figure out a way to do this.
Thanks!
All Comments (3)
Hello,
As I understand, you would like to deploy RDM in a Terminal Server environment. Am I correct?
If yes, I would recommend consulting the online help topic below to properly configure RDM in this kind of environment.
https://help.remotedesktopmanager.com/installation_terminalservices.htm
Best regards,
Jeff Dagenais
Yeah, that's what I am following. My apologies, the link I put there was the the wrong one, that page you mention bring me to this one: https://help.remotedesktopmanager.com/index.html?installation_allusers.htm this is where I encounter the problem with the pre-requisites (C++/VS redistributables). See image on a test machine.
https://ibb.co/cdE5px
Hello,
Over the years we've removed everything that we had electively set as mandatory/pre-req. We had to do this because a minor percentage of our community was getting a lot of errors when in hardened environments. I believe that those last remains are unavoidable as .net code is run by the installer and therefore some components must be present at all costs.
As they are tagged pre-reqs as dependency packages, being that they are themselves built using the installer technology, it would be expected that they respect the command line parameters since they are the standard ones supported by msiexec. I would have to look at the detailed logs to see why msiexec decides to show a confirmation dialog when we request a silent install.
But, for the problem at hand as it appears today, I see not other choice apart from managing them beforehand as you describe. I believe they've changed twice in the 5 years I've been here.
Sorry about that.
Maurice