For Linux hosts, the system always uses the Java delivery method. If the system cannot install the ActiveX control because ActiveX is turned off on the user’s system, it attempts to install Host Checker using Java. If the system successfully installs the ActiveX control, the control manages the installation of the Host Checker program. When a Windows user signs in to a device, the system attempts to install an ActiveX control on the user’s system. If Host Checker is not installed, the system attempts to install it using either an ActiveX or a Java delivery method or or Pulse Secure Application Launcher (PSAL). When you do, the system evaluates the realm-level option when the user accesses the sign-in page and then determines if the current version of Host Checker is installed on the user’s machine. Connect Secure automatically installs Host Checker-Enable automatic installation through the Users/Administrators > User Realms/Administrator Realms > Authentication Policy > Host Checker page of the admin console.
You can use two methods to install Host Checker on a user’s system: Otherwise, when the system evaluates the Host Checker policy, the user’s machine fails because the Host Checker client is not available to return a success status. If you implement any policy at the realm, role, or resource policy level that requires Host Checker, you must provide a mechanism by which the system or the user can install Host Checker on the client machine.
Specifying Host Checker Installation Options
0 kommentar(er)
