Open Windows PowerShell or a command prompt. Run the following command to determine if you already have WinRM over HTTPS configured.
Matches if the device successfully responds to a WinRM client session request. User name and password credentials are required. If there are multiple credentials, each set of credentials will be attempted to find a potential match. The commands are used to automate interaction with the device. Each command is run via Powershell.

The persistent agent remains installed on the endpoint and can perform scheduled compliance scans automatically without user interaction. The passive agent collects endpoint information without requiring installation or user action, enabling ongoing compliance evaluation transparently.

RADIUS accounting must be enabled on FortiGate so it sends session start and stop records to FortiNAC-F. These accounting messages provide real-time VPN session status updates, allowing FortiNAC-F to track user connections and enforce appropriate network access policies.

DHCP must be allowed so endpoints in the isolation network can obtain an IP address. DNS must be permitted so isolated hosts can resolve the FortiNAC-F hostname or required resources.
HTTP/HTTPS must be allowed to enable redirection and communication with the FortiNAC-F captive portal for registration and authentication.