System Settings
Yoou can set various system preferences for your Solstice display, including the timezone or the language settings.
How To
Configure the date and time settings on Solstice Pods to show the correct date and time on Solstice displays. Windows Display Software instances of Solstice inherit the time settings on the Windows computer the software is installed on.
In Solstice Dashboard, select Pods from the list of Your Solstice Instances.
Go to the System tab.
To set the date and time using a time server:
Enable Set Time/Date Automatically and enter the time server URL in the corresponding field (default timeserver URL is pool.ntp.org).
Select the Timezone the Pod is in.
Click Apply.
Tip
Check that Solstice displays have a good connection to the configured network time server. Network issues that prevent the Solstice from reliably reaching the time server may cause minor issues such as the screen key displaying randomly.
To set the date and time manually:
Uncheck Set Time/Date Automatically.
In the message that appears, click Ignore, Keep Manual Time Setting.
In Date and Time, enter or select the date and time to use for the Pod.
Select the Timezone the Pod is in.
Click Apply.
Administrators can change the hostname by which the Solstice Pod identifies itself to the local network, including in LLDP reporting and for security certificates.
In Solstice Dashboard, select a Solstice Pod from the list of Your Solstice Instances.
Go to the System tab > System section. The default hostname for the Solstice Pod appears in the Hostname field.
Enter the unique hostname you want the Pod to use to identify itself on the network.
Note
Hostnames for Solstice Pods can be up to 32 characters long. They must start with a letter, end with a number or letter, and can contain uppercase and lowercase English-language characters, as well as numbers and dashes.
Click Apply.
Click Apply Changes and Restart Display.
In Solstice Dashboard, select displays from the list of Your Solstice Instances.
Go to the System tab > System section.
Enter the unique hostname you want the Pod to use to identify itself on the network.
Note
Hostnames for Solstice Pods can be up to 32 characters long. They must start with a letter, end with a number or letter, and can contain uppercase and lowercase English-language characters, as well as numbers and dashes.
Click Apply.
Click Apply Changes and Restart Display.
In Solstice Dashboard, select Pods from the list of Your Solstice Instances.
Go to the System tab > Tools section.
Click the Reboot button.
Enable and schedule daily Pod software reboots to refresh the Pod’s memory usage and maximize system performance. If users are connected and sharing content to a Pod at the scheduled reboot time, that Pod's reboot is skipped until the next scheduled reboot time.
In Solstice Dashboard, select Pods from the list of Your Solstice Instances.
Go to the System tab > Tools section.
Select Schedule daily reboot.
In Reboot time of day, enter the time you want the Pod to reboot each day.
Note
Daily reboots will take place within 10 minutes after the selected time.
If you want the daily reboot to proceed when the Pod is receiving input from a connected HDMI device, such as a digital signage player, select Allow scheduled reboot with active HDMI input.
Click Apply.
When enabled, Solstice can use any USB camera attached to the back of a Pod to detect whether a meeting space is occupied. Occupancy data can then be used as a trigger for such actions as suspending and reactivating the Solstice display (see Display Power Management Settings for more details). This feature is disabled by default.
Note
Solstice version 5.X or higher is required for occupancy data collection.
Any USB camera can be used to detect occupancy, but Mersive recommends one of our supported USB cameras or videobarssupported USB cameras or videobarsvideobars for best results.
In Solstice Dashboard, select Pods from the list of Your Solstice Instances.
Go to the System tab.
In the Room Services section, select Occupancy Counting.
Click Apply.
Important
No video or audio data from an attached camera ever leaves the Solstice Pod. All processing occurs locally, and only aggregated occupancy data is sent to Solstice Cloud.
Note
The Solstice Location Service, used to estimated the approximate geographic location of Pods and auto-disconnect users, is deprecated. The Location Services setting remains in the Room Services section of the System tab in Solstice Dashboard, but it is disabled on Solstice Pods running Solstice 6 and later.