Windows Server 2008 R2 Remote Desktop Licensing Crack
I have a 2008 R2 Server with Remote Desktop Services installed. There are currently 6 computers at the location and only 5 of them can rdp in at a time. I ordered two Remote Desktop Services License Packs and installed one of them so far. I noticed before I installed the license that in the RD Licensing Manager there was nothing showing up except the standard 2000 Server Built-In licenses.
Microsoft did more than just change Terminal Services' name - it revamped the product. See why Remote Desktop Services is on our list of top 10 features in Windows Server 2008 R2. Enough with the redubs, though. Built on a VDI infrastructure, RDS brings with it a host of enhancements like fair share CPU scheduling and the Remote Desktop Connection Broker. There's a lot more, too (but we just don't have the space to list them all ).
After I installed the license now it shows the Per User license installed but I am still unable to connect with all 6 devices. When I generate the per user report it is showing 1 installed, 4 issued, and none available.CAL Version,CAL Type,Installed CALs,CALs in Use,CAL AvailabilityWindows Server 2008 or Windows Server 2008 R2,Per User,1,4,NoneI am not sure where to go from here, any help would be appreciated. Yes, the licenses were installed correctly and they show up in the Terminal Server Licensing manager, but I only see the one additional license in there and not the original five. I don't have any experience with 2k8 R2 Standard or per user licensing, everything else I have installed has been 2k8 R2 Enterprise with per device licensing. I guess what I really need to find out is why I can't see the original 5 licenses and if they are the same type of licenses that I just purchased.
- To install Remote Desktop CALs, you first need to install a Remote Desktop License Server. This is a role service of the Remote Desktop Services role on Server 2008 R2. Also Citrix XenApp relies on a RDS license server. Because what XenApp essentially does, is to extend the capabilities of the Microsoft Remote Desktop session host server.
- After 120 days, the RD Session Host server stops allowing these clients to connect unless a Remote Desktop Licensing server is available in the network. For the question 'if the old Terminal Service CALs are able to be converted to RDS licenses', Windows Server 2008 R2 needs Windows Server 2008 R2 RDS CAL and we can’t convert RDS CALs from lower version to higher version.
I did not set this environment up originally so I am just going off of what I can see on the server now and I am just assuming that it came with 5 licenses since the original four pc's were able to connect. All six of the current pc's can connect but right now only four concurrent along with the server desktop logged on. Once that threshold is reached it doesn't give any type of licensing error or anything but just instantly says it can't connect on the client. I looked in the registry on the clients to make sure there were no per devices licenses installed and there are not.When you buy 2k8 R2 Standard with a 5 pack do the licenses come separately or are they built in? If you're talking about the pack of 5 CALs that come with Windows Server 2008 R2 then those are server access CALs, which are actually different to RDS CALs. You can't track the usage of these CALs as Microsoft have gone with the 'honour system', where they provide you with a piece of paper and you write down the total amount of User and Device CALs (see below).I re-read your original post and you mentioned that you didn't see any RDS CALs in the RD Licensing Manager console. To me this says that the original person who set this server up never actually installed any RDS Per User CALs - this doesn't necessarily mean that RDS Per Device CALs weren't installed.
Server 2008 R2 Remote Desktop
The RD Licensing Manager console doesn't have the ability to generate reports for RDS Per Device CALs - you'll need to run the GeneratePerDeviceReport.vb s script to see if there are any Per Device CALs installed.If there are no RDS Per Device CALS then the next place to check after this would be the System logs - look for the time that you generated the report for the RDS Per User CALs and check for any warnings/errors. If the RD Licensing Manager role has been installed on a Domain Controller you will need to add the computer account for the DC to the Terminal Server License Servers group as well as the Network Service account.
Windows 2012 Remote Desktop Licensing Hack
Remember to add the Network Service account to the Terminal Server License Servers group as well seeing as the server is also a domain controller. You will then need to restart the Remote Desktop Licensing service then try generating a new Per User CALs usage report. Let me know how you go.As to your second question - I have seen in the past where workstations were able to connect to RDS servers without any licenses installed. The RDS server did get to a point where it then started refusing client connections due to the missing CALs.