Updating Solstice to the Latest Version

There are several components of the Solstice product suite that should 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.

If using the Solstice Dashboard, you must first upgrade your Dashboard before you upgrade your Pods and/or Windows Display Software licenses. To upgrade your Solstice Dashboard, download and install the latest version from our downloads page, where you can also access the latest versions of the Solstice Apps and Solstice Discovery Service (SDS).

Access to Solstice Software Updates

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 will retry and resume 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 will reach out to the Mersive web server to access software updates. Once Pods are imported into Solstice Cloud from Solstice Dashboard, you can log in to Solstice Cloud (https://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 will 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) – This method should only be used 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 will send SLR updates via port 443.

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.

How To