<?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: CheckPoint Endpoint VPN and Sophos in SASE and Remote Access</title>
    <link>https://community.checkpoint.com/t5/SASE-and-Remote-Access/CheckPoint-Endpoint-VPN-and-Sophos/m-p/203822#M4164</link>
    <description>&lt;P&gt;The SK you mentioned is about something else. Do you have a TAC case for this issue?&lt;/P&gt;</description>
    <pubDate>Mon, 22 Jan 2024 12:09:14 GMT</pubDate>
    <dc:creator>_Val_</dc:creator>
    <dc:date>2024-01-22T12:09:14Z</dc:date>
    <item>
      <title>CheckPoint Endpoint VPN and Sophos</title>
      <link>https://community.checkpoint.com/t5/SASE-and-Remote-Access/CheckPoint-Endpoint-VPN-and-Sophos/m-p/203444#M4163</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;We use CheckPoint Endpoint VPN on our clients and Sophos as anti-virus. There is a known problem that Sophos can no longer update with newer EndPoint clients. There is the sk178308. I got the passdialogue.exe and basically it works. However, the passdialogue.exe does not seem to have any silent parameters. We would like to do this via our software distribution, because we have to do this on a few hundred clients, it is not an option to do this manually. Has anyone had the same problem and been able to solve it?&lt;/P&gt;&lt;P&gt;I was actually hoping CheckPoint would solve the problem in a newer version, but I don't think anything will happen. &lt;span class="lia-unicode-emoji" title=":disappointed_face:"&gt;😞&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Best regards,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Maik&lt;/P&gt;</description>
      <pubDate>Thu, 18 Jan 2024 07:08:34 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/SASE-and-Remote-Access/CheckPoint-Endpoint-VPN-and-Sophos/m-p/203444#M4163</guid>
      <dc:creator>Maik1</dc:creator>
      <dc:date>2024-01-18T07:08:34Z</dc:date>
    </item>
    <item>
      <title>Re: CheckPoint Endpoint VPN and Sophos</title>
      <link>https://community.checkpoint.com/t5/SASE-and-Remote-Access/CheckPoint-Endpoint-VPN-and-Sophos/m-p/203822#M4164</link>
      <description>&lt;P&gt;The SK you mentioned is about something else. Do you have a TAC case for this issue?&lt;/P&gt;</description>
      <pubDate>Mon, 22 Jan 2024 12:09:14 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/SASE-and-Remote-Access/CheckPoint-Endpoint-VPN-and-Sophos/m-p/203822#M4164</guid>
      <dc:creator>_Val_</dc:creator>
      <dc:date>2024-01-22T12:09:14Z</dc:date>
    </item>
    <item>
      <title>Re: CheckPoint Endpoint VPN and Sophos</title>
      <link>https://community.checkpoint.com/t5/SASE-and-Remote-Access/CheckPoint-Endpoint-VPN-and-Sophos/m-p/203840#M4165</link>
      <description>&lt;P&gt;Every time we had similar issues like this in the past with customers, we ended up opening TAC case. I dont deal much myself with endpoint side, so cant say for sure what outcome was, but thats definitely your best option.&lt;/P&gt;
&lt;P&gt;Andy&lt;/P&gt;</description>
      <pubDate>Mon, 22 Jan 2024 13:43:20 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/SASE-and-Remote-Access/CheckPoint-Endpoint-VPN-and-Sophos/m-p/203840#M4165</guid>
      <dc:creator>the_rock</dc:creator>
      <dc:date>2024-01-22T13:43:20Z</dc:date>
    </item>
  </channel>
</rss>

