Activating Windows Server 2016 50 Device CAL
The Windows Server 2016 50 Device CAL licence is a device-based licence assigned to devices that connect to the server. This means that the permission is granted to a specific device, regardless of the number of users using it. This solution is particularly useful in companies, schools, warehouses, and service points where several people work on a single computer.
In practice, it is worth remembering one important thing: Device CAL does not require installation or entering a key in the Windows Server system. It is not activated like the operating system itself. It is a licence that confirms the right to access server services for a specified number of devices. In the case of the 50 Device CAL package, this means the possibility of legal access for a maximum of 50 devices.
The article below explains how to properly deploy and verify such a licence, and what to pay attention to in case of any problems.
Step by Step
1. Determine the type of licence you have
Before you start, make sure that the licence you purchased is indeed Windows Server 2016 Device CAL, and not User CAL. The difference is significant:
- Device CAL is assigned to a device
- User CAL is assigned to a specific user
If multiple employees use the same computer in shifts, Device CAL is usually a better choice.
2. Verify the number of devices in the company
The 50 Device CAL package covers a maximum of 50 devices accessing the server. It's worth counting all computers, terminals, laptops, or other devices that connect to the server's resources, such as:
- shared folders
- network printers
- domain services
- applications running on the server
If the number of devices exceeds 50, it will be necessary to purchase additional access licences.
3. Keep the purchase document and licence details
Since CAL access does not require installation, the most important thing is to properly store the documents confirming the purchase. You should keep:
- the invoice or proof of purchase
- the product name
- the number of CALs purchased
- the email with licence confirmation, if it was delivered electronically
These documents are the basis for confirming the legality of licensing during an audit or internal control.
4. Assign licences to devices in internal documentation
Microsoft does not require a separate CAL installation on each computer, but the company should keep its own records. The simplest way is to prepare a list of devices to which the licence has been assigned. Such a list may include:
- computer name
- inventory number
- department or location
- date of licence assignment
This makes it easier to demonstrate that the number of actively using devices is within the limit of 50.
5. Ensure the server is running the correct version
Windows Server 2016 CAL licences are intended for a Windows Server 2016 environment. In everyday use, you need to ensure compatibility between the server version and the purchased access rights. This is especially important when expanding infrastructure or migrating from older system versions.
6. Inform the IT administrator
If the environment is managed by an IT specialist or an external IT company, it's worth passing on the information about the purchase and scope of the licence. The administrator should know that:
- the organisation uses the Device CAL model
- the limit is 50 devices
- the licence does not require technical activation
- control of the number of devices accessing the server is necessary
Verification
After purchasing, many clients look for a place in the system to "enable" or "activate" Device CAL. In the case of this type of licence, it's essential to understand that it does not appear as a separate program to install. There is also no standard activation procedure involving entering a key into Windows Server, if we're talking about regular CAL access licences.
To verify that everything is properly prepared:
- confirm that the server is Windows Server 2016
- check that the number of devices with access does not exceed 50
- ensure that the purchase document is kept
- keep a simple record of devices covered by the licence
If these conditions are met, it means that licensing has been implemented correctly from a formal point of view.
If you have any further questions or concerns, please do not hesitate to contact us at [email protected] or call us on 00 800 121 1654.
Problems
The most common problem is the assumption that Device CAL needs to be installed like an application or activated with a command in the system. This is a mistaken approach. CAL is a right to use the server, not a separate installation component.
Another common difficulty is confusing Device CAL with User CAL. If a company has purchased device licenses, but in practice wants to license users working on multiple computers, this may mean a wrong choice of licensing model.
Lack of documentation is also a problem. Even if a company has legally purchased licenses, the lack of an invoice or an internal list of devices makes it difficult to later demonstrate compliance.
It is also worth paying attention to the expansion of infrastructure. If more than 50 devices start connecting to the server, the current package will no longer be sufficient. In such a situation, it is necessary to extend the licensing with additional CALs.
In case of doubts regarding license compliance, selection of the appropriate type of CAL, or purchase documents, you can contact us at: [email protected] or call us at 00 800 121 1654.
FAQ
Does Windows Server 2016 50 Device CAL need to be installed on the server?
No. CAL does not require installation. It is a license confirming the right of access to the server for a specified number of devices.
Does one computer used by multiple employees count as one license?
Yes. In the Device CAL model, the license is assigned to the device, not to individuals. One computer used by multiple employees still counts as one device.
What to do if there are more than 50 devices in the company?
You should purchase additional CAL licenses so that the number of licensed devices corresponds to the actual number of devices using the server.