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 a 5.3 or 5.3.1 version of the Solstice client, admins centrally upgrading the client to version 5.3.2 via MSI will first need to remotely reboot the user machine then uninstall the previous version of the client via MSI before upgrading to 5.3.2. Admins can use the following command lines for uninstalling the 5.3 or 5.3.1 versions of the client:

5.3:
msiexec /x “{8cca01d5-9b6f-4474-9409-d5a586c3c2e7}” AFTERBOOT=1 /quiet

5.3.1:
msiexec /x “{b4efba4f-8b7f-42e4-a991-c779da1bff58}” AFTERBOOT=1 /quiet

After running the uninstall command, admins can then install the 5.3.2 client via MSI as normal. If Solstice Conference capabilities were not previously installed, admins can upgrade or uninstall as normal.

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

When you install a new version of the 64-bit client, the installer first removes any previously installed version of the 64-bit client. However, the 64-bit client installer does not remove a 32-bit version of the client. Mersive recommends that you uninstall any 32-bit Solstice clients before installing 64-bit clients.

Here is an example of how to use msiexec to install the Solstice client with the following options:

  • Set the SDS address to sdshost.yourcompany.com
  • Install the client in the directory C:\Program Files\Mersive\SolsticeClient
  • Not start the client on login
  • Hide the user interface when sharing the desktop
  • Install the client silently
  • Write an installation log file named C:\SolsticeClient.log

msiexec /i SolsticeClient-5.3.msi SDSADDRESS=192.168.2.129 INSTALLDIR="C:\Program Files\Mersive\SolsticeClient" STARTONLOGIN=0 HIDEUIWHENSHARING=1 /quiet /log c:\SolsticeClient.log

Typically, silent installs do not require any user interaction during the installation process. However, when installing the Solstice Conference drivers bundled into the client, there is a confirmation screen that requires the user to explicitly trust the software from Mersive. In order to eliminate this confirmation step, you will need to pre-install the Mersive trust certificate on the machine where the client is being installed. Below are steps to accomplish this locally on a single machine.

If you are deploying centrally to multiple PCs, you can use Microsoft’s Group Policy or another 3rd party tool to add the Mersive publisher certificate to the Trusted Publishers certificate store.

  1. From a computer that does not have the Solstice Conference feature of the Solstice Client installed, run SolsticeClient-5.3.msi. (If you are working with a computer that already has this feature installed, skip to step 5.)
  2. Work through the installation wizard, and select the Install Solstice Conference checkbox.

  3. Continue the installation wizard.

    When the installation starts, you will be prompted to trust Mersive software.

  4. Select the Always trust software from "Mersive Technologies, Inc." check box, and click Install.

    The Mersive trust certificate is installed on the computer.

  5. On the Windows start menu, enter certmgr.msc
  6. From the certmgr dialog, navigate to Trusted Publishers > Certificates.
  7. Right click the Mersive certificate and select All Tasks > Export.
  8. Click Next, and then click Next again.
  9. Enter the file name for the Mersive certificate. For example, you could enter mersive_cert.cer. You can also use the Browse dialog to specify both the name and the location of the file.
  10. Click Next, and then click Finish.
  11. Place the SolsticeClient-5.3.msi file and the trust certificate you just exported, into the same folder or on the same share where they can used for installation.
  12. On the Windows computer where you want to perform the silent install, open a command prompt with Administrator permissions.
  13. Install the certificate by entering certutil -addstore "TrustedPublisher" <certificate name>.
  14. Using msiexec run SolsticeClient-5.3.msi with the "quiet" (or silent) option.

For example, to run both certutil and msiexec from the same command, you could enter:

certutil -addstore "TrustedPublisher" mersive_cert.cer && msiexec /i SolsticeClient-5.3.msi SDSADDRESS=192.168.2.129 INSTALLDIR="C:\Program Files\Mersive\SolsticeClient" STARTONLOGIN=0 HIDEUIWHENSHARING=1 ADDCONFERENCE=1 /quiet /log c:\SolsticeClient.log

Here is an example command showing how to use msiexec to uninstall the Solstice client.

msiexec /x SolsticeClient32-5.3.msi /quiet /log c:\SolsticeClient.log

Related Topics

Deploy the Solstice App with SCCM