Skip to main content

Understanding SPLA RDS SAL counting logic

  • Updated

Overview

Under the SPLA agreement, the RDS SALs are counted based on potential access to the Windows server environment.

Key points

  1. RDS SALs Are Based on Potential Access

    • An RDS SAL is required for each user who has the technical capability to access Windows servers over Remote Desktop Protocol (RDP), Remote Desktop Services (RDS), or third-party products like Citrix.

    • This is determined by potential access, regardless of the number of deployed RDS Client Access Licenses (CALs) or concurrent connections.

  2. Counting RDS SALs

    • To determine the correct RDS SAL count:

      • Identify which servers in your environment fall under the SPLA license scope.
      • Scan these servers to detect all users who can potentially access them.
    • The count includes all users with the capability to access any Windows server in the environment, even if the server does not have a Terminal Server (TS) or RDS role.
  3. User-Based Licensing
    • RDS SALs are user-based, meaning every user with potential access must be counted, regardless of actual use or duration.
    • Example: If 100 users can access the environment at any point in the month, 100 RDS SALs are required.
  4. Impact of RDS CALs and Concurrent Access
    • The number of RDS CALs or concurrent users does not affect the RDS SAL count. Only potential access determines the requirement.
    • Example: If 1,000 RDS CALs are deployed but 5,000 users can potentially access the servers, 5,000 RDS SALs are required.

Conclusion

To comply with SPLA RDS SAL licensing, count all users with potential access to the Windows server environment, irrespective of actual use or concurrent connections.

Related articles