Understanding User CALs and Device CALs

Selecting the right Windows Server edition is only one part of the licensing process. Once the server itself is licensed, the next question is often the one that causes the most confusion:

Do we also need Client Access Licenses (CALs)?

For many organizations, the answer is yes—but determining which type of CAL is appropriate isn’t always straightforward.

The choice between User CALs and Device CALs depends less on technical specifications and more on how people actually work. Do employees use several devices throughout the day? Are workstations shared between multiple users? Will the business continue to grow over the next few years?

Understanding these scenarios is far more valuable than simply memorizing licensing terminology.

In this guide, we’ll explain how Windows Server CAL licensing works, compare User CALs and Device CALs with practical examples, highlight common licensing mistakes, and help you choose the model that best aligns with your organization’s day-to-day operations.

If you’re still evaluating server editions, our Windows Server 2025 Standard vs Datacenter: Complete Comparison explains how virtualization rights and infrastructure planning influence licensing decisions before CALs come into the picture.

For a broader overview of Microsoft’s licensing model, you can also read our Windows Server Licensing Guide.

What Is a Windows Server CAL?
Why Does Windows Server Use CALs?
When Are CALs Required?
Understanding User CALs
Understanding Device CALs
User CAL vs Device CAL
Which Licensing Model Fits Your Business?
Common Licensing Mistakes (Part 2)

What Is a Windows Server CAL?

A Client Access License (CAL) is a license that grants a user or a device permission to access services provided by a licensed Windows Server.

One of the biggest misconceptions is that purchasing Windows Server automatically covers everyone who connects to it. In reality, the server license and CALs serve different purposes.

Think of it this way:

The Windows Server license allows you to install and run the server operating system.
Client Access Licenses determine who or what is permitted to access the services hosted on that server.

Those services might include:

File sharing
Active Directory
Print services
Shared folders
Internal business applications
Authentication services
Network resources

While this licensing structure may seem unusual at first, it allows organizations of different sizes to license access according to their operational needs rather than using a one-size-fits-all model.

Why Does Windows Server Use CAL Licensing?

Businesses don’t all use Windows Server in the same way.

A small accounting firm with six employees has very different requirements from a manufacturing company with hundreds of workers across multiple locations.

Instead of treating every deployment identically, Microsoft separates the licensing of the server itself from the licensing of the people or devices accessing it.

This provides flexibility for organizations that:

are expanding gradually,
operate multiple offices,
use shared workstations,
support remote employees,
or manage hybrid IT environments.

Although the licensing terminology can appear complex at first, the underlying concept is fairly straightforward once you understand who is connecting to the server and how they access it.

When Are CALs Required?

One of the most common questions organizations ask is whether CALs are required for every Windows Server deployment.

The answer depends on how Windows Server is being used.

In many business environments where employees or company devices authenticate to Windows Server and access its services, Client Access Licenses are typically part of the licensing model.

For example, employees may access:

shared company files,
printers,
Active Directory,
business applications,
accounting systems,
or internal databases.

Rather than asking:

“Do we need CALs?”

it’s often more useful to ask:

“Who will be connecting to the server, and from what devices?”

That perspective usually makes licensing decisions much easier.

Understanding User CALs

A User CAL is assigned to an individual person.

Once licensed, that employee can generally access Windows Server from multiple devices without requiring a separate CAL for each one.

This approach works particularly well in organizations where employees regularly switch between different computers throughout the day.

Typical examples include:

office desktop computers,
company laptops,
home office PCs,
tablets,
remote work environments.

Instead of licensing every piece of hardware, the license follows the individual.

Example: Consulting Firm

A financial consulting company has 18 employees.

Each consultant works from:

an office workstation,
a company laptop,
and occasionally a home computer.

Licensing every device separately would quickly become difficult to manage.

In this scenario, assigning one User CAL to each employee is typically the simpler and more flexible solution.

Understanding Device CALs

A Device CAL takes the opposite approach.

Instead of licensing an individual employee, the license is assigned to a specific computer or workstation.

Anyone using that licensed device may access Windows Server services.

This licensing model is particularly common in environments where several employees share the same equipment throughout the day.

Typical examples include:

warehouse terminals,
hospital nursing stations,
retail checkout systems,
manufacturing floor workstations,
reception desks,
training room computers.

Example: Warehouse

A distribution center operates three shifts every day.

Forty-five employees share twelve warehouse terminals.

Because the number of devices is much smaller than the number of users, licensing each workstation with a Device CAL is often the more efficient approach.

User CAL vs Device CAL

