Description This article describes the configuration steps required to
quickly isolate hosts that initially had the Persistent Agent
communicating, but are no longer doing so. The host's compliance status
may have changed during this time, and it may...
Description This article describes a behavior observed in FortiNAC
Manager related to CA Management, where the FortiNAC CA status appears
as 'Failed' despite stable network communication and normal CA
functionality. This behavior is isolated to Stand...
Description This article describes the steps required to successfully
deploy the Persistent Agent on a Linux host. In this example, Ubuntu
24.04 is used as the test host. Scope FortiNAC and Linux hosts. Solution
This article is a follow-up to Technic...
Description This article describes how to create and use a Custom Script
to send customizable event content via Email. Scope FortiNAC. Solution
The scripts are located in the '/home/cm/scripts' directory and can be
reached after entering the shell. e...
Description This article describes the steps to create an additional
Winbind instance in FortiNAC that connects to a different domain and its
respective Domain Controllers. The reason why the configuration of
Winbind is required in FortiNAC is explai...
Most of the features should work normally. I suggest opening a ticket
with TAC support to investigate this behavior further.It will be added
to the support list after it is tested and confirmed to be fully
compatible with macOS Tahoe, most likely wit...
Fortinet training courses include important details about
troubleshooting and analyzing debugs.Another source is the community
articles, which share configurations and possible issues verified
through logs for specific topics. You can also refer to t...
PEAP/MSCHAPv2 requires the use of Winbind since it verifies challenges
instead of passwords, Technical Tip: MSCHAPv2 authentication, join
FortiNAC in domain and checks You can try to use EAP-TTLS instead.