Is VPN before logon, like we had in FortiClient 6.0, ever coming back for non-EMS customers? They say the VPN does not require EMS, but starting in 6.2 where it is a separate app (instead of the same app and just not activating EMS features), they ripped out critical features like this.
Being able to connect to the corporate network from a button on the Windows login page, before logging in, allows authenticating your Windows login against a DC just like if you were on site, rather than cached credentials. This is absolutely critical to:
- forgotten password resets
- field personnel passing off a laptop to a fellow employee who hasn’t been cached on it
- Primarily desktop users who have a laptop for occasional remote use, haven’t used it since before their last password expiration. They know their current password, but not the one cached on that laptop.
A VPN that cannot connect without a successful Windows logon by the end-user is a joke or a toy, and not an enterprise product or even a business product. Is this ever going to be rectified, or is the new model still “screw anyone who can’t afford EMS”?
Between this, Windows Always On VPN Device Tunnel being limited to Enterprise editions, Azure AD not being self hostable like AD, and the dwindling availability of remote support software that uses a hosted server, I get the feeling tech companies are colluding to sabotage capabilities that make mobility practical with things you own, as part of a scheme to sell the narrative that mobility can only be rented (or is “enabled by the cloud”). But maybe I’m just a conspiracy theorist. In any case, I’d like to keep VPN before logon as 6.0 goes EOL, and like most SMBs, cannot buy a huge bundle of other features we don’t need to go with it.