Splashtop Streamer can be silently installed with command line parameters.
Windows
Notice: Supported by Splashtop Streamer 3.3.6.0 or higher.
New install using EXE:
streamer.exe prevercheck /s /i sc=gateway_address:port,dcode=your_code,confirm_d=0,ignoressl=1,hidewindow=1
Upgrade using EXE:
streamer.exe prevercheck /s /i hidewindow=1
- Replace "streamer.exe" with the actual file name of your streamer installer.
- Replace "gateway_address:port" with your own gateway's IP/FQDN:Port
- Replace "your_code" with your own 12-digit deployment code.
Note that there is no space after each comma.
EXE parameters:
- prevercheck: (required)
- /s: Silent installation. Bypass InstallShield prompts.
- /i: Run in command-line mode (required).
- sc=gateway_address:port: the Gateway's IP/FQDN:Port, if Port is 443, it can be ignored
- dcode=your_code: Inject the 12-digit deployment code to automatically associate the Streamer with pre-defined Splashtop group and settings.
- confirm_d=0: Do not show the confirmation prompt when injecting deployment code.
- ignoressl=1: Do not prompt SSL warning if the Gateway has no trusted SSL cert
- 0: Force SSL check
- 1: Ignore SSL check
- hidewindow=1: Do not show the Streamer window after installation.
- sec_opt=number: Security option. (Note: the deployment code config overrides this parameter)
- 0: No additional password
- 1: Require security code
- 2: Require Windows login on
- sec_code=your_security_code: Choose the security code to use (no space or special symbols allowed).
Create a custom configured MSI for GPO deployment:
For easier deployment via Group Policy (GPO), you can create a custom configured MSI to include several settings, such as the deployment code. Here are step-by-step instructions:
Custom MSI with Orca.
New install using MSI:
msiexec /norestart /qn /i streamer.msi USERINFO="sc=gateway_address:port,dcode=your_code,hidewindow=1,confirm_d=0,ignoressl=1"
- Replace "streamer.msi" with the actual file name of your Streamer MSI installer.
- Replace "gateway_address:port" with your own gateway's IP/FQDN:Port
- Replace "your_code" with your own 12-digit deployment code.
Upgrade using MSI:
msiexec /norestart /qn /i streamer.msi REINSTALL=ALL REINSTALLMODE=vomus MSIENFORCEUPGRADECOMPONENTRULES=1 CA_UPGRADE=1 USERINFO="hidewindow=1"
- For upgrade, the streamer.msi file name has to be the same as the originally installed MSI file name. If the original install was with the EXE installer, then the file should be named "setup.msi".
- msiexec /norestart /qn /i setup.msi REINSTALL=ALL REINSTALLMODE=vomus MSIENFORCEUPGRADECOMPONENTRULES=1 CA_UPGRADE=1 USERINFO="hidewindow=1"
- Note: If you are running the command from a CMD window, the CMD window must be running with admin rights.
Note that there is no space after the comma.
MSI parameters:
- /qn: Silent installation.
- /i: Run in command-line mode (required).
- hidewindow=1: Do not show the Streamer window after installation.
- sc=gateway_address:port: the Gateway's IP/FQDN:Port, if Port is 443, it can be ignored
- dcode=your_code: Inject the 12-digit deployment code to automatically associate the Streamer with pre-defined Splashtop group and settings.
- sec_opt=number: Security option
- 0: No additional password
- 1: Require security code
- 2: Require Windows login on
- ignoressl=1: Do not prompt SSL warning if the Gateway has no trusted SSL cert
- 0: Force SSL check
- 1: Ignore SSL check
- sec_code=your_security_code: Choose the security code to use (no space or special symbols allowed).
- confirm_d=0: Do not show the confirmation prompt when injecting deployment code.
Silent uninstall:
streamer.exe msiexec /qn /x setup.msi
This uninstallation command works for both EXE and MSI installations.
Mac OS X
Notice: Supported by Splashtop Streamer 3.3.2.0 or higher.
sudo ./deploy_splashtop_streamer_op.sh -i streamer.dmg -z "gateway_address:port" -d your_code -w 0 -s 0 -q 1 -n "my_computer1"
- Replace with the appropriate installer image file name and your own 12-digit code.
- Download the script file deploy_splashtop_streamer.sh.zip below (uploaded 2021/09/29).
- Please uninstall already deployed Streamers by running Uninstall Splashtop Streamer.sh or uninstall app find inside the streamer.dmg before using the script to make sure there was no previous setting interference.
Parameters:
- -z "gateway_address:port": the Gateway's IP/FQDN:Port, if Port is 443, it can be ignored
- -d your_code: Inject the 12-digit deployment code to automatically associate the Streamer with pre-defined Splashtop group and settings.
- -w 0: Do not show the confirmation prompt when injecting deployment code.
- -s 0: Do not show the Streamer window after installation.
- -q 1: Do not prompt SSL warning if the Gateway has no trusted SSL cert (0 Force SSL check; 1 Ignore SSL check)
- -n "Computer_name": computer name.
Example:
Installation
sudo ./deploy_splashtop_streamer_op.sh -i streamer.dmg -z "ste_server:443" -d 123456789XXX -w 0 -s 0 -q 1 -n "my_computer1"
Upgrade
sudo ./deploy_splashtop_streamer_op.sh -i streamer.dmg -w 0 -s 0
Silent Uninstall Mac Streamer
1. Extract Uninstall Splashtop Streamer.sh from your Streamer_v3.x.x.x.dmg - Uninstall Splashtop Streamer.app/Contents/Resources
2. Locate the script path and execute with below command in Terminal:
sudo ./'Uninstall Splashtop Streamer.sh'
Comments
Installing Soundflower driver will hang if the Mac has no users logged in at the time of deployment
Is this a system limitation, or could it be fixed on your side?
Hi Witold,
We have fixed this limitation of Soundflower driver. The article and attached script file are both updated. Welcome to try it out.
Installation works good. Now option for silent Streamer uninstall on macOS would be nice... :)
Hi Witold,
Please download the uninstall Mac Streamer script and run the command in the last section of the article.
Once again - blazing fast. Thank you. 🙂
When running the script I'm getting this message.
The command I'm using (sanitized for posting) is...
The script continues but without the On-Premise backend address or deployment code.
And fixed... I shouldn't have added "https://" to the FQDN. Sad trombone noises. :-)
Installation script needs an update for M1 Macs. It does not install sound driver (looking at the source it just tries to install old kext sound driver instead of a new audio plugin).
Hi Witold, the script should work for M1 as well, but to install M1 sound driver 2 of the followings are needed. 1.) The .dmg to be used should be above v3.4.4.x, better to use the latest v3.5.0.5 version. 2.) If the kext was already installed on a Mac, an uninstall scripts + deploy scripts should work.
My mistake, it does not concern M1. The current script does not install plugin sound driver at all (no matter the architecture) if it is included in another .pkg and is launched by installer process (as we do to deploy Streamers using JAMF or Munkitools) when a user is logged in. It does not pass $USER == "root" check in line 783, I had to remove it (I see no reason for it to be there). There are additional "silent" errors in installPluginSoundDriver function - lines 445 and 449 have '==' instead of '=' operator.
And the uninstaller script does not remove plugin audio driver, only the kext one... :-)
1.） $USER == "root" is required to be here contextually, we are sorry for the inconvenience. 2.) Uninstall script would get modifed based on each release version, please find the latest inside .dmg, which will remove the plugin audio driver. Details in the last section of the above article. 3.) Deploy script has been updated accordingly, thank you!
Please sign in to leave a comment.