https://community.checkpoint.com/t5/Firewall-and-Security-Management/Mobile-Access-Blade-Checkpoint-EndPoint-Security/m-p/118634#M16793 <P>Hi,</P><P>So MAB and Endpoint Sec are different things, and do have different portals. But if you are migrating between VSX and Physical hardware I'm almost certain you're going to have to create a new object in the SmartConsole for the gateway(s) which will mean a new certificate will need to be created.&nbsp;<BR /><BR />Your users will receive a "certificate warning" to say it's been changed, providing everything else is the same.</P><P>&nbsp;</P><P>Daniel</P> Tue, 18 May 2021 12:50:45 GMT Daniel_Collins 2021-05-18T12:50:45Z https://community.checkpoint.com/t5/Firewall-and-Security-Management/Mobile-Access-Blade-Checkpoint-EndPoint-Security/m-p/118620#M16790 <P>Hi All,</P><P>We are migrating from VSX to Physical boxes. In this environment we are using the same existing policy by cloning it.</P><P>We have Mobile Access blade with Checkpoint endpoint Security enabled here. So after migration do we need to update any certificate or anything else that needs to be considered for Checkpoint Endpoint Certificate to work without any issues? All the IPs that are in the VSX platform will be configured as the VIP IPs in the migration to Physical box. So IPs will remain same for Endpoint to work. Just concerned about Certificate and any other parameters which should be checked. Please help.</P><P>Regards,</P><P>Sanjay S</P> Tue, 18 May 2021 10:03:53 GMT https://community.checkpoint.com/t5/Firewall-and-Security-Management/Mobile-Access-Blade-Checkpoint-EndPoint-Security/m-p/118620#M16790 Sanjay_S 2021-05-18T10:03:53Z https://community.checkpoint.com/t5/Firewall-and-Security-Management/Mobile-Access-Blade-Checkpoint-EndPoint-Security/m-p/118634#M16793 <P>Hi,</P><P>So MAB and Endpoint Sec are different things, and do have different portals. But if you are migrating between VSX and Physical hardware I'm almost certain you're going to have to create a new object in the SmartConsole for the gateway(s) which will mean a new certificate will need to be created.&nbsp;<BR /><BR />Your users will receive a "certificate warning" to say it's been changed, providing everything else is the same.</P><P>&nbsp;</P><P>Daniel</P> Tue, 18 May 2021 12:50:45 GMT https://community.checkpoint.com/t5/Firewall-and-Security-Management/Mobile-Access-Blade-Checkpoint-EndPoint-Security/m-p/118634#M16793 Daniel_Collins 2021-05-18T12:50:45Z https://community.checkpoint.com/t5/Firewall-and-Security-Management/Mobile-Access-Blade-Checkpoint-EndPoint-Security/m-p/118636#M16794 <P>Thank you Daniel.</P><P>I was talking about the Client based VPN which can be enabled in Mobile Access blade, the oprion is Endpoint Security VPN.</P><P>Regards,</P><P>Sanjay S</P> Tue, 18 May 2021 13:22:55 GMT https://community.checkpoint.com/t5/Firewall-and-Security-Management/Mobile-Access-Blade-Checkpoint-EndPoint-Security/m-p/118636#M16794 Sanjay_S 2021-05-18T13:22:55Z https://community.checkpoint.com/t5/Firewall-and-Security-Management/Mobile-Access-Blade-Checkpoint-EndPoint-Security/m-p/118663#M16802 <P>Yes, so that's the same client but called Check Point Mobile. Same applies, so if you're creating new gateway objects then you'll get a new certificate which will be presented to the users unless you're using a valid certificate for the device.&nbsp;<BR /><BR />There is sometimes a way to export the existing VPN certificate, but this has been challenging in the past.&nbsp;</P> Tue, 18 May 2021 15:33:52 GMT https://community.checkpoint.com/t5/Firewall-and-Security-Management/Mobile-Access-Blade-Checkpoint-EndPoint-Security/m-p/118663#M16802 Daniel_Collins 2021-05-18T15:33:52Z