If Host Checker is configured with an interval other than '0' Windows 10 users get disconnected at the second scheduled Host Checker interval due to Host Checker timing out and terminating the session.
This issue only affects Windows 10 users who login to a realm and/or get assigned a role where Host Checker is configured to check the compliance of the machine .
The User Access Log will show the following messages:
info - [184.108.40.206] - pulsesecure-test(LDAP)[PulseSecure-Test] - 2016/06/22 15:44:16 - System process detected a Host Checker
time out on host 220.127.116.11 for user 'pulsesecure-test' (last update at 2016-06-22 15.36.51 -0400 EDT).
info - System(LDAP) - 2016/06/22 15:44:16 - Session for user pulsesecure-test on host 18.104.22.168 has been terminated.
info - [22.214.171.124] - pulsesecure-test(LDAP)[PulseSecure-Test] - 2016/06/22 15:44:16 - Closed connection to APUser1 port 3389
after 420 seconds, with 8339827 bytes read (in 2972 chunks) and 31366 bytes written (in 246 chunks)