Remote Desktop Services Licensing Oddness
Hi all, hoping someone might have some insight on this. I configured a new remote desktop services setup on Windows Server 2025. Everything appears to be working just as it did in our previous RDS environment which was on 2016, and it seems like the licensing is/should be working properly, but I keep getting a warning when logging in on the broker/license server that a license will expire soon, etc. The license diagnoser seems to show the same or a similar warning. I want to ensure that we won't have any disruption in service. I believe I have everything configured properly, but maybe I've missed something? Or is this some sort of red herring message due to the built in temporary license? In RD licensing diagnoser I see this message: In the licensing manager everything appears like it should be good to go, though: Even shows the licenses being assigned to active connections: The license server is set within the RDS config as such: Thanks in advance for any help or advice. I've tried looking at everything I could find off general searching.
Server 2019 RD-Connectionbroker Rolle broken after Windows Update
Hi, we have a RD session deployment with 1 Connection Broker/Web Access, 8 Session Hosts for RD and 1 Session Host for Apps and 1 License Server. All Servers are VM´s on VMware running Server 2019 DC running perfect for a year now. Some Weeks ago after an Windows update i noticed that i was no longer able to see and configure the deployment in Server Manager on the Connection Broker (I can see and in parts manage the deployment from other Servers Server Manager) Deployment is still working and users are able to connect, load balancing also works. On The Connection Broker it just says: "Es ist keine Remotedesktopdienste-Bereitstellung im Serverpool vorhanden. Führen Sie zum Erstellen einer Bereitstellung den Assistenten zum Hinzufügen von Rollen und Features aus, und wählen Sie die Installationsoption "Remotedesktopdienste" aus." Powershell get-rdserver output: PS C:\Windows\system32> get-rdserver get-rdserver : Der RD-Verbindungsbrokerserver ist nicht verfügbar. Stellen Sie sicher, dass Sie eine Verbindung mit dem RD-Verbindungsbrokerserver herstellen können. In Zeile:1 Zeichen:1 + get-rdserver + ~~~~~~~~~~~~ + CategoryInfo : NotSpecified: (:) [Write-Error], WriteErrorException + FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,Get-RDServer Eventlog: ID1280 "Die Remotedesktopdienste konnten keine Verknüpfung mit dem Verbindungsbroker auf dem Server "VSTSBro01.xxx.de" herstellen. Fehler: Die aktuelle asynchrone Nachricht wurde vom asynchronen Verteiler gelöscht, da eine neue Nachricht vorhanden ist, die die aktuelle Nachricht überschreibt." ID2056 "Der Remotedesktop-Verbindungsbrokerserver konnte die Ziele für den Anbieter "NULL" nicht aus der Datenbank auflisten. Name der in einem Pool zusammengefassten virtuellen Desktopsammlung: NULL Fehler: Die Anmeldung bei der Datenbank ist fehlgeschlagen." Things i tried so far: Configuring Connection Broker HA, WID got successfull migrated to dedicated VM with SQL Server But cause the connection Broker is not available i couldnt add a second connection broker. Restoring Connection Broker VM from Backup, after restore i could see and manage the deployment again but had to reboot the VM after Domain Trust reset. Update got installed with that and Problem is the same again. Update that got installed at that time: Edge Stable 103 x64 Build 103.0.1264.49 2022-07 Cumulative Update for Windows Server 2019 for x64 based Systems KB5015811 I guess something broke the connection to the WID and its no longer able to load the information. But why is it able to show the deployment on other servers? First pic Broken CB second pic other Server Any Ideas how to fix that? Thx!
Remotedesktop RDWeb Disable Multimonitor
Havent found anything regards disabling Multi Monitor Found following in the registry of the connection broker server: Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Terminal Server\CentralPublishedResources\PublishedFarms\XXXX\DeploymentSettings DeploymentRDPSettings redirectclipboard:i:1 redirectprinters:i:1 redirectcomports:i:0 redirectsmartcards:i:1 devicestoredirect:s:* drivestoredirect:s:* redirectdrives:i:1 session bpp:i:32 prompt for credentials on client:i:1 server port:i:3389 allow font smoothing:i:1 promptcredentialonce:i:0 gatewayusagemethod:i:0 gatewaycredentialssource:i:0 use multimon:i:1 full address:s:XXXXX gatewayprofileusagemethod:i:1 videoplaybackmode:i:1 audiocapturemode:i:1 Changing use multimon:i:1 to: use multimon:i:0 does not affect the connection to the session host, still opens with mulitmonitor.. Has anyone encountered this configuration and made it work? Help appreciated.
