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).
“…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…”