Pulse secure Host Checker machine certificate was not found

[hescobar]

Migrating from NC to Pulse Secure.

When connecting using Pulse secure I receive an error, "Machine certificate was not found" The machine does have a machine certificate because it works fine with NC. The Host check policy fails at the user role. I can bypass the host checker and it connects just fine. I created a test host checker (Predefined OD Checker) to check a minimum version of Windows 10 and it works.  Some reason it just fails for the machine certificate. Any help would be appreciated. Thanks. 

[tbradbury · Accepted solution]

You might try re-creating the machine auth policy from scratch, rather than using the same policy that was used by NC.

Also, make sure you are using the latest version of ESAP - later versions include fixes for the Pulse client specific HC integrations.

If none of these help, open a TAC ticket.  They will want HC client-side logs.

[hescobar]

Updated the ESAP and nothing. Thanks.

[[email protected]]

Hmm... What is the pulse client version used? It seems like a bug to me on the pulse client side, as the same machine certificate is getting detected when NC is used.