
Microsoft Windows Server 2025 Remote Desktop Services External Connector Perpetual License
PRODUCT DESCRIPTION
Microsoft Windows Server 2025 Remote Desktop Services External Connector (DG7GMGF0PWHS:0001) - Local Support
RDS External Connector — Unlimited External Users, Licensed Per Physical Server
An External Connector licenses a server rather than a person. Microsoft defines it as “a License assigned to a Server that permits access to the corresponding version of the server software or earlier versions of the server software by External Users”. One External Connector covers any number of external users reaching Remote Desktop Services on that server, across any number of operating system environments on it.
Microsoft’s rule on quantity is simple and easy to under-buy: “Each physical server accessed requires an External Connector.” Two servers in the published farm means two External Connectors.
Read the Definition of “External User” Before You Buy This
This is the part that catches buyers out, and getting it wrong is an audit finding rather than a saving. Microsoft defines External Users precisely, and the definition is narrower than most buyers assume: users that are not “(a) employees of Customer or its Affiliates, (b) contractors or agents that typically work for Customer or its Affiliates for more than 30 hours on average per week, or (c) contractors or agents that typically work onsite for Customer or its Affiliates on each working day.”
In plain terms: your own employees are not external users. Neither is a contractor who works more than 30 hours a week for you on average, nor one who is onsite each working day. All of those still need ordinary RDS CALs. The External Connector is for genuinely third-party audiences — customers, partners, the public.
It Is Additive, and It Is Not a Run Right
The RDS External Connector is an additive External Connector: it sits on top of the base Windows Server External Connector in the same way an RDS CAL sits on top of a base CAL. And like a CAL, it grants access only. Microsoft: “The right to run instances of the server software is licensed separately; the EC, like the CAL, simply permits access.” The server is still licensed per core.
When It Is the Right Instrument — and When It Is Not
The External Connector wins when you cannot count or control the external audience: a customer portal, a public-facing application, a partner extranet. It is poor value, and non-compliant, if what you actually have is staff working remotely — that is an RDS CAL population, however inconvenient the counting.
Tell us who the audience genuinely is and how many physical servers they reach, and we will quote the instrument that fits rather than the one that looks cheapest. 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 External Connector Datasheet — Licensing and Specifications
Licence
| Product Name | Microsoft Windows Server 2025 Remote Desktop Services External Connector |
| Part Number (SourceIT) | DG7GMGF0PWHS:0001 |
| Licence Type | Perpetual additive External Connector |
| Licensing Model | Per physical server accessed |
| Users Covered | Any number of external users, across any number of operating system environments on that server |
| Internal Users | Not covered. Employees, and contractors working more than 30 hours a week on average or onsite each working day, require RDS CALs |
| Base Requirement | Additive to the base Windows Server External Connector, in the same way an RDS CAL is additive to a base CAL |
| Server Licence Included | No — the server is licensed separately, per core |
| Local Support (Singapore) | Supplied by SourceIT with local support and a GST invoice |
Microsoft’s Definition of an External User
| Covered | Users who are not employees or affiliates of your organisation — customers, partners, the public |
| NOT covered: employees | Employees of the customer or its affiliates |
| NOT covered: near-full-time contractors | Contractors or agents who typically work for you for more than 30 hours on average per week |
| NOT covered: onsite contractors | Contractors or agents who typically work onsite for you on each working day |
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 dedicated Microsoft product-terms page for Remote Desktop Services External Connector. 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.
Contractors are the detail most often got wrong on this licence. They are not simply covered or not covered: Microsoft’s definition excludes any contractor or agent who typically works for you more than 30 hours a week on average, or who works onsite each working day. A contractor outside both tests can be an external user; one inside either test needs an RDS CAL like an employee. If your arrangement is anywhere near those thresholds, ask us before you decide.
A sourcing limitation worth stating. Microsoft does not publish a product-terms page specific to Windows Server Remote Desktop Services at a live URL. The External Connector rules on this page are therefore taken from Microsoft’s product-terms glossary and its Windows Server 2025 licensing guidance, both of which are cited below.
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 defines External Users precisely, and the definition is narrower than most buyers assume: users that are not “(a) employees of Customer or its Affiliates, (b) contractors or agents that typically work for Customer or its Affiliates for more than 30 hours on average per week, or (c) contractors or agents that typically work onsite for Customer or its Affiliates on each working day.”
Quantity is per physical server: “Each physical server accessed requires an External Connector.” If your published desktops or applications are spread across three hosts, you need three.
The External Connector does not replace the base Windows Server External Connector — it is additive to it, exactly as an RDS CAL is additive to a base CAL.
If your remote audience is your own staff, this is the wrong product and we will tell you so. Buy RDS CALs, which we list in both User and Device form.
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
- Windows Server licensing resources — microsoft.com
Microsoft does not publish an RDS-specific product-terms page at a live URL; the glossary and licensing-guidance sources above are the authoritative ones for these rules. 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 External Connector
How many External Connectors do I need?
One per physical server that external users reach. Microsoft: “Each physical server accessed requires an External Connector.” It is not one per organisation.
Does it cover my employees working from home?
No. Microsoft’s definition of an external user excludes employees entirely. Staff working remotely need ordinary RDS CALs, however many of them there are.
Does it cover contractors?
Only some. Microsoft excludes contractors or agents who typically work for you more than 30 hours a week on average, or who work onsite each working day. A contractor outside both of those tests can be an external user. If you are unsure, ask us — this is the single most misread definition in Windows Server licensing.
Is it cheaper than buying RDS CALs?
For a genuinely external, uncountable audience, usually yes, because it covers unlimited external users per server. For internal staff it is not an option at any price.
Does it license the server as well?
No. Microsoft is explicit: the right to run the server software is licensed separately; the External Connector, like a CAL, simply permits access.
Do I also need the base Windows Server External Connector?
The RDS External Connector is additive, in the same way an RDS CAL is additive to a base CAL. Tell us the full picture and we will confirm the complete licence stack in writing before you order.
What warranty applies?
None, and none is implied — this is a licence, not hardware. SourceIT provides local Singapore support and a GST invoice.
