When I re-run that, it finds the server in "RD Connection Broker". To create a deployment, run the add roles and features wizard and select the remote desktop services installation option." On that section, it shows the server under "Servers", but on Overview, it says "A remote desktop services deployment does not exist in the server pool.
On Server manager, it has a Remote Desktop Services tab. I tried uninstalling and reinstalling RDP roles.
SCREENFLICK REMOTE NOT CONNECTING LICENSE
That issue no longer shows up, but it still shows the other issue: "The Grace period has expired but the RD Session Host has not been configure with any license servers." The license server is active on the RDP server, and in the registry it lists the server name under license servers. I couldn't find a way to do it through the GUI, so I went into the registry and changed it from '5' (not set) to '4' (Per User). One issue the RD Licensing Diagnoser listed was that the Licensing Mode was not set. They show up fine in License Manager, but users still can't make RDP connections (not even domain admins). So I installed the license manager on the RDP server itself and migrated the licenses to that. When the CALs arrived, I set up a license manager on the domain controller, but the RDP server didn't connect to it to get the licenses. By the time I received the CALs, the grace period had passed and users weren't able to connect anymore on RDP. At that time, we did not have CALs yet, so I could not connect it to a license manager. We set up a 2022 Server as a RDP server for a few users to connect to as virtual desktops. Hi, I've been struggling with this for days.
0 kommentar(er)
