Choosing local or network licensing (Windows)

On Windows, product keys may be installed locally (stand-alone) or on a network (shared) machine. On a new system, local or network licensing is specified during installation. On a system that previously had Synergy/DE installed, licensing will default to the configuration of the previous installation, but it can be changed after installation. See Modifying license configurations (Windows).

Local licensing

Local licensing (also referred to as stand-alone licensing) uses License Manager server to manage licenses on a single machine. You can configure local licensing on any Windows system. Each system with local licensing requires its own product keys, which include a single user license for each Synergy/DE product that will be run on that system.

Network licensing

Network licensing uses License Manager server to manage licenses for one or more license clients. You can configure network server licensing on any Windows machine to manage license clients in a local area network (LAN).

With network licensing, product keys are installed only on the license server machine. On the license clients, all you need to do is specify the name of the license server during installation. Synergy/DE applications running on the license client take their licenses from the license server; therefore, the license server must have the necessary licensing in place before you can run applications on the clients.


If your license server will connect to pre-version 10 clients, be aware that the permitted length for the license server name was changed in version 10. The current limit is 63 characters, but prior to version 10, it was 15 characters. Because you must specify the license server name on the license clients, it is effectively limited to 15 characters when you have pre-version 10 clients.

There are two scenarios in which you must use network licensing:

To improve the resiliency of network licensing, you can add a backup license server, which will take over the task of serving licenses should the primary server fail. See Configuring a backup license server (Windows).


Users accessing an application via remote desktop software or a terminal server session are licensed using the license settings on the terminal server machine. There is no licensing setup required on the remote client device.



For Synergy .NET applications (including those using ClickOnce deployment) that are deployed to systems where Synergy licensing is not installed, you must specify a license server name in the App.Config file. For details, see Runtime Settings page of Visual Studio project properties (Synergy .NET).