Solstice, whether running on a Pod or a Windows host, can be successfully deployed on complex networks with rigorous security standards. In this Solstice Deployment Overview video we dive into how to deploy Solstice on your network.
A Solstice Pod may be deployed as a standalone WAP, on either a wired or wireless network, or on both a wired and wireless network simultaneously. Dual-network mode is made possible by the Pod’s two distinct network cards. These cards use separate routing tables, maintaining security between the two networks. This mode is commonly used to allow users on two different networks to collaborate, such as employees on a main enterprise network and guests on a guest WiFi network. If a Pod is deployed on both networks, the two parties may have a fully collaborative session on a shared, Solstice-enabled display without compromising the integrity of either network.
While broadcast mode is the easiest way to enable click-to-connect functionality for Solstice end users, we recognize that many large networks do not permit broadcast traffic. The Solstice Discovery Service (SDS) is an IT-friendly, non-broadcast mechanism that an administrator can set up to let end users click on a display’s name in their free app to connect rather than be required to enter an IP address before every collaboration session. An SDS record can even be added to a network’s DNS to prevent users from having to enter an IP address even the first time they interact with a Solstice display on your network. For more information, see ‘configuring an SDS routing override’.
In this video, we will cover:
- Attaching Solstice host(s) to the network
- Opening required ports (see full port diagram here).
- Configuring user and network security
- Setting up display discovery
- Validating the deployment is operational
For more detail, see our complete Network Deployment Guide.
Share this Post