KB: No RDS license when you connect to an RDS farm in Windows Server 2012

A new KB (2916846) was released by Microsoft in regards to installing the RDSH role (rol-based, not scenario based) and possible issues with successfully acquiring RDS CAL’s from a RD Licensing server.

“…Assume that you install the Remote Desktop Session Host (RDSH) role service on a computer that is running Windows Server 2012, and then configure the computer to obtain licenses from a Remote Desktop Services Licensing Server. When you try to connect to the computer by using Remote Desktop or Remote App, you may receive an error message that indicates there is no Remote Desktop Services Client Access License..”

“…This issue occurs because the RDSH server is missing certificates when a connection arrives and it cannot request a license for that connection to the Licensing server…”

Source & download: http://support.microsoft.com/kb/2916846/en-us?sd=rss&spid=16526

KB: Best practices for setting up Remote Desktop Licensing across Active Directory Domains/Forests or Workgroup (2473823)

Microsoft has published a new KB article (KB2473823 ) covering Best Practices for Remote Desktop Licensing.

 

“…Question:
Can the RD Licensing (Terminal Server Licensing) server issue a Client Access License (CAL) to users or devices connecting to RD Session Host (Terminal Server) servers under any of the following conditions?

• RD Session Host servers are in an Active Directory Domain and RD Licensing server is in a workgroup environment
• RD Session Host servers are in a workgroup and the RD Licensing server in an Active Directory Domain
• RD Session Host servers and RD Licensing server are in different forests. No trusts exist (One-way or Two-way trust) between these forests
• RD Session Host servers and RD Licensing servers are in the same workgroup

Answer:
For both Per Device and Per User CALs issuance to work, the RD Session Host and RD Licensing server in any one of the following three configurations:

• Both in the same workgroup
• Both in the same domain
• Both in the trusted (Two-way trust) Active Directory Domains or Forest..”

For more information on these scenario’s see the KB article:
http://support.microsoft.com/kb/2473823/en-us?sd=rss&spid=14134

You cannot install RDS CALs automatically by using Windows PowerShell in Windows Server 2008 R2

A new KB article related to installing RDS CALs using Powershell was launched today.

Article ID: 2648662 - Last Review: January 11, 2012 - Revision: 1.0
You cannot install RDS CALs automatically by using Windows PowerShell in Windows Server 2008 R2

Consider the following scenario:

• You install the Remote Desktop Licensing (RD Licensing) role service on a computer that is running Windows Server 2008 R2.
• You install hotfix package 2618115 on the computer.
• You try to install Remote Desktop Services client access licenses (RDS CALs) automatically by using Windows PowerShell.
• You select Telephone or Web Browser as the connection method.
• The RD Licensing server does not have an active Internet connection.

In this scenario, you cannot install RDS CALs and you receive the following message:

Access to the object at RDS:\LicenseServer\LicenseKeyPacks\LicenseKeyPack is denied for the cmdlet New-Item. A license key pack could not be created because the input was not valid or permissions were insufficient.

At line:1 char:9

+ New-Item <<<< -path RDS:\LicenseServer\LicenseKeyPacks -ConnectionMethod PW

+ CategoryInfo : PermissionDenied: (:) [New-Item], AccessViolationException + FullyQualifiedErrorId : PermissionDenied,Microsoft.PowerShell.Commands.NewItemCommand

 

Cause
This issue occurs because the RD Licensing server unnecessarily checks whether it is authenticated or not. This behavior requires Internet access. Therefore, the authentication check fails if the RD Licensing server does not have an active Internet connection.

 

Source and hotfix: http://support.microsoft.com/kb/2648662/en-us?sd=rss&spid=14134