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

Guidelines for installing the Remote Desktop Session Host role service on a computer running Windows Server 2012 without the Remote Desktop Connection Broker role service (2833839)

Microsoft has releases a FAST PUBLISH KB (2833839) regarding installing the Remote Desktop Session Host (RDSH) role without the Remote Desktop Connection Broker (RDCB) role. This server can be part of a workgroup or may even be configured as a Domain Controller.

Why is this important? With RDS/VDI in Windows Server 2012, the RD Connection Broker is more or less a mandatory component. I believe deploying RDS/VDI 2012 within an Active Directory Domain where the Domain Controller is not combined with RDS roles and where the RD Connection Broker is part of the deployment, is always the recommended way to go. However, I’ve seen many, many questions arise on TechNet Forum where people ask for deployments on a single server where the all RDS roles (including Active Directory) are installed on a single server and accepting all the downsides. Obviously intended for very small scenarios, where only 1 server is available. Second, many have asked for a deployment of RD Session Host without even using a Active Directory domain, and thus a workgroup. Third, many have asked for deployments where only the RD Session Host role is deployed (role based).

So here’s Microsoft's answer:
Guidelines for installing the Remote Desktop Session Host role service on a computer running Windows Server 2012 without the Remote Desktop Connection Broker role service

“…This article provides the guidelines to install and configure the Remote Desktop Session Host  role service on a computer running Windows Server 2012 without the Remote Desktop Connection Broker role service installed.
This configuration should only be used when it is the only option as the recommended configuration includes the Remote Desktop Connection Broker to provide access to the complete functionality with Remote Desktop Services. If a Domain Controller is available on a separate server, it is recommended to use the Standard Remote Desktop Services deployment wizard. This configuration is appropriate when there is only one server on the network. This server can be part of a workgroup or may be configured as a Domain Controller.
This configuration, will provide desktop sessions to users based on the number of Remote Desktop Services client access license (RDS CALs) installed on the server, but will not provide access to RemoteApp programs or the RDWeb site…”

Source: http://support.microsoft.com/kb/2833839/
(KB2833839)