Should we migrate the existing 2008 licenses to the 2012 server, and then attempt to 'upgrade' the licenses? Is this even possible? This answer to a server 2003 question says you can't even put older licenses on a newer server, but this seems to contradict the interoperability matrix put out by MS on technet. Can someone confirm that it is possible to migrate the licenses from a 2008 R2 server to 2012 R2? I just want to migrate the CALs. I know it's not possible to convert 2008 CALs to 2012 CALs.
By: Lacey Hartje
Summary: With the consumerization of IT, and the proliferation of devices in the workplace, it is now as important as ever that the licensing model you use is delivering the most value to your business. Our volume licensing programs can offer the flexibility and improved manageability to ensure your CAL licensing model is optimally matched with your organization’s needs. If your business needs change and you want to switch from your current method of Client Access Licensing (CAL) there is an opportunity to switch from Device to User CALs or vice versa. That opportunity comes when you renew Software Assurance (SA) on your CALs.
License your RDS deployment with client access licenses (CALs); 3 minutes to read +2; In this article. Applies to: Windows Server (Semi-Annual Channel), Windows Server 2019, Windows Server 2016. Each user and device that connects to a Remote Desktop Session host needs a client access licenses (CAL). Question is - do you need to move the Terminal Services (it is in fact now called Remote Desktop Services or RDS) Licensing Role to a new server or do you want to implement a new Terminal Server that will actually host the sessions? To move the Licensing Role, there is no 'smooth' transition process. Like with one click or so. The licensing for Server and Desktop OS's is different, for servers the license you have is the only one you need and as it is a VL one (as opposed to OEM that came with the server), you can transfer it to new hardware, just use the key from the VL portal with the new server, there is no paperwork to fill out.
Let’s say your Company chose license access to server software with Device Client Access Licenses (CALs) in the early days of the business because Device CALs made economic sense as you had more employees than devices. By licensing devices, you were guaranteed that all access to the server software was properly licensed and this was the most cost effective solution.
Now let’s fast-forward a few years. Your devices outnumber your employees. Put another way, each employee now has multiple devices; a PC, a laptop, a tablet, or a smart phone and you want them to be able to access your server software with ALL of these devices. The most cost effective licensing solution for this scenario is to license client access by User CALs.
Terminal License Server
If this mix between users and devices exists in your organization it’s a likely indication that you should consider switching from Device CALs to User CALs as it is more cost effective and applicable for your business needs.
How is this accomplished? Here are the key steps you’ll need to take:
- First, confirm that your CALs are covered by active Software Assurance (SA).
- Second, the switch is made ONLY at the time of SA renewal on the CALs. This licensing situation is outlined in the Product List. If you’re searching the Product List for this text, it’s called transitioning between User and Device CALs.
Client Access License (CAL) Decision Tool
In closing, volume licensing and active software assurance can give you the flexibility to switch between User and Device based CALs upon renewal of your SA coverage. Refer to the current Product List, contact our Pre-Sales/Licensing customer service team, or work with your reseller or account team if you have additional questions.
This is one scenario, and licensing situation. Each customer scenario can vary by deployment, usage, product version, and product use rights. Always check your contract, and the current Products Use Rights document to confirm how your environment should be fully licensed. The blogging team does not warrant that this scenario will be the right licensing solution for other similar cases.
We have several Windows 2008 R2 terminal servers and users who are on from about 6AM to 12Midnight. I need to move the RDS licensing to a new server. It will be a straight transfer from Windows Server 2008 R2 to Windows Server 2008 R2.I found this article about the general process:
http://technet.microsoft.com/en-us/library/cc730776.aspx
And this article about changing the licensing server on each of the RDS servers:
http://technet.microsoft.com/en-us/library/cc770585.aspx
Purchase Terminal Server License
What I need to know is this - can I do this while users are on the servers or will it disconnect them? Of course I'd like to do it during the day, but if this will cause issues I won't. If the process does not disconnect users, but temporarily stops new users from logging on, I could live with that.