Deploy the Solstice App with MSI

The MSI installer package of the Solstice App allows for a GUI-based installation on a local machine or GPO deployment in Active Directory. This allows your IT administrator to centrally deploy the Solstice App for users on a Windows machine, and can be set to install silently. The installer requires admin privileges to install system-wide. This makes it easier to use the MSI in a remote deployment where either an administrator or the SYSTEM account can install this properly. The MSI installer can be run interactively, specifying options through the GUI, or silently, specifying installation parameters directly on the command line making it easier automate deployment.

Important Note: If Solstice Conference capabilities have been previously installed from an earlier version of the Solstice client (5.2.1 or earlier), admins centrally upgrading the client to version 5.3 via MSI, or uninstalling the previous version of the client via MSI, will first need to remotely reboot the user machine. Admins will then need to add a command line option AFTERBOOT=1 to their MSI command line and resubmit the MSI upgrade or uninstall command. If Solstice Conference capabilities were not previously installed, admins can upgrade or uninstall as normal with no reboots required.

Here are the current values that can be set during installation:

The Mersive MSI installer is case sensitive. Installation options must be specified in capital letters.

INSTALLDIR= controls where the client will be installed. The default is: “C:\Program Files (x86)\Mersive Technologies, Inc\Solstice\Client”.

STARTONLOGIN={ 0 | 1 } controls whether the client will auto launch when a user logs in. A value of 1 means it will start automatically, 0 means it will not.

HIDEUIWHENSHARING={ 0 | 1 } controls whether the client User Interface (UI) is hidden when the desktop is being shared. This is a convenient shortcut so it doesn’t get in the way of your sharing. A value of 1 means it will automatically hide, 0 means it will not. Note: The string “HIDEUIWHENSHARING” must be written in capital letters.

SDSADDRESS= where can be a domain name (e.g. x.y.z) or an IP address (1.2.3.4). This controls the initial setting of the Solstice Discovery Service (SDS) address for the client. If this parameter is not given, the client’s SDS Address will not be modified.

NAME=”user name with spaces”will let the user specify the client’s user name at install time. If the user name has spaces, it will need to be surrounded by quotes.

DEFAULTNAME={ 0 | 1 } will set the client’s user name to be the machine name the client was installed on. And if both of them are given, the user name will be the machine name (DEFAULTNAME wins out).

AUTOSHAREAUDIO={ 0 | 1 } will set whether desktop audio is automatically shared when the user's desktop is shared.

ADDCONFERENCE={ 0 | 1 } will determine whether the Solstice Conference drivers are installed at installation time.

STARTDOCKED={ 0 | 1 } will determine whether the client starts in docked mode or not.

ADDSHORTCUT={ 0 | 1 } will determine if an icon for the Solstice client is added to the user's desktop.

ADDCONFERENCE={ 0 | 1 } will determine if the lightweight drivers required for Solstice app users to utilize Solstice Conference capabilities are automatically installed. This allows administrators to deploy Solstice Conference capabilities in case end-users do not have the elevated permissions needed to install.

HIDECONFERENCE={ 0 | 1 } will hide the Solstice Conference capability in the Solstice app from end-users.

HIDESETTINGS={ 0 | 1 }will hide the settings options and configurations from end-users.

The client-specific data that was stored in each user’s home directory (e.g. c:\programdata\Mersive\<username>) will now be stored under a central shared location (e.g. C:\ProgramData\Mersive\ALLUSERS\Solstice\Client).This allows for centralized management of these settings and the ability to update them for all users at installation time.

Examples

Related Topics

Deploy the Solstice App with SCCM