It looks like there's some renewed interest in resolving this issue. If you're still experiencing the error when trying to connect to an app via RDWeb on Windows Server 2016, here are some steps to troubleshoot:
1. Verify Licensing
Ensure you have the correct licensing setup:
Server License: Required for the Windows Server.
User CALs (Client Access Licenses): Needed for each user accessing resources. You can buy these as user CALs for better flexibility.
RDS User CALs: Required for each user connecting to the RDS.
A Server license (one per copy of Windows Server 20XX)
Service User or Device CALS (most of the time people get user CALs) you would need one per each user accessing resources from servers on your network.
RDS User CALs (again one per connection) so if you have 10 people accessing RDS but only 5 ever connect at a time you can get just 5 CALs
Once you have the RDS CALs you would deploy a RDS licensing server (if you only have one server you can install the role on there)
Import your RDS CALs into the licensing manager
In your RDS configuration you would tell it which licensing server to use.
It looks like there's some renewed interest in resolving this issue. If you're still experiencing the error when trying to connect to an app via RDWeb on Windows Server 2016, here are some steps to troubleshoot:
1. Verify Licensing
Ensure you have the correct licensing setup:
Server License: Required for the Windows Server.
User CALs (Client Access Licenses): Needed for each user accessing resources. You can buy these as user CALs for better flexibility.
RDS User CALs: Required for each user connecting to the RDS.
Make sure the RDS Licensing server is correctly configured and available:
Open the Remote Desktop Licensing Manager.
Verify that the server has been activated.
Ensure that the RDS CALs have been properly installed.
Configuring the Licensing Server:
In Server Manager, click on Remote Desktop Services.
Click on RD Licensing.
Add the selected server if it isn’t listed.
In the deployment properties, specify the licensing mode and the licensing server.
3. Firewall Settings
Ensure that your Windows Firewall or any network firewall between the client and server has the necessary ports opened for RDS:
Port 3389 (default RDP port) must be open.
Any specific ports that you've configured.
4. Event Logs
Check the Event Viewer for clues: []Navigate to Windows Logs > Application and Windows Logs > System. []Look for any errors or warnings that might provide more details about the connection issue.
5. Network Connectivity
Ensure that the network connectivity between the client and the RDS server is stable:
Check for any network inconsistencies or packet drops.
Ensure that DNS resolution is functioning correctly.
6. Group Policy Settings
Make sure that there are no conflicting Group Policy settings that might affect the RDS configuration: []Open Group Policy Management. []Check for any policies that could affect RDS settings and adjust accordingly.
7. Compatibility and Updates
Ensure all servers and clients are fully updated. Sometimes compatibility issues can cause problems if the software is outdated.
8. Test with another App
Try connecting to a different published app to see if the issue is isolated to the Calculator app.
Summary
By ensuring proper licensing, checking firewall settings, verifying server configuration, and examining event logs, most RDWeb connection issues can be diagnosed and resolved. If all else fails, it might be beneficial to contact Microsoft Support for further assistance. Let us know if this helps or if you have any more details about your specific setup!