> Let me get back to real basics with this one
Yes, at least then there is little room for confusion.
> You can use Endpoint Security VPN and Mobile Access Blade on the Same Gateway.
> ie One User connects with Endpoint Security VPN Client and another connects with say Capsule Connect or Check Point
> Mobile for Windows Client.
> However they use different licenses.
Yes, agree completely - as I have been saying exactly this in my previous posts.
> So if you have 50 Endpoint Security VPN Licenses and a 200 Seat MOB license then then you can have 50 Endpoint Security
> Users and 200 MOB Users connected to the Same Gateway at the same time
Again, completely agree - I have been saying this too in my previous posts.
> However what it won't do is take a 51st Endpoint Security VPN Client Connection and use a Spare MOB license for that
> It won't take the 201st MOB Connection and use a spare Endpoint Security VPN licensse to allow to connect.
Are you sure? I mean - do you really know this for certain?
The reason I ask is one (1) The Mobile Access Blade configuration explicitly allows you to use the Endpoint Security VPN client with MAB licensing - see screenshot below:
(2) it allows you to connect to a gateway with only the MAB blade ticked and SSLVPN licensing (and no IPSec blade and no Sandblast Basic or Endpoint container licensing).
As I have stated in previous posts, I am not asking whether an Endpoint Security VPN client will get the FW functionality if connecting via MAB licensing - of course it won't.
What I am asking given that the MAB blade clearly supports the use of the Endpoint Security VPN client and counts such a connection again the MAB license and given that I have a 50 seat endpoint container license then:
(1) which licence is used first and
(2) is the product "clever" enough to realise that it has two licensing schemes, both capable of allowing an Endpoint Connect VPN client and so automatically start counting new clients towards the second license once the first is depleted?