Terminal Services Client IP Address incorrect

Version 1

    Verified Product Versions

    Environment Manager 8.6Environment Manager 8.5Environment Manager 8.4Environment Manager 8.2Environment Manager 8.1Environment Manager 8.3Environment Manager 8.0Application Control 8.6Application Control 8.5Application Control 8.9Application Control 8.8Application Control 8.7Application Control 8.4Application Control 8.3Application Control 8.2Application Control 8.1Application Control 8.0

    Introduction

    When connecting from a host running Windows 8.1 / Windows Server 2012 R2 to a machine that is running any OS over RDP, AM Connecting device rules and EM Client IP Address conditions may not function as expected.

    Detail

    This issue can be recreated without AppSense installed.

    When connecting from a host running the Windows 8.1 / Windows Server 2012 R2 to any OS using RDP and calling the WTSQuerySessionInformation function to retrieve the WTS_Client_Address the AddressFamily member is 0 (AF_UNSPEC) and the Address returns a weird array of byte values. The Remote Desktop Services Manager console on Windows Server 2008 R2 also discovers the client address as unknown:



    When performing the same RDP connection from a Windows 7 / Windows Server 2008 R2 host the AddressFamily returns 2 (AF_INET) or 23 (AF_INET6) correctly and the byte array correctly represents the IP address of the RDP client:



    This is a Microsoft issue. Installing Windows Updates resolved the issue.