< Back
You are here:

It is possible to set up NetSupport Notify to work across multiple sites. The method you chose to perform this will depend on the connectivity between the sites. Some common examples of how this can be achieved are below:

Multi-site environments with WAN connectivity
If you have a multi-site environment with each remote site connected across a WAN, there are different options on how to implement NetSupport Notify. For example, if you have a central site, you can install and host a central NetSupport Notification Server at this location. A single Notification Server is designed to support up to 10,000 Notify Agents.

Once the central Notification Server has been installed and configured, you can then deploy the Notification Agents to your devices located across the different sites using your chosen deployment method. The Agent deployment can be pre-configured with an Agent configuration to connect the Agent to the central Notification Server. To differentiate between which Agents are located at which site when sending notifications, you can assign a department value to the Agents as part of the deployment or enforce it via AD Group policy using the Notify AD Template files.

The Notification Console can also be deployed and configured to connect to the central Notification Server, allowing the Console to send notifications to the Agents located across the different sites. If you want to control access to which sites the Console user can send notifications to, you can set up Console Operator access on the Notification Server and configure which Agent departments the Operator can target notifications to.

You need to ensure the port that the NetSupport Notify Server is configured to use is accessible to both the Agents and Console across the WAN. By default, the Notification Server listens on port 443. Please note this port is configurable via the Notification Server configuration.

Another option for this environment is to set up a Notification Server at each of the different sites. The Agents located at each site can then be configured to point to the Notification Server located on their local site.

The Notification Console can still be configured to access multiple Notification Servers, ensuring it is still possible to send a notification to Agents connected across different sites/Notifications Servers. Alternatively, to help control access to how you can send notifications to each site, you can pre-configure via the AD Template files for Notify, which Consoles will see which Notification Server, allowing you to control the sites they can deliver notifications to.

Multi-site environments without WAN or VPN connectivity between sites
If your multi-site environment does not have WAN or VPN connectivity between sites or if you have Agent devices located off-site and working from home, it is still possible to deliver notifications using NetSupport Notify.

To do this, your NetSupport Notification Server needs to be externally visible. Once the Notification Server is externally visible, Notify Consoles and Agents will continue to connect to the Notification Server to send and receive notifications.

A port forwarding rule is needed for the Notification Server to point requests from external Notify Agents and Consoles to the internal address and port of the Notification Server. The remote Agents can then be configured to connect to this using the external address or DNS name, configured port and Gateway key to permit them to connect.

Access to send notifications via the Notification Server can also be restricted to certain users using the Notification Server’s Operator feature.

For further details on implementing one of the above methods in your environment, please contact our Support team.

Was this article helpful?
5 out Of 5 Stars

1 rating

5 Stars 100%
4 Stars 0%
3 Stars 0%
2 Stars 0%
1 Stars 0%
How can we improve this article?
Please submit the reason for your vote so that we can improve the article.
Need help?