Although both licensing models provide access to Windows Server services, they solve different business problems.

Business Scenario	User CAL	Device CAL
Employees use multiple computers	✔ Recommended
Shared office workstations		✔ Recommended
Hybrid workforce	✔ Recommended
Manufacturing facilities		✔ Recommended
Schools and training rooms		✔ Recommended
Mobile employees	✔ Recommended

The important point is that there isn’t a universally better option.

Instead, organizations should choose the licensing model that reflects how employees interact with their technology every day.

Which Licensing Model Fits Your Business?

Rather than focusing only on licensing terminology, consider your organization’s daily workflow.

Ask questions like:

Do employees work from more than one computer?
Are workstations shared across multiple shifts?
Is remote work common?
Will additional employees join the business soon?
Are users mostly office-based, or do they work in warehouses, healthcare facilities, retail stores, or educational environments?

The answers often make the right licensing approach much clearer.

Licensing decisions also become more important as businesses expand their infrastructure. Organizations planning larger deployments should understand how Windows Server editions affect future scalability and virtualization rights. If you haven’t already, our Windows Server 2025 Standard vs Datacenter: Complete Comparison provides a detailed overview before moving on to more advanced licensing topics.

Common Windows Server CAL Licensing Mistakes

Most CAL licensing problems do not start with a complicated server configuration. They usually begin with a simple assumption that turns out to be wrong later.

A business adds employees, introduces remote work, opens another location, or changes how workstations are shared. The server continues to operate normally, so nobody revisits the licensing model.

That is where gaps can appear.

Assuming the Server License Covers Every User

Purchasing Windows Server does not automatically provide access rights for every employee in the organization.

The server license and Client Access Licenses address different parts of the licensing model. One covers the server software; the other covers access by users or devices where CALs are required.

This distinction should be reviewed during deployment planning rather than after the server is already in daily use.

Counting Employees Instead of Actual Access

Suppose a company has 70 employees.

That number alone does not tell you how many CALs may be needed.

Perhaps only 25 employees access Windows Server resources. Or perhaps 70 employees work across 20 shared terminals.

The correct starting point is to document who accesses the server and how that access happens.

Choosing User CALs Because They Sound Simpler

User CALs are convenient in environments where employees use several devices, but that does not make them the default choice for every business.

A warehouse with 80 employees and 15 shared terminals may have a very different licensing profile from an office with 80 employees who each use a desktop and a laptop.

The licensing model should reflect the environment, not familiarity with a particular CAL type.

Forgetting About Business Growth

A licensing model that works for a ten-person company may become inefficient after the business doubles in size.

Changes such as remote work, additional offices, new shifts, and shared workstations can alter the balance between User CALs and Device CALs.

CAL planning should therefore be reviewed when the way people access server resources changes.

Confusing Windows Server CALs with RDS CALs

This is probably the most common point of confusion.

A Windows Server CAL and a Remote Desktop Services CAL are not interchangeable.

Standard Windows Server CALs cover access to Windows Server services under the applicable licensing terms. Remote Desktop Services introduces an additional licensing layer for users or devices connecting through RDS.

We will examine that difference in more detail below.

How CALs Fit into Windows Server Licensing

It helps to view Windows Server licensing as a series of layers rather than a single purchase.

A typical business deployment may look like this:

Windows Server license

↓

The physical server and its processor cores are licensed

↓

Windows Server is installed and configured

↓

Users or devices access server services

↓

User CALs or Device CALs may be required

↓

Remote Desktop Services CALs may also be required when RDS is used

Each layer answers a different licensing question.

The Windows Server license covers the server operating system and is tied to Microsoft’s server licensing rules. CALs address access to Windows Server services. RDS CALs address qualifying Remote Desktop Services access.

Core licensing adds another consideration because modern Windows Server editions are commonly licensed according to the physical cores in the server.

For a broader explanation of how core licensing, CALs, virtualization rights, and server editions work together, see our Complete Windows Server Licensing Guide.

Later in this Windows Server series, we will also cover core calculations separately in the Windows Server Core Licensing Guide.

Are Windows Server CALs and RDS CALs the Same?

No.

This distinction is important because the names are similar enough to cause confusion.

A Windows Server CAL provides qualifying access rights to Windows Server services.

An RDS CAL is associated specifically with Remote Desktop Services access.

Consider a company where employees use Windows Server for file sharing and Active Directory. The organization may require Windows Server CALs for those users or devices.

Now imagine the same company configures a Remote Desktop Session Host so employees can sign in remotely and run business applications on the server.

That changes the licensing scenario.

