Related Articles

KB44500 - Implications of disabling to the "Store host checking evaluation results" Feature on Pulse Connect Secure/Pulse Policy

KB9628 - How to verify that a Host Checker policy is enforced correctly

KB44643 - Host Checker fails after upgrading ESAP version to 3.7.1 or 3.7.2 or 3.7.4 from any previous ESAP version on macOS endpoints.

KB44243 - Host Checker fails after upgrading to ESAP version to 3.4.3 or higher on macOS endpoints

KB43875 - Authentication with Pulse Desktop client fails with "General Error 1300" when Host Checker is configured with a machine certificate policy that is enforced on the role.

KB43670 - Host checker fails to detect Symantec Endpoint Protection 14.0.3x on macOS

KB44635 - After upgrading to macOS 11.0 (Big Sur), compliance check fails with "FileVault 10.16 does not comply with policy. Compliance requires drives to be encrypted"

KB44629 - Predefined Operating System (OS Check) for macOS Big Sur fails

KB43966 - Host Checker OS check fails with "Host checker client version is incompatible" if 9.0 components are used to connect to pre-9.0 Pulse Connect Secure / Pulse Policy Secure

KB17389 - [Host Checker] How to enforce domain membership with Host Checker Policy

< Back to search results

Article

KB44663 - Host Check fails on macOS 11.1 when policy is enforced.

« Go Back

Information

Last Modified Date	2/18/2021 11:15 AM

Synopsis

This article describes the Host Checker failure on macOS 11.1 when policy is enforced.

Problem or Goal

Host Checker fails on macOS 11.1 if any HC policy is Enforced.

This issue does not occur in the previous macOS versions.
This issue is applicable to both Browser and Pulse Desktop macOS Clients.

Cause

This occurred due to Apple not following their normal OS version naming convention.

Solution

This issue is resolved in 9.1R11 PCS/PPS/PDC version onwards.

Workaround:

Do not enforce Host Checker Policies.

Related Links

Attachment 1

Created By	Raghu Kumar