Microsoft Windows Server 2025 Remote Desktop Services 1 Device CAL Perpetual License
PRODUCT DESCRIPTION
Microsoft Windows Server 2025 Remote Desktop Services Device CAL (DG7GMGF0PWHB:0001) - Local Support
Remote Desktop Services Device CAL — Required IN ADDITION to a Windows Server CAL
An RDS CAL is required in addition to the base Windows Server CAL, not instead of it. This is the single most common and most expensive licensing mistake in the Windows Server range. Microsoft’s wording is “a Windows Server CAL and an incremental Remote Desktop Services (RDS) CAL is required for each user or device using Windows Server Remote Desktop Services”, and structurally: “Base CALs are the minimum requirement for accessing any of the applicable server product’s functionality” while “Access to advanced functionality associated with an Additive CAL requires the appropriate Additive CAL in addition to the Base CAL”.
If you are budgeting a Remote Desktop deployment, the arithmetic is three lines, not two: the server licence per core, a Windows Server CAL per user or device, and an RDS CAL per user or device on top. Miss the third and the deployment is unlicensed.
What an RDS CAL Buys You
Microsoft’s licensing guidance describes the RDS CAL as required “for use of Windows Server to host a graphical user interface” — that is, for a remote desktop or published-application session rather than ordinary file, print or directory access. Structurally it is an additive CAL: it unlocks advanced functionality on top of the base CAL, and does not replace it.
Device CAL: How It Is Assigned
This is the Per Device RDS CAL. Microsoft publishes that Per User RDS CALs are “assigned to a user in Active Directory”, while Per Device CALs are “physically assigned to each device”.
Getting the Instrument Right Matters Here
Per User and Per Device RDS CALs behave differently in ways that affect compliance, not just cost — see the lifecycle and entitlement section below for Microsoft’s published differences on over-allocation, revocation and tracking. Tell us your user and device counts and how they overlap, and we will quote the instrument that actually fits. Supplied by SourceIT in Singapore with a GST invoice and local support. For a written quotation, current stock position or delivery lead time, contact our team.
Microsoft Windows Server 2025 Remote Desktop Services Device CAL Datasheet — Licensing and Specifications
Licence
| Product Name | Microsoft Windows Server 2025 Remote Desktop Services Device CAL |
| Part Number (SourceIT) | DG7GMGF0PWHB:0001 |
| Licence Type | Perpetual additive Client Access Licence |
| Licensing Model | Per device |
| Base CAL Required | Yes — a Windows Server CAL is required in addition to this licence |
| Server Licence Included | No — the server is licensed separately, per core |
| Assignment | Physically assigned to each device |
| Over-allocation | Not possible — Microsoft states Per Device CALs cannot be over-allocated |
| Revocation | Up to 20% of RDS CALs may be revoked |
| Temporary CALs | Issued on first sign-in per device, valid for 90 days |
| Version Rule | RDS CALs cannot access a later version of Windows Server; later RDS CALs can access earlier servers |
| Local Support (Singapore) | Supplied by SourceIT with local support and a GST invoice |
The Three Licences a Remote Desktop Deployment Needs
| 1. Server licence | Windows Server 2025 Standard or Datacenter, licensed per physical core |
| 2. Base CAL | A Windows Server 2025 User or Device CAL for every user or device |
| 3. RDS CAL | This licence — an additional RDS CAL for every user or device using a Remote Desktop session |
What Microsoft Does Not Publish for This Product
The following are commonly asked about but are not stated on any current official Microsoft source for this product, so SourceIT does not quote them: a Singapore price and a Microsoft-published CAL price list. We would rather leave a field blank than print a figure we cannot substantiate.
Lifecycle, End of Support and Entitlement
Windows Server 2025 is a Long-Term Servicing Channel release under the Fixed Lifecycle Policy. Microsoft publishes mainstream support ending in November 2029 and extended support ending in November 2034, with its lifecycle database and its release-health page rendering each date one day apart. Both renderings appear in the table below.
This is a perpetual licence: a one-time purchase with no renewal. Note that “perpetual” describes the licence, not the support — Microsoft publishes a dated end of support for Windows Server 2025 (see the lifecycle section), and we do not use the word “lifetime” anywhere on this page.
Microsoft publishes useful operational differences for Per Device RDS CALs: they are “physically assigned to each device”, temporary CALs are issued on first sign-in and valid for 90 days, full CALs are “valid for a random period of 52–89 days before renewal”, up to 20% can be revoked, and they “can’t be over-allocated” — unlike Per User CALs, which can.
A note for anyone using the Azure Arc pay-as-you-go route: Microsoft publishes that “A pay-as-you-go subscription does not require CALs; however, Remote Desktop Services (RDS) CALs are still required.” Pay-as-you-go removes the base CAL, not the RDS CAL.
Published Lifecycle Dates
| Servicing model | Long-Term Servicing Channel (LTSC), under the Fixed Lifecycle Policy |
| Release date | 1 November 2024 per the lifecycle database and the release-health page. Microsoft’s update history separately shows the first build, KB5046617 (OS build 26100.2314), shipping 12 November 2024 |
| Mainstream support ends | 14 November 2029 per the lifecycle database; 13 November 2029 per the release-health page |
| Extended support ends | 15 November 2034 per the lifecycle database; 14 November 2034 per the release-health page |
| Why two dates | The same instant rendered in different timezones. Microsoft’s lifecycle page labels its dates Pacific Time yet renders them at 06:59:59, which is midnight PT of the previous day expressed in UTC. Both renderings are published here rather than one being chosen |
Support and Entitlement Position
A software licence carries no hardware warranty. SourceIT supplies this licence with local Singapore support and a GST invoice, and will confirm the licensing position in writing before you order — which on server licensing is worth doing, because the cost of getting it wrong surfaces at audit rather than at purchase. No warranty term is quoted or implied.
Compatibility, Deployment and System Requirements
Microsoft’s RDS CAL version rule: “The RDS CAL for your users or devices must be compatible with the version of Windows Server that the user or device connects to. You can’t use RDS CALs for earlier versions to access later versions of Windows Server, but you can use later versions of RDS CALs to access earlier versions of Windows Server.”
If your remote users are genuinely external to your organisation — customers, partners, the public — an RDS External Connector may be the cheaper instrument, because it covers unlimited external users per physical server. Read the external-user definition on that product page carefully first: it excludes your employees and any contractor working more than 30 hours a week or onsite each working day.
Official Microsoft Sources & Downloads
- Desktop Application and Windows Server RDS licensing guidance — microsoft.com/licensing
- Base and Additive CALs — microsoft.com/licensing
- Remote Desktop Services client access licenses — Microsoft Learn
- Microsoft product terms glossary — microsoft.com/licensing
- Windows Server 2025 licensing guidance — microsoft.com/licensing
Every licensing rule quoted on this page comes from the Microsoft sources above. Supplied by SourceIT in Singapore with a GST invoice and local support. For a written quotation, current stock position or delivery lead time, contact our team.
Frequently Asked Questions — Microsoft Windows Server 2025 Remote Desktop Services Device CAL
Do I still need a normal Windows Server CAL as well?
Yes. This is the most important thing on this page. Microsoft requires “a Windows Server CAL and an incremental Remote Desktop Services (RDS) CAL” for each user or device using Remote Desktop Services. The RDS CAL is additive, not a substitute.
Does this license the server itself?
No. The server is licensed separately, per physical core. A Remote Desktop deployment needs three things: the server licence, a base CAL, and this RDS CAL.
Can I use RDS CALs from an older Windows Server version?
No. Microsoft: you “can’t use RDS CALs for earlier versions to access later versions of Windows Server”. Later RDS CALs can access earlier servers, so buying current is the safe direction.
Per User or Per Device — which should I buy?
Per Device if several people share each machine; Per User if people roam across devices. Microsoft publishes that Per Device CALs cannot be over-allocated, that up to 20% of them can be revoked, and that they can be tracked regardless of Active Directory membership — which makes them the more controllable instrument of the two.
What if my remote users are outside my organisation?
Then look at the RDS External Connector, which covers unlimited external users per physical server. Check the definition first: Microsoft excludes employees and contractors working more than 30 hours a week or onsite each working day.
Does pay-as-you-go remove the need for this?
No. Microsoft states that a pay-as-you-go subscription does not require base CALs, but RDS CALs are still required.
What warranty applies?
None, and none is implied — a CAL is a licence, not hardware. SourceIT provides local Singapore support and a GST invoice.
