This article describes an issue where Single Sign-on (SSO) for Windows Terminal Services access method (WTS) does not work when the client machine is running Windows 10 Anniversary Edition (Build 1607 or higher, codenamed Redstone).
Problem or Goal
When an end-user, running Windows 10 Anniversary Edition as the client endpoint, accesses a WTS bookmark (with SSO configured) to RDP to a backend resource instead of automatically passing credentials the user will be prompted for credentials as shown in the below image.
This issue is due to incompatibility between the SSO mechanism used by the Pulse Secure's WTS client component and Microsoft’s Windows 10 Anniversary Edition.
Even though SSO fails the user should be able to manually enter their credentials and use the RDP session. Alternatively, if SSO is important you may temporarily configure Pulse Secure L3 VPN access method instead of WTS access method, then use your preferred RDP client to access the backend resource.