{"product_id":"microsoft-windows-server-2016-rds-device-cal-50-cal","title":"Microsoft Windows Server 2016 RDS Device CAL [50 CAL]","description":"\u003ch2\u003eWindows Server 2016 RDS Device CAL: Authorize 50 Devices to Connect via Remote Desktop\u003c\/h2\u003e\n\u003cp\u003eWhen users connect to a \u003ca href=\"\/products\/microsoft-windows-server-2016-rds-device-cal-50-cal\"\u003eWindows Server 2016 RDS Device CAL\u003c\/a\u003e host through the Remote Desktop Services role, two licenses are required: a Windows Server CAL that authorizes the access to the server itself, and a Remote Desktop Services CAL that authorizes the Remote Desktop connection. The \u003ca href=\"\/products\/microsoft-windows-server-2016-rds-user-cal-50-cal\"\u003eWindows Server 2016 RDS Device CAL,\u003c\/a\u003e sold in a 50-pack, is the additive CAL that grants the Remote Desktop authorization, billed per device rather than per user. Your key is delivered to your account dashboard within seconds of payment clearing, ready to paste into the Remote Desktop Licensing Manager. If the key fails to activate for any reason within 7 days, you get a one-to-one replacement key or a full refund — your choice, no questions asked. Activate the CAL pack on your Remote Desktop license server and start assigning licenses within minutes. 🖥️🔧\u003c\/p\u003e\n\n\u003ch2\u003eWhat Is Included and How Activation Works\u003c\/h2\u003e\n\u003cp\u003eWhen your order is confirmed, you receive a 25-character \u003ca href=\"\/products\/microsoft-windows-server-2016-essentials-retail-2-pc\"\u003eWindows Server 2016 Essentials\u003c\/a\u003e RDS Device CAL product key and a Certificate of Authenticity (COA) delivered to your account dashboard and your order email. The key activates 50 Device CALs on a Remote Desktop License Server (RDLS), which is the role that issues and tracks RDS CALs in a Windows Server environment. The license is perpetual: the Device CALs are valid for the lifetime of the server, and the same CALs can be issued to replacement devices as older devices are retired.\u003c\/p\u003e\n\u003cp\u003eThe standard activation flow takes about fifteen minutes on a server with internet access:\u003c\/p\u003e\n\u003col\u003e\n\u003cli\u003eInstall the Remote Desktop Licensing role on a \u003ca href=\"\/products\/microsoft-windows-server-2016-essentials-retail-5-pc\"\u003eWindows Server 2016 Essentials\u003c\/a\u003e host in the same Active Directory forest as the RDS session hosts you want to license.\u003c\/li\u003e\n\u003cli\u003eOpen the Remote Desktop Licensing Manager and add the 25-character product key from your order email.\u003c\/li\u003e\n\u003cli\u003eActivate the license server through the Microsoft Clearinghouse. The default internet activation method is the simplest; telephone activation is available for air-gapped environments.\u003c\/li\u003e\n\u003cli\u003ePoint the RDS session hosts in the deployment at the activated license server using Group Policy or the RDS configuration tool.\u003c\/li\u003e\n\u003cli\u003eThe license server issues a temporary CAL on first connection and a permanent CAL after the device reconnects.\u003c\/li\u003e\n\u003c\/ol\u003e\n\u003cp\u003eOnce activated, the license server tracks the issued Device CALs centrally and reports on remaining capacity through the Remote Desktop Licensing Manager. Devices that connect to a session host receive their CAL from the license server automatically; no per-device interaction is required.\u003c\/p\u003e\n\n\u003ch2\u003eKey Features and Capabilities\u003c\/h2\u003e\n\u003cul\u003e\n\u003cli\u003e\n\u003cstrong\u003e50 RDS Device CALs in one pack.\u003c\/strong\u003e A single 25-character product key activates 50 Device CALs on a Remote Desktop License Server. Larger deployments can stack multiple 50-packs to reach the required capacity.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eCompatibility with \u003ca href=\"\/products\/microsoft-windows-server-2016-r2-standard-retail-2-pc\"\u003eWindows Server 2016.\u003c\/a\u003e\u003c\/strong\u003e RDS CALs purchased for \u003ca href=\"\/products\/microsoft-windows-server-2016-standard-retail-2-pc\"\u003eWindows Server 2016 Standard\u003c\/a\u003e are valid for \u003ca href=\"\/products\/microsoft-windows-server-2016-standard-retail-5-pc\"\u003eWindows Server 2016\u003c\/a\u003e session hosts only. The 2016 RDS CALs are not valid for \u003ca href=\"\/products\/microsoft-windows-server-2019-rds-device-cal-50-cal\"\u003eWindows Server 2019,\u003c\/a\u003e 2022, or later Windows Server versions unless the CAL is upgraded through Software Assurance or a Volume Licensing agreement.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eRDS Gateway, RDS Web Access, and the modern RDS feature set.\u003c\/strong\u003e The Device CAL authorizes the use of the full Remote Desktop Services feature set, including RDS Gateway for secure external access, RDS Web Access for browser-based session launch, RDS Connection Broker for session distribution, and RemoteApp for individual application publishing.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eCentralized tracking on the RDLS.\u003c\/strong\u003e The Remote Desktop License Server issues, tracks, and reports on all RDS CALs in the deployment. The license manager shows the number of CALs available, the number of CALs issued, and the history of CAL issuance.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eTemporary CALs for first-time devices.\u003c\/strong\u003e The first time a device connects to a session host, the license server issues a temporary CAL valid for 90 days. The temporary CAL is converted to a permanent CAL when the device reconnects to the session host within the temporary period.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eRight model for shared devices.\u003c\/strong\u003e The Device CAL is the more cost-effective choice when the same device is shared by multiple users: factory-floor terminals, hospital workstations, retail point-of-sale systems, or call-center shifts where one workstation is used by many different employees.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eCompatible with User CALs in the same environment.\u003c\/strong\u003e The same license server can hold both Device CALs and User CALs, and a deployment can mix the two models to match the way different groups of users access the server.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eClearinghouse activation for license compliance.\u003c\/strong\u003e The license server is registered with the Microsoft Clearinghouse, which provides the central registration and tracking that supports software license compliance audits.\u003c\/li\u003e\n\u003c\/ul\u003e\n\n\u003ch2\u003eWho This Edition Is For\u003c\/h2\u003e\n\u003cp\u003eThe RDS Device CAL is the right choice when devices are shared by multiple users. The personas below describe the most common buyers of a 50-pack of Windows Server 2016 RDS Device CALs.\u003c\/p\u003e\n\u003cul\u003e\n\u003cli\u003e\n\u003cstrong\u003eCall centers and contact centers.\u003c\/strong\u003e A small pool of workstations is shared by a large number of agents across shifts. The Device CAL is the more cost-effective model because each workstation is one CAL, regardless of how many agents use it.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eHealthcare and clinical workstations.\u003c\/strong\u003e Hospital wards, nursing stations, and clinical workstations are shared by many clinicians. The Device CAL is the standard licensing model for these shared workstations.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eRetail point-of-sale and back-office terminals.\u003c\/strong\u003e Retail chains with a fixed pool of terminals and a rotating pool of staff benefit from the Device CAL model, especially in environments with high staff turnover.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eManufacturing and factory-floor workstations.\u003c\/strong\u003e A production line with a fixed number of operator terminals that are used by many different operators is a typical Device CAL scenario.\u003c\/li\u003e\n\u003c\/ul\u003e\n\n\u003ch2\u003eSystem Requirements\u003c\/h2\u003e\n\u003cp\u003eThe RDS Device CAL is a software license; there is no client-side hardware requirement beyond the workstation that is connecting to the session host. The license server that holds and tracks the CALs is a Windows Server role that follows the standard Windows Server 2016 hardware baseline.\u003c\/p\u003e\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eComponent\u003c\/th\u003e\n\u003cth\u003eMinimum\u003c\/th\u003e\n\u003cth\u003eRecommended\u003c\/th\u003e\n\u003c\/tr\u003e\n\u003c\/thead\u003e\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003eLicense server OS\u003c\/td\u003e\n\u003ctd\u003eWindows Server 2016\u003c\/td\u003e\n\u003ctd\u003eWindows Server 2016 with full management tools\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eProcessor\u003c\/td\u003e\n\u003ctd\u003e1.4 GHz 64-bit (x64)\u003c\/td\u003e\n\u003ctd\u003eMulti-core 64-bit server CPU at 2 GHz or higher\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eRAM\u003c\/td\u003e\n\u003ctd\u003e512 MB minimum; 2 GB for Server with Desktop Experience\u003c\/td\u003e\n\u003ctd\u003e4 GB or more for a license-only server\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eStorage\u003c\/td\u003e\n\u003ctd\u003e32 GB system partition\u003c\/td\u003e\n\u003ctd\u003e40 GB or more for the license database growth\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eNetwork\u003c\/td\u003e\n\u003ctd\u003eStandard Ethernet adapter\u003c\/td\u003e\n\u003ctd\u003eGigabit Ethernet connected to the Active Directory domain\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eActive Directory\u003c\/td\u003e\n\u003ctd\u003eMember server in an Active Directory domain\u003c\/td\u003e\n\u003ctd\u003eSame forest as the session hosts\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eClient devices\u003c\/td\u003e\n\u003ctd\u003eAny device running Microsoft Remote Desktop Client 8.0 or later\u003c\/td\u003e\n\u003ctd\u003eCurrent Remote Desktop client\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003c\/tbody\u003e\n\u003c\/table\u003e\n\u003cp\u003eThe license server should be a member server in the same Active Directory forest as the session hosts it is licensing. Group Policy is the typical way to point session hosts at the license server; the policy setting is found under \u003cstrong\u003eComputer Configuration → Administrative Templates → Windows Components → Remote Desktop Services → Remote Desktop Session Host → Licensing\u003c\/strong\u003e.\u003c\/p\u003e\n\n\u003ch2\u003eActivation and Licensing Notes\u003c\/h2\u003e\n\u003cp\u003eYour 50-pack of Windows Server 2016 RDS Device CALs is a perpetual license that is tracked on the Remote Desktop License Server. A few details worth knowing up front:\u003c\/p\u003e\n\u003cul\u003e\n\u003cli\u003e\n\u003cstrong\u003eOne CAL per device.\u003c\/strong\u003e Each Device CAL authorizes one device to connect to a session host. The number of users who use that device is irrelevant for licensing purposes.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eIssued automatically on first connection.\u003c\/strong\u003e The license server issues a temporary CAL the first time a device connects, and a permanent CAL when the device reconnects. There is no per-device interaction with the license server.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eCALs remain with the device.\u003c\/strong\u003e A Device CAL stays with the original device even when the user changes. When the device is retired, the CAL is released back to the license pool after the standard 90-day temporary-CAL period.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eThis is a 2016 CAL.\u003c\/strong\u003e These CALs are valid for Windows Server 2016 only. For \u003ca href=\"\/products\/microsoft-windows-server-2019-rds-user-cal-50-cal\"\u003eWindows Server 2019 RDS User CAL\u003c\/a\u003e \u003ca href=\"\/products\/microsoft-windows-server-2022-rds-device-cal-50-cal\"\u003eWindows Server 2022,\u003c\/a\u003e or later session hosts, the matching RDS CAL for that version must be purchased.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eActive Directory is required.\u003c\/strong\u003e The license server is a member server in an Active Directory domain. A workgroup license server is supported but adds management complexity.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eMicrosoft support timeline.\u003c\/strong\u003e Windows Server 2016 mainstream support ended on January 11, 2022. Extended support continues through January 12, 2027, with security updates only. The CALs themselves remain valid but the underlying operating system no longer receives feature updates.\u003c\/li\u003e\n\u003c\/ul\u003e\n\n\u003ch2\u003eGet Started With Windows Server 2016 RDS Device CALs\u003c\/h2\u003e\n\u003cp\u003eBuying a 50-pack of Windows Server 2016 RDS Device CALs is the simplest way to authorize 50 shared devices to connect to your Remote Desktop Services deployment. Once the order is confirmed, the key and COA are in your inbox, the activation steps are above, and the CALs are issued to your session hosts in one short session. If you have any questions about whether the Device CAL is the right model for your deployment, our support team is on hand before and after the purchase.\u003c\/p\u003e\u003ch2\u003eMicrosoft Windows Server 2016 RDS Device CAL Alternatives\u003c\/h2\u003e\n\u003cp\u003eThree credible alternatives cover most server workloads depending on your requirements.\u003c\/p\u003e\n\u003ch3\u003eLinux Server (Ubuntu LTS or RHEL)\u003c\/h3\u003e\u003cp\u003eFree or low-cost, runs most modern web, container, and database workloads, and is widely supported by cloud providers.\u003c\/p\u003e\u003ch3\u003eWindows Server on Azure \/ AWS \/ GCP\u003c\/h3\u003e\u003cp\u003eManaged cloud versions of Windows Server with pay-as-you-go licensing. Removes the need for an on-premises licence key.\u003c\/p\u003e\u003ch3\u003eWindows Server LTSC container images\u003c\/h3\u003e\u003cp\u003eMicrosoft-published container images for development and CI\/CD scenarios. Free for development but require a licence for production use.\u003c\/p\u003e\n\u003cp\u003e\u003cstrong\u003eHow to choose:\u003c\/strong\u003e Stay on Windows Server if you run Active Directory, SQL Server, Exchange, or .NET Framework line-of-business apps. Move to Linux server for new web and container workloads. Move to cloud-managed Windows Server to remove licence management overhead.\u003c\/p\u003e\n\n\u003ch2\u003eFrequently Asked Questions\u003c\/h2\u003e\n\u003cdetails\u003e\n\u003csummary\u003eWhat is the difference between a Device CAL and a User CAL?\u003c\/summary\u003e\n\u003cp\u003eA Device CAL authorizes one device to connect to a session host, regardless of how many users share that device. A User CAL authorizes one user to connect to a session host from any number of devices. The Device CAL is the more cost-effective choice when many users share a small pool of devices; the User CAL is the more cost-effective choice when one user connects from many devices. The two models can be mixed in the same environment.\u003c\/p\u003e\n\u003c\/details\u003e\n\u003cdetails\u003e\n\u003csummary\u003eDo I also need a Windows Server CAL?\u003c\/summary\u003e\n\u003cp\u003eYes. A Windows Server CAL is required for every user or device that accesses the server itself, and an RDS CAL is an additional license that is required specifically for the Remote Desktop connection. Both licenses are required for any device that connects to a Windows Server 2016 session host via Remote Desktop.\u003c\/p\u003e\n\u003c\/details\u003e\n\u003cdetails\u003e\n\u003csummary\u003eCan I use 2016 RDS CALs with later Windows Server versions?\u003c\/summary\u003e\n\u003cp\u003eNo. RDS CALs are version-specific. The 2016 RDS CALs are valid for Windows Server 2016 session hosts only. For Windows Server 2019 or later session hosts, the matching RDS CAL for that version must be purchased. The exception is downgrade rights through Software Assurance, which can allow a later CAL to be used against an earlier session host.\u003c\/p\u003e\n\u003c\/details\u003e\n\u003cdetails\u003e\n\u003csummary\u003eWhat is a Remote Desktop License Server?\u003c\/summary\u003e\n\u003cp\u003eThe Remote Desktop License Server is a Windows Server role that issues, tracks, and reports on RDS CALs in a Windows Server environment. The license server is activated with the Microsoft Clearinghouse and holds the CAL database for the deployment. Session hosts in the deployment point at the license server through Group Policy.\u003c\/p\u003e\n\u003c\/details\u003e\n\u003cdetails\u003e\n\u003csummary\u003eWhat happens if the license server is offline?\u003c\/summary\u003e\n\u003cp\u003eIf the license server is temporarily offline, session hosts continue to issue temporary CALs to connecting devices. The temporary CAL is valid for 90 days, which gives the operations team time to bring the license server back online. If the license server remains offline past the temporary period, devices that attempt to reconnect receive a licensing error and cannot start a new session.\u003c\/p\u003e\n\u003c\/details\u003e\n\u003cdetails\u003e\n\u003csummary\u003eHow long does delivery take?\u003c\/summary\u003e\n\u003cp\u003eThe product key and Certificate of Authenticity are delivered to your account dashboard and order confirmation email immediately after payment is confirmed, typically within seconds. The activation flow on the license server takes about fifteen minutes including the Clearinghouse registration.\u003c\/p\u003e\n\u003c\/details\u003e\n\n","brand":"Microsoft","offers":[{"title":"Default Title","offer_id":59850922623057,"sku":"MS-148-MICROSOFT-WINDOWS-SERVER-2016-RDS-DEVICE","price":9.99,"currency_code":"USD","in_stock":true}],"thumbnail_url":"\/\/cdn.shopify.com\/s\/files\/1\/1059\/0191\/6241\/files\/microsoft-windows-server-2016-rds-device-cal-50-cal.webp?v=1784725668","url":"https:\/\/dotkeys.net\/products\/microsoft-windows-server-2016-rds-device-cal-50-cal","provider":"DotKeys","version":"1.0","type":"link"}