I'd probably stay with FortiClient and EMS, probably best bang for the buck since you're already on a FortiGate. And, if that happens to be Fortinet's EMS, so be it. I can easily build a case for it, I just have to find the right product. I know in all likelyhood we'll be spending more money, and I'm ok with this. I know this is probably more about licensing than anything.ĮDIT: I'm not looking to get this for cheaper than the version we are using.

Currently we have around 220 users regularly connected, but the idea is that we could have roughly 2000 connecting if needed. This is fixable with a new XML File that ALL USERS would have to import, which is really not an option.Ĩ- Scalable, quickly, in case we have to have all users using it. This causes the local (home) IP to register in DNS. If I am at home, on my wireless, and I connect, I get our company DNS servers injected into my LOCAL WIRELESS CONNECTION, not just the VPN adapter. EDIT: This can include using a Windows DHCP server or the VPN programs own.ģ- NOT register our DNS servers on the machines LOCAL IP SETTINGS. While the Forticlient configuration on the firewall allows us to point to a DHCP server, that configuration does not work and upon further conversations with fortinet, the feature actually is not functional even though it shows there. Currently, we can't set lease times on VPN addresses. Forticlient requires us to have users update an XML file.Ģ- DHCP with LEASE TIMES. When a user logs in, if we change something in the settings it should register the change and apply without the user having to import a new XML or settings file. Here is a list of things I am looking for in a new solution (in no particular order.ġ- Manage endpoint settings remotely. It works, at least in basic terms, but there are a lot of things that we can't do with it unless we upgrade to their EMS solution, and that is not something we want to do. Currently we are using Fortinets Forticlient as our VPN Solution.

Fortinet vpn client requirements