Then, restart the Remote Desktop Service. Path: HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services and HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\\.It triggers an Active Directory query to check for RDP profile settings: If the server has the RD Session Host Role installed, apply the following registry keys to enable the RCM legacy model. I think this issue is from Windows 2016 and you can try the registry settings shared in this link from Microsoft, hopefully this should be able to help you to solve your issue. The old server also has Remote Desktop Connection Broker and Remote Desktop Web Access installed, but we are not planning to use RemoteApp or Web based features so we didn't think we needed those.ĭoes this feature no longer work on Server 2022? Do we need the Connection Broker installed? Are there any other ideas to get this working?
Nothing runs, no error message, nothing at all.īoth servers are set up with Remote Desktop Licensing role service and the Remote Desktop Session Host role service. The old server is still up and running and this works fine. On the 2022 server this feature appears to not work at all. This worked well for simplicity as it automatically launches the program when they connect, and closes the connection if they close the program. We used the Remote Desktop Services startup environment tab in Active Directory to start the program when they logged in. We had a terminal server set up for remote users to access our database. We are in the process of upgrading from Server 2012 to Server 2022.
0 kommentar(er)