Using Remote Desktop Services generally introduces RDS CAL requirements in addition to the underlying Windows Server access licensing requirements.

License Type	Primary Purpose
Windows Server License	Licenses the server operating system
Windows Server CAL	Covers qualifying user or device access to Windows Server
RDS CAL	Covers qualifying access through Remote Desktop Services

The exact requirements depend on the deployment and applicable Microsoft licensing terms, so organizations should review their environment before making licensing decisions.

Our Windows Server RDS CAL Guide explains this licensing layer in detail, including the difference between RDS User CALs and RDS Device CALs.

Can a Business Use Both User CALs and Device CALs?

Yes, some organizations operate environments where a single CAL model does not reflect every department.

Consider a company with two very different teams.

The administrative department has 25 employees. Each person uses a desktop in the office and a company laptop when working remotely.

User CALs may make sense for those employees.

The same company also operates a warehouse with 40 workers sharing eight terminals across several shifts.

Device CALs may be more practical for the warehouse environment.

This is why CAL planning should be based on actual access patterns.

The goal is not to force the entire organization into one licensing model simply because it is easier to describe. The licensing structure should match how users and devices access Windows Server resources.

Organizations using a mixed approach should maintain clear records showing how licenses are assigned.

Real-World CAL Licensing Scenarios

Licensing rules are easier to understand when applied to actual workplace environments.

Scenario 1: Accounting Firm

An accounting firm has 22 employees.

Every employee has a desktop computer at the office. Most also use company laptops when visiting clients or working remotely.

The number of devices is significantly higher than the number of employees.

Likely approach: User CALs.

Licensing the users can be more practical because each person accesses server resources from several devices.

Scenario 2: Manufacturing Facility

A manufacturing company employs 90 production workers across three shifts.

Employees share 18 computers located throughout the production facility.

The number of users is much higher than the number of devices.

Likely approach: Device CALs.

Licensing shared workstations may align more closely with the way the facility operates.

Scenario 3: Growing Professional Services Company

A consulting company currently employs 30 people but plans to hire another 20 employees during the next year.

Most consultants use laptops and frequently work outside the office.

Likely approach: User CALs, with future staffing growth included in licensing planning.

The important point is not simply choosing the correct CAL type today. The company should also have a process for assigning CALs as new employees join.

Scenario 4: Retail Business

A retailer operates several locations.

Employees at each location share a small number of workstations used for internal business systems.

Staff turnover is relatively high, but the number of devices remains stable.

Likely approach: Device CALs may be worth evaluating.

Licensing individual employees could become difficult to manage when the workforce changes frequently.

Scenario 5: Mixed Office and Warehouse Environment

A distribution company has:

35 office employees using individual laptops
60 warehouse employees sharing 12 terminals

Using only User CALs or only Device CALs may not reflect the organization’s actual access pattern.

A mixed licensing approach may be more practical, with User CALs assigned to office employees and Device CALs assigned to qualifying shared warehouse terminals.

These examples are simplified for planning purposes. Actual licensing decisions should be based on Microsoft’s current product terms and the organization’s specific deployment.

Do CALs Depend on Standard or Datacenter Edition?

The choice between Standard and Datacenter does not remove the need to evaluate Client Access Licensing.

Standard and Datacenter primarily differ in areas such as virtualization rights and advanced infrastructure capabilities.

CAL requirements address a different question: who or what accesses the Windows Server environment?

This means a small Standard deployment and a large Datacenter environment may both need CAL planning.

If the main decision is still which server edition fits your infrastructure, our Windows Server 2025 Standard vs Datacenter comparison explains the differences in virtualization rights, features, and deployment scenarios.

CAL Planning for Virtualized Environments

Virtualization often makes Windows Server licensing discussions more complicated because several licensing concepts are considered at the same time.

An administrator may be thinking about:

physical cores,
virtual machines,
Standard versus Datacenter,
Windows Server CALs,
and Remote Desktop Services.

These are related, but they are not the same licensing requirement.

Virtualization rights determine how Windows Server may be deployed in virtual operating system environments after the physical host is correctly licensed.

CALs still address access by users or devices.

For example, moving a file server from physical hardware into a Hyper-V virtual machine does not automatically eliminate the need to evaluate Client Access Licensing.

Organizations building larger virtual environments should separate these questions during planning:

How is the physical server licensed?
Which Windows Server edition is being used?
How many virtual operating system environments are planned?
Which users or devices access Windows Server services?
Is Remote Desktop Services part of the deployment?

