Licensing Model

Workspace Control offers two license types: Named User licenses and Concurrent User licenses. Which license type, or combination of licenses you need, very much depends on the number of users, Workspaces and devices in your environment. Concurrent licensing is mainly used in Virtual Desktop environments, and named licensing for mobile workers (laptops). For example, when a user works on a laptop and connects to a Virtual Desktop, a named user license suffices to work with Workspace Control on both, as the license is associated to the user name.

Licensing information is stored in the Datastore and cached locally on Agents. If, according to the local cache, licenses are available for the session, the session is allowed. If, according to the local cache, no licenses are available, the Workspace Control licensing policy is applied.

Licenses are pooled per environment and are claimed by Workspace Control Agents according to the rules outlined below.

In the context of Workspace Control environments, machines (computers, laptops etc.) are considered online if the Workspace Control Agent running on them is connected to Relay Servers or to the Datastore. Machines go offline when they are not connected to Relay Servers or to the Datastore.

Named User licenses

When using named user licenses only, the following applies:

  • Workspace Control claims a named user license for each user upon first session connect. Once the license is claimed, the user can use any type of client (terminal server, desktop or laptop) with the assigned user account.

  • A license is claimed for 45 days. The license claim is renewed at every new session connect.

  • On a laptop, the claimed named license is cached locally. When the laptop goes offline (the Workspace Control Agent is not connected to a Relay Server or to the Datastore), it is not possible for remote users to start Workspace Control sessions until the laptop goes online again. The local user of the laptop can still start Workspace Control session until the license expires, regardless if the laptop is offline or online.

  • Every time a Workspace Control session starts, the Workspace Control Agent running on that machine renews the license claim when connecting to a Relay Server or to the Datastore. If the machine goes offline, then the Workspace Control Agent cannot renew the license claim.

  • The machine must go online before the 45 day claim period expires and allow the Workspace Control Agent to renew the license claim. Otherwise, the local user cannot start Workspace Control sessions unless the If no license is available at logon option is set to Continue with reminder for 45 days. With this option enabled, the claim period can be extended to 90 days. For more details, see Licensing.

Concurrent licenses

When using Concurrent licenses only, the following applies:

  • Workspace Control claims a concurrent license for each active workspace (regardless of user name, client name or computer name).
  • Each laptop claims a seat, regardless of user sessions or Datastore connection state. A license claimed by a laptop will remain claimed whether anyone uses the laptop or not.

Combining Named User licenses and Concurrent licenses

Concurrent user licenses and named user licenses can be used together.

When using Concurrent licenses and Named Licenses together, the following applies:

  • Workspace Control will use a named user license if it has already been claimed or reserved for the user who is logging on.
  • If no license is claimed/reserved, Workspace Control checks whether the current device is a laptop.
    • For laptops, Workspace Control claims a named user license by default. If none are available, the Workspace Control licensing policy is applied.
      • To claim concurrent licenses for laptops from a mixed license pool, during installation, set the public property CLAIMLAPTOPLICENSE to "yes". See (Parameters for) Unattended installation for more information.
    • For other types of devices, Workspace Control claims a concurrent license. If none are available, it will claim a named user license. If no license can be claimed, the Workspace Control licensing policy is applied.

Special scenarios

  • If you use more than one Workspace Control module (Composition, Governance, Security), you can still mix concurrent and named user licenses. However, for each license type you need the same number of licenses per module. For more information see Select Workspace Control Modules.
  • If you use several published applications, you only need a license for the first session originating from the same client - even if the sessions run on different servers and the client has no composer running. Prerequisite is that all sessions run using the same database.
  • If the originating client uses a local composer, it already has a license in use - any subsequent remote session will not require a license, even if different databases are used.

Named or Concurrent?

The following examples illustrate several environments with their most advantageous license types:

Laptops

Case

Why?
  • 1000 users: 800 laptops, 200 desktops
  • 1000 Named licenses

Users are bound to a device, so Named is cheaper.

Desktops

Case

Why?
  • 1000 users: 600 desktops
  • 600 Concurrent licenses

Fewer Workspaces than users, so Concurrent is cheaper.

Remote Desktop Services

Case

Why?
  • 2000 users: 1200 Workspaces at a time
  • 1200 Concurrent licenses

Fewer Workspaces than users, so Concurrent is cheaper.

Remote Desktop Services and Laptops (1)

Case

Why?
  • 800 users: 800 laptops offline, that use Remote Desktop Services in the office
  • 800 Named licenses

Users are bound to a device, so Named is cheaper.

Remote Desktop Services and Laptops (2)

Case

Why?
  • 1200 users: 400 laptops, 800 Workspaces
  • 400 Named licenses + 400 Concurrent licenses

Different kinds of usage. Mobile workers that use Remote Desktop Services in the office are better off with Named, but the other 400 active sessions are better off with Concurrent.
Reserve Named User licenses for laptop users!