- #2012 r2 remote desktop services licensing how to
- #2012 r2 remote desktop services licensing install
But not all, so we’ll configure this too. I guess in that in most of these small deployments, having a self generated certificate is acceptable. In 2008R2 you could manage the settings of a RDSH farm through the use of group policies, and this is still possible in 2012R2:Īlmost everything can be configured here, the RDP certificate is one of those things you cannot do using Group policy. Won’t work, they have rewritten the cmdlets to only use the new way.
#2012 r2 remote desktop services licensing how to
Ok, so how to configure this bare bone config? Powershell? They’ve removed the management consoles we know from 2008, and added a more centralized server management. Under the hood, much of the settings are the same as in 2008R2. Ok, no go here, which makes sense since the way 2012 and up works completely different than 2008(R2). Great, now lets configure the service using Server manager: Install-WindowsFeature –Name RDS-RD-Server -Restart Install-WindowsFeature –Name RDS-Licensing It’s also possible to do this using powershell:
#2012 r2 remote desktop services licensing install
It also offers to install the management features:īut these are mostly for analyzing licensing and configurering the license server itself.
Next, and one can select Remote Desktop services:Īnd here we can select the desired roles, in this case RDSH and licensing. The trick is, don’t select remote desktop services during the adding of the role, but the regular role-based of feature-based installation: Uh oh, no next possible without assigning a connection broker.īut it is possible to just install the RDSH role without doing from a connection broker, or using a connection broker. The default path most take leads to opening the server manager, choosing add role to install and choosing Remote Desktop Role: In some cases, such a simple setup can be quite useful, in this blog I’ll explain a way to do this. This option appears to have been removed in 2012 and later.
The part I liked about the way 2008(R2) worked, one could use only RDSH and the licensing role to create a really simple configuration. With a session host collection configuration. When following all the howto’s on the internet, you’ll always end up with at least four roles installed on one or more servers (RDSH, RDWI, CB and RD licensing). Using a connection broker a web interface is overkill, and why install these roles without needing them. But what about a small environment? Or you just need a stand-alone server from which to manage the rest of the network. In most larger environments you usually want a complete installation with a connection broker, web interface and gateway service.
0 kommentar(er)
