Other Solstice Software Updates
Several components of the Solstice product suite may need to be updated when a new software version is released. This guide for Solstice administrators provides an overview of how each component is updated, as well as step-by-step instructions for the various methods for updating Pods. A current Solstice Subscription is needed to access software updates.
Mersive strongly encourages administrators to update their Solstice Pod deployments using the tools in Solstice Cloud. However, a number of other possible methods for installing the latest Solstice software on your Pods are also described below.
Note
If using Solstice Dashboard to manage Solstice displays, you must first upgrade Dashboard before upgrading your Pods and/or Windows Display Software instances. To upgrade Solstice Dashboard, download and install the latest version from https://www.mersive.com/download-admin/, where you can also access the latest versions of the Solstice Apps and Solstice Discovery Service (SDS).
Access to Solstice Software Updates
Solstice Pods - There are several ways to update Pods. For more information about the various ways to update your Pods, see the Solstice Pod Update Options below.
Mersive Solstice user apps - Users are automatically reminded to download the newest version of the Mersive Solstice app when they connect to a Solstice display running a software version newer than the app. To install the latest version, you can access the all Solstice apps from the Solstice Download Center (for laptops) or from your mobile device’s app store.
Centrally deploy Mersive Solstice app using MSI or SCCM - The Mersive Solstice app for Windows can be centrally deployed via either MSI or SCCM. The MSI installer package allows for a GUI-based installation on a local machine or GPO deployment in Active Directory, while the SCCM installer package allows for a remote installation. These updates can be accessed at Solstice Download Center > Admin Downloads > Deployment Management. For more information on MSI and SCCM installations, see Deploy Solstice with MSI or SCCM.
Solstice Dashboard - If using Solstice Dashboard to manage your Solstice deployment, always update Dashboard first before updating your Pods. The latest version of the Dashboard is available at https://www.mersive.com/download-admin/.
Solstice Discovery Service (SDS) - The latest version of SDS is available at https://www.mersive.com/download-admin/. Click for more information on SDS.
Solstice Windows Display Software - Contact Mersive for the latest information about the Solstice Windows Display. Click for more information on Solstice Windows Display Software.
Solstice Pod Update Options Summary
The following are the available methods for updating Solstice Pods:
Standard Over-The-Air (OTA) Updates via Solstice Cloud - Recommended method for Enterprise Edition Pods. Administrators can choose to schedule over-the-air updates to begin at a later time, or can choose to start the update process immediately. Pods can be scheduled to update in batches, with an option to notify you when the scheduled update is complete. If internet connectivity is interrupted during the update process, Solstice Cloud retries and resumes the update where it left off. To use this method, Pods must be added to your Solstice Cloud account and have direct internet access, and the Mersive web server (https://www.mersive.com) must be allowed through your firewall. Pods reach out to the Mersive web server to access software updates. After Pods are imported into Solstice Cloud from Solstice Dashboard, you can log in to Solstice Cloud (cloud.mersive.com) to update the Pods. For more information, see Schedule Solstice Pod Updates Using Solstice Cloud.
Standard OTA Updates via Solstice Dashboard – The Pod’s default OTA (over the air) update method reaches out to the Mersive web server to access updates. To use this method, Pods must have direct internet access and the Mersive web server (https://www.mersive.com) must be allowed through your firewall. This method can be configured via Solstice Dashboard or a Pod’s local/web configuration panel.
OTA via Web Proxy – This method can be used when Pods have internet access via web proxy. Pods still receive OTA updates from the Mersive web server, but the Pod must have the proper web proxy settings configured to do so. This method is useful if the network requires Pods to be behind a firewall and can be configured via Solstice Dashboard or a Pod’s local/web configuration panel.
Local OTA – The Local OTA method can be used when Pods don’t have direct or web proxy-based access to the Mersive web server for updates. This method requires you to download the Solstice upgrade file, place it on a local web server, and configure Pods to point to that location for updates via the Solstice Dashboard. This is only available for Enterprise Edition Pods version 3.5 or later and can only be configured using Dashboard version 3.5 or later.
Solstice Local Release (SLR) – Use this method when Pods can’t receive OTA updates because they don't have access to the Mersive web server or a local web server for updates. This method uses a local file downloaded to the Solstice Dashboard machine for upgrades and is only available for Enterprise Edition Pods using the Dashboard. When network encryption is enabled, Solstice Dashboard sends SLR updates via port 443.
Note
When updating Solstice Pods to version 5.0, Pods may experiences slightly longer update times than normal. Please give Pods at least 8 minutes to fully update, and do not unplug or reboot your Pod during the update process.