Restrict unlicensed vpn versions connecting via VPN

Forum|Forum|2 years ago
December 19, 2023
1 reply
1248 views

We're utilizing FortiClient EMS and aiming to set up a host check to prevent unlicensed VPN versions from connecting via VPN.

To achieve this, we're considering using the registry key HKEY_CURRENT_USER\Volatile Environment (USERDOMAIN).

This method might not be the most reliable in identifying specifically those users employing the free version of FortiClient.

While this registry key can restrict access based on the domain, it doesn't guarantee conclusively that users are using the free version of FortiClient.

Which registry key should I use to configure the host check to authorize only users with FortiClient EMS and not the free FortiClient?

Thank you

ozkanaltas

Valued Contributor III

Hello @Kellua ,

I found a key in the registry related to FortiClient connection status with EMS.

This key is in this path
"HKEY_LOCAL_MACHINE\SOFTWARE\Fortinet\FortiClient\FA_ESNAC"

If "status" key equal to "1" this means FortiClient is not registered to EMS.
If "status" key equal to "2" this means FortiClient is registered to EMS.

I think you can use this key.

Also, I think the best way for your request ZTNA Tag. You can use ZTNA Tag on your firewall policy. Even if someone connects to VPN with an unlicensed FortiClient, can't access your internal resources.

Sign up

Login with SSO

Login to the community

Login with SSO