Older clients might have problems with these security settings (like Network Level Authentication - NLA) These are my specific settings, you should change the parameters based on your experience or leave them at their default values.
User profile disks were not needed in my environment.Īfter the creation, there are some things that should be changed in the Collection properties (Server Manager > Remote Desktop Services > Collections > Collection Name): In a production environment a custom group should be used to control the number of permitted users. Make sure you select the server by moving it to the right with the arrow.
This is also pretty straight forward stuff. Server Manager > Remote Desktop Services > Collections > Tasks > Create Session Collection Now on to the last step: Create a custom device collection. With RD Licensing Diagnoser you can check for potential errors (can be opened through Server Manager > Tools > Remote Desktop Services). HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TermService\Parameters\LicenseServers The license server can be also set through the registry: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\RCM\Licensing Core This registry key worked wonderfully though: I had problems with the licensing mode not being applied properly. Server Manager > Remote Desktop Services > Overview > Tasks > Edit Deployment properties In a production environment, usually there is a separate server hosting the RDS Licensing service. Two things are needed in order for licensing to work properly: The license server and licensing mode. The three roles (RD Connection Broker, RD Web Access and RD Session Host) will be installed.Īfter the installation a license warning will be shown in the Notification Center. The server should be automatically selected. Session-based deployment enables multi-session support on the server. I went for the Quick Start because my deployment is fairly basic. Start by adding the RDS role through Server Manager. It was a pretty straightforward installation, but minor things might work differently compared to previous versions of Windows Server (I was migrating off Windows Server 2012 R2). I got tasked with installing a brand new Windows Server 2019 with the Remote Desktop Services (RDS) role.
0 kommentar(er)