Our upcoming Windows Server Hyper-V Licensing Guide will focus specifically on virtualization rights and how Standard and Datacenter licensing differ in Hyper-V environments.

How to Plan Windows Server CALs Before Deployment

A simple inventory is often more useful than starting with a licensing calculator.

Create three lists.

List 1: Users

Document employees and other qualifying users who need access to Windows Server resources.

Consider whether they:

work remotely,
use multiple devices,
travel regularly,
or access server resources from different locations.

List 2: Devices

Document computers and workstations that connect to the Windows Server environment.

Identify:

individually assigned computers,
shared workstations,
warehouse terminals,
reception computers,
and other shared devices.

List 3: Access Methods

Finally, document how server resources are accessed.

Examples include:

Active Directory authentication,
shared file access,
internal applications,
Remote Desktop Services,
and virtualized business applications.

Once these three lists are complete, the User CAL versus Device CAL decision usually becomes much easier.

Businesses planning a new deployment may also want to review the Windows Server 2025 System Requirements Guide before finalizing server hardware and infrastructure planning.

Best Practices for Managing CAL Licensing

CAL management does not need to become a complicated administrative project.

A few practical habits can make licensing easier to review.

Keep a record of assigned User CALs and Device CALs.
Review licensing when employees join or leave the organization.
Document shared workstation environments.
Reassess CAL strategy when opening new locations.
Review remote access changes separately.
Do not assume RDS access is covered by a standard Windows Server CAL.
Check current Microsoft product terms when planning major infrastructure changes.

The most important habit is to treat licensing as part of infrastructure management rather than a one-time purchasing task.

Servers change. Workforces change. Access patterns change.

Licensing plans should be reviewed when those changes materially affect the environment.

Frequently Asked Questions About Windows Server CALs

Are CALs included with Windows Server?

Windows Server licensing and Client Access Licensing are separate components in many licensing scenarios. Organizations should verify the licensing terms for their specific Windows Server edition and deployment.

Do I need one CAL for every employee?

Not necessarily.

The number and type of CALs depend on which users or devices access Windows Server services. A Device CAL model, for example, may be more practical when many employees share a smaller number of workstations.

Can one User CAL cover multiple computers?

A User CAL is assigned to an individual user and is generally intended for scenarios where that person accesses Windows Server from multiple devices, subject to applicable licensing terms.

Can multiple employees use a device with one Device CAL?

A Device CAL is assigned to a specific device. Multiple authorized users may use that licensed device to access Windows Server services under the applicable licensing terms.

Can I mix User CALs and Device CALs?

Organizations may use both CAL models when different parts of the business have different access patterns. Clear licensing records are particularly important in mixed environments.

Do I need CALs for virtual machines?

Virtualization rights and Client Access Licensing address different parts of Windows Server licensing. Running Windows Server in a virtual machine does not automatically remove CAL considerations for users or devices accessing server services.

Is an RDS CAL the same as a Windows Server CAL?

No. Remote Desktop Services licensing is an additional licensing consideration. Organizations using qualifying RDS functionality generally need to evaluate RDS CAL requirements alongside Windows Server CALs.

Do administrators need CALs?

Licensing exceptions may apply to limited server administration scenarios. Organizations should review current Microsoft licensing terms for the specific access scenario rather than assuming all administrative access is treated the same.

Should I choose User CALs or Device CALs?

Choose based on access patterns.

User CALs are often more practical when employees use several devices. Device CALs are often worth considering when many employees share a smaller number of workstations.

Do CALs expire?

The answer depends on the licensing program and agreement under which the licenses were acquired. Businesses should verify the terms associated with their licensing channel and deployment.

Final Thoughts

Windows Server CAL licensing becomes much easier to understand once you stop thinking about CALs as a technical server feature.

They are primarily an access licensing decision.

If employees regularly use several devices, User CALs may align more naturally with the business. If many employees share a limited number of workstations, Device CALs may be the more practical model.

The difficult part is rarely understanding the difference between the two. The real challenge is accurately documenting how people and devices interact with the server environment.

Start with users, devices, and access methods. Then evaluate the licensing model against the organization’s actual workflow.

For the broader licensing picture, our Complete Windows Server Licensing Guide explains how core licensing, server editions, CALs, Remote Desktop Services, and virtualization rights fit together.

If you are planning a new server deployment, the Windows Server 2025 Standard vs Datacenter comparison can also help clarify the edition decision before you finalize access licensing.

The next topic in this Windows Server series is Windows Server RDS CAL Licensing, where we will look specifically at Remote Desktop Services, RDS User CALs, RDS Device CALs, and common remote access licensing scenarios.