VERY important to NOT accept "Windows XP style scaling" which can be the default.
Requires Remote Desktop 8.1 protocol which is an update for Windows 7 though comes on Windows 8.1 and above. Windows 7 did not ship with the correct scaling pieces: requires updates to scale correctly. The first issue was recognizing that we had Windows 7 rather than Windows 10. It seems like this user still has the clients open when they collected logs which can cause this.
Ultimately, the RoyalTS did perform as it was supposed to but had important prerequisites. Re: Remote Desktop Client on Windows 7 James Bliss The Logs are incomplete (no connection related Logs, and Feed subscription Logs without anything useful). RoyalTS worked flawlessly on Win 10 client but would not scale on the Thinkpad.įinally, was able to debug the problem with screen resolution on the new Carbon Thinkpad. Unfortunately, our Remote Desktop application runs on Win Server 2008R2 at fixed 1600x900 and not DPI aware. Decision was to rollback to Win 7 for easier system-wide maintenance. Onboarding new high resolution Thinkpads with native screen resolution of 1920x1080. The HTML 5 Remote Desktop Web-Client is available in newer versions of Windows Server that is configured as a Remote Desktop Services Deployment at no additional cost. The client has initiated a multi-transport connection to the server 192.168.13.201. Hoping this might help another struggling sole. The Remote Desktop web client enables users to access the enterprise Remote Desktop infrastructure through a compatible web browser. For example, EventID 1102 occurs when a user connects to a remote Windows Server RDS host or a Windows 10/11 computer with RDP enabled (desktop Windows editions also support multiple simultaneous RDP connections).