When you install the role, by default, you have a 120-day grace period that Microsoft gives you to properly license the server for use as an RDS installation. If you are using a server in a lab environment, most likely, you are not going to license this type of server outside of production.
The Remote Desktop Services license server issues client access licenses (CALs) to users and devices when they access the RD Session Host. You can activate the license server by using the Remote Desktop Licensing Manager.
Rds Cal License Keygenl
A client access license (CAL) is needed for each user and device that connects to a Remote Desktop Session host. An RDS licensing server is needed to install, issue, and track RDS CALs. When a user or a device connects to an RD Session Host server, the RD Session Host server determines if an RDS CAL is needed.
Microsoft has time and again heard from customers that license management should focus on simplification to scale deployments. Therefore, it has focused on improving management of Remote Desktop (RD) Licensing servers and entitlement through Active Directory (AD).
After installing and configuring the Remote Desktop Services (RDS) role in Windows server, a license server needs to activated. Without an activated license server, clients will fail to connect to the Session Host server when the licensing grace period expires. To activate the license server follow the instructions below.
I am facing same problem. We had purchased Windows Server 2022 user cals through CSP. In 365 Admin Center - your products i can see my purchased windows server 2022 cals but no license key can be seen. Since its purchased through Cloud there has been no license no & authorization no for it. Please help how do i activate those cals on my Win Svr 2022 std.
For Windows Server CALs there is no key provided since in Windows Server there is no place to enter any key for CALs since Windows Server 2003, and there is no technical tracking of CALs. A Windows CAL is only something that the customer needs to have from a licensing perspective, the only time somebody would look for it would be in case of a license audit, where the customer then can show they own this product.
I activated the Win7 VM I am using for the template. Obviously I will need to refresh these destops in the pool as I install WIndows updates and new applications. But it appears that it deactivates the licenses on the clients in the VDI pool everytime I run the Recreate All Virtual Desktops???
To be licensed to access a Windows desktop OS VM on a server - each client access device needs a Windows VDA license to be licensed for the VM. Windows VDA is included with Windows Client SA and Windows Intune, so if you have either of those licenses you are good and already have Windows VDA coverage.
As far as activation of the VM - you should be using volume license media from VLSC and key to activate the VM. Through VL Windows 8, Windows 7 and WIndows Vista all activate using KMS and MAK. VLSC media comes with your KMS client activation key built into the Windows OS image from VLSC. You can change if from KMS to MAK if needed.
Is that the same if you have per user or per device licensing on EA or SA? What happens if a user has a per user EA license assigned but no physical Windows desktop, say they have a Mac or are on BYOD?
How are you delivering the desktops VMs from the server to the clients? If you are using Remote Desktop Services Opens a new windowto deliver the OS to the client - yes you need a RDS CAL on top of the Windows VDA license.
OK so im confused. In a virtual environment do you need to purchase a volume license use it for each client install (meaning youre paying for window 7 on every single vm) AND have a VDA for each person also accessing that install?
To use VDI (Virtual Desktop Interface) you need and OS license (either a workstation license with Software Assurance or VDA or Intune [combined with a desktop OS license]) and a connection method license, such as RDS or VMWare View or XenDesktop.
So say someone is using a windows 7 desktop without SA (so weve already purchased that client license) to access a dedicated windows 7 VM (have to purchase another license for that) which means theyd need a VDA license, which is not only one shot but a yearly repetitive cost, in addition to the per client license of the way its being access (RDP, VMWARE, CITRIX) is this correct?
So, technically if you had a linux device or device without a Windows OS, then technically your're not purchasing the license twice. But if you have an OEM Windows Pro license you can add SA and not purchase Windows VDA.
Licensing a VM on a server as compared to a physical OS is a completely different set of requirements. The OEM license has a lot of restrictions on licensing and SA and Windows VDA are Microsoft's licenses options for a more flexible way to use the Windows OS.
The Windows VDA license (or through Windows Client SA) is the license required to access a Windows desktop OS VM from a server. The Windows VDA/SA license is not available under SPLA (as to provide a Windows desktop OS VM from a sever as a service). However, you can provide a Windows Server VM as a server to a customer through RDS.
You can find an OEM version of Windows 8 Pro for $150. However, the OEM/FPP license is not to be used as a VM license for a server. Technically you can 'assign' it to a server, it would be for local use only and any client devices that accesses the VM would require the Windows VDA license.
Only the primary user of the licensed device may remotely access his/her device. With server hardware, there is no primary user, therefore is considered a shared device. If you were to assign a retail copy of Windows desktop OS (XP, Vista, W7, W8, etc) to a server - the retail copy of Windows could only be used on the device. The retail license does not permit remote access from any user other than the licensed user. The Windows VDA would be the license required.
I hate to drag this back up but the one question I have is still not answered. If I have 5 Windows 7 VM's on a Server (that is backed by Server 2012 R2 Datacenter which does not matter), then how do you license *those* virtual machines? I understand the access rights licenses for example say my user has a win 8.1 upgrade with SA assigned to them.
You dont have to have RDS licenses if you used windows 8.1 VMs on the Server 2012 R2 Datacenter edition and connected with those VM's using those VM's built in Remote Desktop service and not through the server's services. You can change the listening RDP ports to 3391, 3392, 3393, 3394 etc for the VMs and call them directly from your devices with RDP client (windows or Mac).
Thank you Pete for taking the time to answer. Question where did you get that an OEM license is in use? I didn't say anything about using any OEM licenses. They are using VDA subscriptions for the Windows 7 Pro - ohhh you took Pro as being OEM vs Win 7 Enterprise - that's it isn't it? Sorry should have said Win 7 Enterprise VM's. Makes sense now. I'm in agreement with all the feedback so far - aka they need a VDA subscription and an RDS CAL however - I can't find anywhere in any licensing guide or website or document from Microsoft that says they need an RDS CAL even when not using RDS Services Role. I've also explained to them that this model is not common and not the suggested path so they ask for a document that compares this method to a full RDS pooled method of which I can't find anything either so anyone with any details on comparing this single non RDS Services method against an RDS pooled method would be helpful. 2ff7e9595c
Comentarios