Forum Discussion

ralvarezOES's avatar
ralvarezOES
Copper Contributor
Oct 09, 2025
Solved

Replacing our Server 2016 RDS with Server 2022 RDS

Hi All,

I have a Server 2016 terminal server.  I set it up a while ago obviously, and I have 10 2016 RDS CALS installed in the RD license manager.

We are part of a domain, and I have a group policy assigned to our current RDS server with lots of user options like session limit, printer redirection, max profile size, etc.

 

I created a new Server 2022 VM and installed the RDS role and all it's features.  But for some reason, it doesn't appear to be configuring the services.

  1. I add the roles via Server Manager
  2. once installed, the computer reboots
  3. when the server comes back up, Server Manager starts and says the install is complete.

But when I go to the Remote Desktop services section in Server Manager, I get this message:  "A remote Desktop Service deployment does not exist in the server pool.  To create a deployment, run the Add Roles and features wizard and select the Remote Desktop Services installation option."

From looking around on the Internet, at step 3. there should be a configuration step where Server Manager starts and configures the RD gateway, license manager, etc.

I also found some articles on the Internet about disabling IPv6 or making sure the server is a member of a domain.  I've already tried those things and it's still not helping.  I also removed all the Roles and readded, but it still behaves the same.  The configuration step doesn't start on reboot and no RDS server.  I also installed a web certificate and installed it on the server from my CA.

Is there a better way to do this?  I haven't worked with RDS in a long time. 

Here's some event viewer messages

Event ID 1306 Remote Desktop Connection Broker Client failed to redirect the user domain\administrator. Error: NULL

Event 102 The Remote Desktop Gateway service requires a valid Secure Sockets Layer (SSL) certificate to accept connections. Ensure that you have obtained a valid SSL certificate, and then bind (map) the certificate by using RD Gateway Manager. For more information, see "Obtain a certificate for the RD Gateway server" in the RD Gateway Help. The following error occurred: "259"

Event ID 2056  The Remote Desktop Connection Broker server could not enumerate the targets for the provider named NULL from the database.

Pooled virtual desktop collection name: NULL
Error: Logon to the database failed.

Event ID 85  The Remote Desktop license server could not be registered as a service connection point in Active Directory Domain Services (AD DS). Ensure that there is network connectivity between the license server and AD DS. To register the license server as a service connection point in AD DS, use Review Configuration in the RD Licensing Manager tool.

  • Uninstall all the components or create a new VM.

    It sounds like you are tying to install each role separate.

    Click Add roles and features

    Select Remote Desktop Services installation (NOT "Role-based or feature-based installation")

    Choose your deployment type:

    Quick Start - Good for single-server deployments (all services on one server)

    Standard Deployment - Better for multi-server setup

     

    Now it should work how you expect.

     

2 Replies

  • dz890's avatar
    dz890
    Brass Contributor

    Uninstall all the components or create a new VM.

    It sounds like you are tying to install each role separate.

    Click Add roles and features

    Select Remote Desktop Services installation (NOT "Role-based or feature-based installation")

    Choose your deployment type:

    Quick Start - Good for single-server deployments (all services on one server)

    Standard Deployment - Better for multi-server setup

     

    Now it should work how you expect.

     

Resources