https://rancher.com/ logo
#rancher-desktop
Title
# rancher-desktop
a

adamant-kite-43734

08/30/2022, 3:30 PM
This message was deleted.
h

handsome-jewelry-53515

08/30/2022, 5:07 PM
Can you share the error or message you're seeing? Is it the error mentioned in issue #1858?
r

rough-balloon-94624

08/30/2022, 7:02 PM
It is not so much an error, but rather, the installation is not being silent. A pop up happens asking the user to accept the license agreement. Since we are packaging for automated install via software center, we need a silent install for that to work.
h

handsome-jewelry-53515

08/30/2022, 10:13 PM
My searching found the same issue you've already found. It looks like the capital /S should work. We tested it here with "Rancher.Desktop.Setup.1.5.0.exe /S" and it worked for us. If you have double-checked that you've used a capital S, and it still doesn't work, there may be some configuration that has to happen in your packager to work with the electron-builder or the NSIS install system mentioned in issue #1858...
r

rough-balloon-94624

08/31/2022, 2:43 PM
Thank you. I will confirm and ask them to re-test and update you.
They confirmed that they tried /S and it still requests the user agreement. They are not packaging, just using SCCM to run the installer.
f

fast-garage-66093

08/31/2022, 8:47 PM
I have no idea what they are doing, but I can confirm that invoking the Setup program from both cmd.exe and from Powershell with the
/S
parameter does not display the license dialog. It does briefly flash a different popup, but that disappears on its own, and then returns to the command prompt. The install runs detached in the background and after about 1min you can see the desktop shortcut icon is being created.
I don't think there is anything else we can do; the people using SCCM need to double-check how they are running the installer and passing the commandline argument. Maybe SCCM is not passing it along correctly? They should start by invoking the Setup program with
/S
from the commandline. If that works as expected, it shows that the issue is not with the installer, but the way they package it.
r

rough-balloon-94624

08/31/2022, 9:47 PM
It seems the issue was related to user they were using to run the installer vs the actual user, so they have changed up that approach and it seems to have cleared the issue. Thank you all for the guidance and support.
11 Views