Users "Status" fields blank on RDS with Windows Server 2025
Hi, we have two RDS Server with Windows Server 2025 installed (In-Place Upgrade from Server 2019). In Task-Manager under the "Users" Tab all fields of the "Status" row are blank. We cant see if a user is connected or disconnected. In cmd with "query user" it works. Someone else discovered this problem?
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.
Remote Desktop Services Deployment fails with exceptions
I'm trying to deploy Remote Desktop Services on a single server on Windows Server 2019 Standard. I've tried both Standard Deployment and Quick Start with a Session-based desktop development but I'm getting the following error during the installation: Unable to add server REMOTEAPP.AD.DOMAIN.COM to the list of servers on the RD Connection Broker server REMOTEAPP.AD.DOMAIN.COM..Exception of type 'System.Runtime.InteropServices.COMException' was thrown. I searched for some hint about this problem but I had not find anything useful. I cannot even find any useful log into the events log, and I tried one more time after reinstalling the server from scratch. Could you help me please? Thank you very much!
TSplus as an alternative to RDS without paying RDS license fees to microsoft
Hello, We are evaluating whether to use TSplus (https://www.terminalserviceplus.eu/) as an alternative to Microsoft RDS/Terminal Server. According to TSplus we can not install or uninstall the RDS role, so we do not use RDS CALs and use TSplus CALs. This way it would not be necessary to pay for Windows Remote Desktop licenses. Is this correct? I can't find any information from Microsoft about it reading documentation. As I see it is correct that using TSPlus without installing Microsoft RDS it would not be necessary to pay Remote Desktop licenses. Could someone confirm me that it is so?
Windows Server 2025 Terminal Servers - start menu pinned icons
I'm designing the config for some terminal servers running Server 2025. I want to pin specific icons to the start menu. In Server 2022 (or Windows 10), this was simply a process of setting up the reference machine how I wanted it, then Export-StartLayout -Path "C:\Export\MStartMenuLayout.xml" to generate the config file, whcih was then applied using the GPO Computer Configuration\Policies\Administrative Templates\Start Menu and Taskbar\Start Layout - this worked fine. On Server 2025 (and Windows 11), however, it appears that this doesn't work the same any more. Although the export command works, it generates a JSON file now rather than an XML. OK, so I saved the file with the JSON extension, and copied the old GPO, amending the name of the config file to point to the new one. However, it still doesn't work and this documentation: https://learn.microsoft.com/en-us/windows/configuration/start/layout?tabs=intune-10%2Cintune-11&pivots=windows-11 Would appear to indicate that it can only be done using Intune. If it was Windows 11 I could do that, but as this is Server 2025 it isn't an option - Intune cannot manage server OSs even if I wanted to do that. Can anyone suggest any alternative methods of doing this? All I want to do is configure a common set of pinned apps for all users - I'm not bothered about configuring any other aspects of the start menu as the defaults are OK. ThanksRDS Farm with FIDO2 Key
Hello everyone, I'm trying to install an RDS farm with fido2 (Yubikey). I think I have created the conditions. The farm is onPrem (hybrid joined), the FIDO2 key is registered in Entra. The farm works correctly with normal credentials. However, setting up the FIDO2 key is giving me a headache. If I log in directly to one of the session hosts, FIDO2 works. But if I want to log in via the session broker, as it should be. I am connected to the session broker as a host and not forwarded to the hosts. But I only found this out by chance when I added the user to the Remodesktopuser group on the broker as a test. Otherwise you just get the message: "Access to the session was denied" and the broker's event log says "Couldn't find the file" #################### redirectclipboard:i:1 redirectprinters:i:0 redirectcomports:i:1 redirectsmartcards:i:1 devicestoredirect:s:* drivestoredirect:s: session bpp:i:32 prompt for credentials on client:i:1 server port:i:3389 allow font smoothing:i:1 promptcredentialonce:i:1 gatewayusagemethod:i:2 gatewayprofileusagemethod:i:1 gatewaycredentialssource:i:4 full address:s:RDS-TEST-BR.xxxxxxxxxxxxx gatewayhostname:s:rds-test.xxxxxxxxxxxxx workspace id:s:RDS-Test-BR.xxxxxxxxxxxxx use redirection server name:i:1 loadbalanceinfo:s:tsv://MS Terminal Services Plugin.1.Test use multimon:i:1 alternate full address:s:RDS-TEST-BR.xxxxxxxxxxxxx screen mode id:i:2 desktopwidth:i:800 desktopheight:i:600 winposstr:s:0,3,0,0,800,600 compression:i:1 keyboardhook:i:2 audiocapturemode:i:0 videoplaybackmode:i:1 connection type:i:7 networkautodetect:i:1 bandwidthautodetect:i:1 displayconnectionbar:i:1 enableworkspacereconnect:i:0 disable wallpaper:i:0 allow desktop composition:i:0 disable full window drag:i:1 disable menu anims:i:1 disable themes:i:0 disable cursor setting:i:0 bitmapcachepersistenable:i:1 audiomode:i:0 redirectlocation:i:0 redirectwebauthn:i:1 redirectposdevices:i:0 autoreconnection enabled:i:1 authentication level:i:2 prompt for credentials:i:0 negotiate security layer:i:1 remoteapplicationmode:i:0 alternate shell:s: shell working directory:s: gatewaybrokeringtype:i:0 rdgiskdcproxy:i:0 kdcproxyname:s: enablerdsaadauth:i:1 username:s:yubikey@xxxxxxxxxxxxx ####################
Maximum number of concurrent shells for the Remote Desktop Services plug-in has been exceeded
Server 2019 Standard (2 each) When opening Server Manager, it takes quite awhile to read the RDS servers and eventually comes back for the local server with the error: Maximum number of concurrent shells for the Remote Desktop Services plug-in has been exceeded. Restart Server Manager, and then try again. I have increased the MaxConcurrentUsers to 2147483647, as well as the MaxShellsPerUser just to make sure: On a Server 2012 R2 server, I have both of the 2019 servers in the server list and open the RDS portion of server mgr and do NOT get this error. It ONLY happens when opening RDS in Server Mgr on the 2019 servers. I have scoured all over the Inter-webs for an answer to no avail. Anyone have a fix for this?Login failure from tssdis.exe on RDS server
Remote desktop server in AD environment [Windows Server 2019 standard, running RDweb, RDG, and session host, etc] periodically has service tssdis.exe (remote desktop session broker) failing to login, Event IDs 4648 and then 4625 about half a dozen times before stopping. This doesn't appear to affect any users, but I can't find anything online addressing it or if it's something that needs to be fixed. Some other people have reported the problem but not the solution, such as here: https://social.technet.microsoft.com/Forums/windowsserver/en-US/26e48e81-1400-4f8c-aef2-df03143fa211/login-through-tssdisexe Below are two exports of the event IDs (sanitized) This is the 4648 A logon was attempted using explicit credentials. Subject: Security ID: NETWORK SERVICE Account Name: SERVERNAME$ Account Domain: DOMAIN Logon ID: 0x3E4 Logon GUID: {10b9db0d-f9e0-e3ab-8c95-7dcb4ec5b3c7} Account Whose Credentials Were Used: Account Name: SERVERNAME Account Domain: DOMAIN Logon GUID: {00000000-0000-0000-0000-000000000000} Target Server: Target Server Name: SERVERNAME.DOMAIN.local Additional Information: SERVERNAME.DOMAIN.local Process Information: Process ID: 0x17c8 Process Name: C:\Windows\System32\tssdis.exe Network Information: Network Address: fe80::xxxx:f30a:xxxx:xxxx Port: 49667 This event is generated when a process attempts to log on an account by explicitly specifying that account’s credentials. This most commonly occurs in batch-type configurations such as scheduled tasks, or when using the RUNAS command. This is the 4625: An account failed to log on. Subject: Security ID: NULL SID Account Name: - Account Domain: - Logon ID: 0x0 Logon Type: 3 Account For Which Logon Failed: Security ID: NULL SID Account Name: SERVERNAME Account Domain: DOMAIN Failure Information: Failure Reason: Unknown user name or bad password. Status: 0xC000006D Sub Status: 0xC0000064 Process Information: Caller Process ID: 0x0 Caller Process Name: - Network Information: Workstation Name: SERVERNAME Source Network Address: fe80::xxxx:f30a:xxxx:xxxx Source Port: 50798 Detailed Authentication Information: Logon Process: NtLmSsp Authentication Package: NTLM Transited Services: - Package Name (NTLM only): - Key Length: 0 This event is generated when a logon request fails. It is generated on the computer where access was attempted. The Subject fields indicate the account on the local system which requested the logon. This is most commonly a service such as the Server service, or a local process such as Winlogon.exe or Services.exe. The Logon Type field indicates the kind of logon that was requested. The most common types are 2 (interactive) and 3 (network). The Process Information fields indicate which account and process on the system requested the logon. The Network Information fields indicate where a remote logon request originated. Workstation name is not always available and may be left blank in some cases. The authentication information fields provide detailed information about this specific logon request. - Transited services indicate which intermediate services have participated in this logon request. - Package name indicates which sub-protocol was used among the NTLM protocols. - Key length indicates the length of the generated session key. This will be 0 if no session key was requested.License Server Configuration Details | Windows Server 2022
Dear Guys, I installed Windows Server 2022 and added the RDSH role. I changed the RDSH license server to be "localhost" and then I noticed as per enclosed screenshot that the License Server Configuration Details in the licensing diagnoser shows that the windows version is 2019! So, Is it a typo problem or there is something else wrong ?! Please advise!
