Silent install

[TheSori46]

Hi all,

I need to create a script to install only VNC Server, register it as a service, and set my password. I have seen other posts, and I have this script:

Code: Select all

UltraVNC_1435_X64.msi SERVERVIEWER=1 SERVICE=1 SETPASSWD=test1

Additionally, I would like no icon to be created on the desktop.

[Rudi De Vos]

msi
UltraVNC_1435_X64.msi SERVERVIEWER=1 SERVICE=1 PASSWORD=test1

inno setup
Using inno setup it's simpler. You can record your settings to a file and later use this file as input for a silent install.

/LOADINF="filename"
Instructs Setup to load the settings from the specified file after having checked the command line. This file can be prepared using the '/SAVEINF=' command as explained below.
Don't forget to use quotes if the filename contains spaces.

/SAVEINF="filename"
Instructs Setup to save installation settings to the specified file.
Don't forget to use quotes if the filename contains spaces.

[keith_andrews]

I've tried using the parameters specified for the .msi install, but the only way I've gotten it to work so far is if I don't include the PASSWORD parameter. There is also contradicting information regarding whether to use parenthesis or not for the password.

In this posting you are suggesting the following command line:

UltraVNC_1435_X64.msi SERVERVIEWER=1 SERVICE=1 PASSWORD=test1

But in the release documentation for ver. 1.4.36, you provide the following sample:

UltraVNC_1436_X86.msi SERVERVIEWER=1 SERVICE=1 PASSWORD="mypass"

Is there a way to pass the password parameter through command line so it doesn't have to be set manually on each machine? I'm trying to deploy this through Intune.

Thanks!
Keith

[Rudi De Vos]

Retested
UltraVNC_1436_X86.msi SERVERVIEWER=1 PASSWORD=12345678
it works
after install you find the correct password in ultravnc.ini

[keith_andrews]

Ok, so don't include the SERVICE=1 with the other command parameters? I have been test deploying the newest version of UVNC on machines that have older working versions on them with public keys stored in the uvnc bvba\UltraVNC folder, and each time the machine is updated from UVNC 1.4.0.9 to 1.4.3.6 for example, it acts like it's a new install and it renders the remote desktop functionality inoperable. It also doesn't launch the settings window to enter a VNC authentication password like a new install would.

After the update I no longer see the server in the system tray, and the program is not running under Services. I am also no longer able to see the winvnc application to start the server. There's definitely something going on when upgrading a machine when using the .msi through Intune. It works fine if it's a new device, and there is no existing version of VNC installed, but if it's updating, then it causes some major issues.

I checked the VNC folder in Program Files and it's missing the apps and public key after the upgrade:



The only way to fix the issue that occurs after an upgrade is to uninstall and reinstall the .msi manually.

[Rudi De Vos]

That are other test parameters....
Need to check it.