End-of-Year Sale: Save Up to 70%!
Offer ends is:
A Windows Server 2016 Client Access License gives a user or device the legal right to access services provided by a licensed Windows Server 2016 installation. The main server licence covers the operating system itself, while CALs cover the people or computers connecting to shared resources.
Businesses may require these access licences when employees use Active Directory, shared folders, network printers, internal applications, authentication services, or other workloads hosted on Windows Server 2016. Selecting the correct CAL model helps organisations maintain clear licensing records and align access rights with everyday working practices.
This category includes the Microsoft Windows Server 2016 User CAL and the Microsoft Windows Server 2016 Device CAL. Before ordering, confirm how many users and devices access the server and determine which assignment model offers the most practical coverage.
A CAL is an access right rather than a software application. It does not install Windows Server, activate the operating system, or add additional server features. Instead, it authorises a named user or a specific device to connect to a properly licensed server environment.
Windows Server 2016 CALs may be required when users or devices access:
The exact licensing requirement depends on how the organisation uses its infrastructure. Businesses should review all employees, contractors, computers, laptops, terminals, and other devices that connect directly or indirectly to Windows Server services.
A User CAL is assigned to one named individual. That person can access the licensed server from multiple devices, including a desktop computer, laptop, tablet, or remote workstation.
This option is generally suitable when employees regularly switch between devices or work from different locations. It can also be more efficient when the organisation has fewer users than connected computers.
A Device CAL is assigned to one shared workstation. Multiple authorised users can access the server from that licensed device, making this option useful for workplaces where employees use the same computer during different shifts.
Device-based licensing is commonly used in warehouses, schools, manufacturing environments, reception areas, healthcare facilities, and other workplaces where several employees use the same terminal.
Yes. Organisations can use both User and Device CALs within the same server environment when this reflects their actual access requirements. For example, office employees who use laptops and home computers may be assigned User CALs, while shared warehouse terminals may be covered by Device CALs.
A mixed approach can reduce unnecessary licensing, but assignments should remain clear and properly documented. Every user or device accessing the server must still be covered by the appropriate licence.
Windows Server CALs follow version-based licensing rules. A Windows Server 2016 CAL is intended for access to Windows Server 2016 and may generally provide access rights to eligible earlier server versions. However, it does not normally cover access to newer releases such as Windows Server 2019, 2022, or 2025.
If your organisation plans to upgrade its infrastructure, you will generally need CALs that correspond to the newer server generation. For example, moving to Windows Server 2019 requires compatible access licences rather than continued use of Windows Server 2016 CALs.
Businesses planning a broader modernisation project can also compare Windows Server 2022 or Windows Server 2025. Always confirm the installed server version before selecting CALs.
Windows Server 2016 User and Device CALs are generally suitable for both Standard and Datacenter editions of the same server generation. The distinction between Standard and Datacenter mainly concerns virtualisation rights, advanced features, and deployment capacity rather than the basic CAL model.
The server operating system must still have its own valid licence. A CAL cannot install or activate Windows Server 2016, and it does not increase the number of permitted server installations or virtual machines.
A standard Windows Server 2016 CAL does not automatically include Remote Desktop Services rights. If users access hosted desktops, RemoteApp applications, or multi-user remote sessions, separate RDS CALs may also be required.
In a Remote Desktop environment, a connecting user or device may require both a standard Windows Server CAL and a compatible RDS CAL. These licences provide different rights and should not be treated as alternatives to one another.
For a Windows Server 2016 remote access deployment, review the available Windows Server RDS 2016 options. Organisations upgrading their remote infrastructure may instead require newer RDS licensing.
An OEM licence is generally supplied with a particular computer or server. It is commonly linked to the original hardware and may have limited transfer rights if that hardware is replaced.
A Retail licence is supplied separately from the hardware and normally includes standalone purchasing documentation. Its use remains subject to the applicable Microsoft licensing terms and the conditions attached to the specific product.
OEM and Retail describe how a licence is supplied. They are different from User and Device CALs, which determine whether the server access right is assigned to a person or a computer.
Standard Windows Server 2016 CALs are generally access rights rather than installed software. Therefore, they are not normally installed or activated individually on every employee computer.
A practical licence management process includes:
RDS CALs are managed differently because they may need to be installed and configured through Remote Desktop Licensing Manager. Standard Windows Server CAL records should still be retained even when no key is entered directly into the server.
A Windows Server 2016 CAL only covers access to Windows Server. It does not automatically provide access rights for other Microsoft server products used within the same network.
For example, an organisation running Microsoft SQL Server 2022 may also require separate SQL Server licences or SQL Server CALs, depending on whether the deployment uses per-core licensing or the server-plus-CAL model.
Each server product should be assessed independently to ensure that users, devices, processors, and workloads are licensed correctly.
Digital License provides clear server licensing options for organisations maintaining Windows Server 2016 infrastructure. Detailed product information helps customers compare User and Device CALs and select the model that fits their working environment.
Digital License is a Microsoft Partner, providing customers with an additional point of trust when purchasing Microsoft-related software products. Microsoft Partner ID : 7033487
Before placing an order, verify the installed server version, calculate the required number of licences, and choose the CAL model that matches how employees and devices connect. Careful planning can simplify licence management, support compliance, and prevent unsuitable purchases.
Yes. The same Windows Server 2016 User or Device CALs generally apply to both Standard and Datacenter editions. The server edition licence is separate from the CALs required for users or devices accessing it.
Yes. Users or devices accessing file shares, network printers, Active Directory, or other Windows Server 2016 services generally need the appropriate CAL. The correct quantity depends on whether licensing is assigned per user or per device.
Yes. One User CAL can cover a named employee accessing the server from multiple devices, including an office computer, laptop, and home workstation. It does not cover other employees using those devices.
No. Windows Server 2016 CALs do not normally provide access rights to Windows Server 2019 or later versions. Upgrading the server generally requires CALs that match or exceed the newer server version.
Yes, when users or devices connect through Remote Desktop Services. A standard Windows Server CAL covers general server access, while an RDS CAL provides the additional right to use remote desktop sessions.
Maintain a compliant server access structure by selecting the Microsoft Windows Server 2016 User CAL
for employees working across several devices or the Microsoft Windows Server 2016 Device CAL for shared
workstations. Organisations planning an infrastructure upgrade can compare Windows Server 2019,
Windows Server 2022, and Windows Server 2025, while remote desktop or database deployments may
also require suitable RDS or Microsoft SQL Server 2022 licensing.
Customise your consent preferences for Cookie Categories and advertising tracking preferences for Purposes & Features and Vendors below. You can give granular consent for each Third Party Vendor and Google Ad Tech Provider. Most vendors require explicit consent for personal data processing, while some rely on legitimate interest. However, you have the right to object to their use of legitimate interest. Additionally, please note that your preferences regarding purposes and vendors are saved in a cookie named 'euconsent' on your device and may be retained for up to 730 days to remember your choices.
Necessary cookies are required to enable the basic features of this site, such as providing secure log-in or adjusting your consent preferences. These cookies do not store any personally identifiable data.
Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics such as the number of visitors, bounce rate, traffic source, etc.
Advertisement cookies are used to provide visitors with customised advertisements based on the pages you visited previously and to analyse the effectiveness of the ad campaigns.
Functional cookies help perform certain functionalities like remembering your preferences and customising your experience on the website.
This section lists the purposes for which partners process your data and the features they use. You can object to the use of legitimate interests.
This section lists third-party vendors that may process your data. You can review and manage consent for each vendor individually.
