<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Remote Access VPN Sites after Client Deployment in SASE and Remote Access</title>
    <link>https://community.checkpoint.com/t5/SASE-and-Remote-Access/Remote-Access-VPN-Sites-after-Client-Deployment/m-p/135593#M7589</link>
    <description>&lt;DIV class="page" title="Page 97"&gt;
&lt;DIV class="layoutArea"&gt;
&lt;DIV class="column"&gt;
&lt;P&gt;&lt;SPAN&gt;Endpoint Security R81 Administration Guide p.&lt;/SPAN&gt;&lt;SPAN style="font-family: inherit; background-color: #ffffff;"&gt;&amp;nbsp;67:&lt;/SPAN&gt;&lt;/P&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;DIV class="page" title="Page 97"&gt;
&lt;DIV class="layoutArea"&gt;
&lt;DIV class="column"&gt;
&lt;P&gt;&lt;SPAN&gt;Defining a VPN Site&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;When you use an exported package, you can configure each component package to connect to a default VPN site.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;You can configure a default VPN site for packages for export. You cannot configure a default VPN site with automatic Deployment rules. To distribute a defined VPN site with Deployment rules, you can:&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;- &lt;/SPAN&gt;&lt;SPAN&gt;Use Deployment rules to distribute an Endpoint Security component package without &lt;/SPAN&gt;&lt;SPAN&gt;Endpoint Connect VPN&lt;/SPAN&gt;&lt;SPAN&gt;.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;- &lt;/SPAN&gt;&lt;SPAN&gt;Create a package for export that includes only &lt;/SPAN&gt;&lt;SPAN&gt;Endpoint Connect VPN &lt;/SPAN&gt;&lt;SPAN&gt;and distribute it manually.&lt;/SPAN&gt;&lt;/P&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;</description>
    <pubDate>Mon, 06 Dec 2021 09:52:50 GMT</pubDate>
    <dc:creator>G_W_Albrecht</dc:creator>
    <dc:date>2021-12-06T09:52:50Z</dc:date>
    <item>
      <title>Remote Access VPN Sites after Client Deployment</title>
      <link>https://community.checkpoint.com/t5/SASE-and-Remote-Access/Remote-Access-VPN-Sites-after-Client-Deployment/m-p/135586#M7588</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;We deploy a number of Endpoint Security (Harmony/Sandblast) clients with the Remote Access VPN included.&lt;BR /&gt;Usually we perform deployments through 3rd party deployment tools like SCCM, meaning we pre-package the VPN site into an exported client and then push that to the Endpoint.&lt;BR /&gt;&lt;BR /&gt;How can we add additional VPN sites to the Endpoint after the fact? As far as I'm aware, SmartEndpoint nor the Infinity Portal Endpoint management pages provides a GUI method of enforcing these changes.&lt;BR /&gt;Is there some other tool or configuration file we can modify &amp;amp; push to Endpoints?&amp;nbsp;&lt;/P&gt;&lt;P&gt;I would expect there to be an elegant way of performing this task.&lt;/P&gt;&lt;P&gt;Thank you&lt;/P&gt;</description>
      <pubDate>Mon, 06 Dec 2021 08:46:43 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/SASE-and-Remote-Access/Remote-Access-VPN-Sites-after-Client-Deployment/m-p/135586#M7588</guid>
      <dc:creator>Swiftyyyy</dc:creator>
      <dc:date>2021-12-06T08:46:43Z</dc:date>
    </item>
    <item>
      <title>Re: Remote Access VPN Sites after Client Deployment</title>
      <link>https://community.checkpoint.com/t5/SASE-and-Remote-Access/Remote-Access-VPN-Sites-after-Client-Deployment/m-p/135593#M7589</link>
      <description>&lt;DIV class="page" title="Page 97"&gt;
&lt;DIV class="layoutArea"&gt;
&lt;DIV class="column"&gt;
&lt;P&gt;&lt;SPAN&gt;Endpoint Security R81 Administration Guide p.&lt;/SPAN&gt;&lt;SPAN style="font-family: inherit; background-color: #ffffff;"&gt;&amp;nbsp;67:&lt;/SPAN&gt;&lt;/P&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;DIV class="page" title="Page 97"&gt;
&lt;DIV class="layoutArea"&gt;
&lt;DIV class="column"&gt;
&lt;P&gt;&lt;SPAN&gt;Defining a VPN Site&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;When you use an exported package, you can configure each component package to connect to a default VPN site.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;You can configure a default VPN site for packages for export. You cannot configure a default VPN site with automatic Deployment rules. To distribute a defined VPN site with Deployment rules, you can:&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;- &lt;/SPAN&gt;&lt;SPAN&gt;Use Deployment rules to distribute an Endpoint Security component package without &lt;/SPAN&gt;&lt;SPAN&gt;Endpoint Connect VPN&lt;/SPAN&gt;&lt;SPAN&gt;.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;- &lt;/SPAN&gt;&lt;SPAN&gt;Create a package for export that includes only &lt;/SPAN&gt;&lt;SPAN&gt;Endpoint Connect VPN &lt;/SPAN&gt;&lt;SPAN&gt;and distribute it manually.&lt;/SPAN&gt;&lt;/P&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;</description>
      <pubDate>Mon, 06 Dec 2021 09:52:50 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/SASE-and-Remote-Access/Remote-Access-VPN-Sites-after-Client-Deployment/m-p/135593#M7589</guid>
      <dc:creator>G_W_Albrecht</dc:creator>
      <dc:date>2021-12-06T09:52:50Z</dc:date>
    </item>
  </channel>
</rss>

