<?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: Endpoint client policy updates in Endpoint</title>
    <link>https://community.checkpoint.com/t5/Endpoint/Endpoint-client-policy-updates/m-p/37396#M933</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thank you Marina, I opened a case:&amp;nbsp;SR # 3-0511850271 but I don't think it was sent to R&amp;amp;D, how can I tell?&lt;/P&gt;&lt;H2 class="" style="color: #333333; background-color: #ffffff; font-weight: bold; text-decoration: none; font-size: 22px; padding: 10px 0px 0px 10px;"&gt;&lt;/H2&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 09 Aug 2018 22:34:27 GMT</pubDate>
    <dc:creator>Dan_Roddy</dc:creator>
    <dc:date>2018-08-09T22:34:27Z</dc:date>
    <item>
      <title>Endpoint client policy updates</title>
      <link>https://community.checkpoint.com/t5/Endpoint/Endpoint-client-policy-updates/m-p/37391#M928</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Greetings,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We have 81 Windows 10 Surface Books all deployed with SandBlast Endpoint Agent.&amp;nbsp; Many of these devices rarely are wired to the network.&amp;nbsp; They connect and get all policy updates for every application we have deployed using Microsoft Direct Access with one exception: SandBlast Endpoint Agent.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If the agent were to connect to the Endpoint Management Server by domain name, policy updates would just work.&amp;nbsp; Now for my question:&amp;nbsp; How can I make the E80.82 client connect to management using its internal DNS name?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have asked TAC but not getting any traction, they don't know what Direct Access is.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best regads &amp;amp; thank you in advance,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Dan Roddy&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 09 Jul 2018 16:58:48 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Endpoint/Endpoint-client-policy-updates/m-p/37391#M928</guid>
      <dc:creator>Dan_Roddy</dc:creator>
      <dc:date>2018-07-09T16:58:48Z</dc:date>
    </item>
    <item>
      <title>Re: Endpoint client policy updates</title>
      <link>https://community.checkpoint.com/t5/Endpoint/Endpoint-client-policy-updates/m-p/37392#M929</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Why not by internal IP address?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 13 Jul 2018 10:43:48 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Endpoint/Endpoint-client-policy-updates/m-p/37392#M929</guid>
      <dc:creator>PhoneBoy</dc:creator>
      <dc:date>2018-07-13T10:43:48Z</dc:date>
    </item>
    <item>
      <title>Re: Endpoint client policy updates</title>
      <link>https://community.checkpoint.com/t5/Endpoint/Endpoint-client-policy-updates/m-p/37393#M930</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Microsoft Direct Access uses the Name Resolution Policy Table (NRPT) to address resources inside the domain, therefore the dns name must be used by the client.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 17 Jul 2018 19:16:11 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Endpoint/Endpoint-client-policy-updates/m-p/37393#M930</guid>
      <dc:creator>Dan_Roddy</dc:creator>
      <dc:date>2018-07-17T19:16:11Z</dc:date>
    </item>
    <item>
      <title>Re: Endpoint client policy updates</title>
      <link>https://community.checkpoint.com/t5/Endpoint/Endpoint-client-policy-updates/m-p/37394#M931</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;OK, can I edit the IP and replace it with dns name?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 08 Aug 2018 14:52:23 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Endpoint/Endpoint-client-policy-updates/m-p/37394#M931</guid>
      <dc:creator>Dan_Roddy</dc:creator>
      <dc:date>2018-08-08T14:52:23Z</dc:date>
    </item>
    <item>
      <title>Re: Endpoint client policy updates</title>
      <link>https://community.checkpoint.com/t5/Endpoint/Endpoint-client-policy-updates/m-p/37395#M932</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Dan,&lt;/P&gt;&lt;P&gt;In one of upcoming releases of Endpoint Management and Endpoint Client we are planning to provide this ability built in the product.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Meanwhile for having workaround please open a Support ticket and ask to get a workaround from R&amp;amp;D to connect&amp;nbsp;with FQDN. The configuration is not very convenient yet but you will be able to test it as a workaround in your environment before we release it officially with convenient configuration.&amp;nbsp;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 08 Aug 2018 15:47:57 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Endpoint/Endpoint-client-policy-updates/m-p/37395#M932</guid>
      <dc:creator>Marina_Lachtarn</dc:creator>
      <dc:date>2018-08-08T15:47:57Z</dc:date>
    </item>
    <item>
      <title>Re: Endpoint client policy updates</title>
      <link>https://community.checkpoint.com/t5/Endpoint/Endpoint-client-policy-updates/m-p/37396#M933</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thank you Marina, I opened a case:&amp;nbsp;SR # 3-0511850271 but I don't think it was sent to R&amp;amp;D, how can I tell?&lt;/P&gt;&lt;H2 class="" style="color: #333333; background-color: #ffffff; font-weight: bold; text-decoration: none; font-size: 22px; padding: 10px 0px 0px 10px;"&gt;&lt;/H2&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 09 Aug 2018 22:34:27 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Endpoint/Endpoint-client-policy-updates/m-p/37396#M933</guid>
      <dc:creator>Dan_Roddy</dc:creator>
      <dc:date>2018-08-09T22:34:27Z</dc:date>
    </item>
    <item>
      <title>Re: Endpoint client policy updates</title>
      <link>https://community.checkpoint.com/t5/Endpoint/Endpoint-client-policy-updates/m-p/37397#M934</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I will follow up.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 12 Aug 2018 08:06:22 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Endpoint/Endpoint-client-policy-updates/m-p/37397#M934</guid>
      <dc:creator>Marina_Lachtarn</dc:creator>
      <dc:date>2018-08-12T08:06:22Z</dc:date>
    </item>
    <item>
      <title>Re: Endpoint client policy updates</title>
      <link>https://community.checkpoint.com/t5/Endpoint/Endpoint-client-policy-updates/m-p/37398#M935</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Marina,&amp;nbsp; I am checking back with you to see if support for IPv6 has been built in to EP clients to get policy updates through Microsoft Direct Access.&amp;nbsp; EP is the only security client in our environment that is not currently working in this regard.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Dan Roddy&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 17 Jan 2019 19:32:03 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Endpoint/Endpoint-client-policy-updates/m-p/37398#M935</guid>
      <dc:creator>Dan_Roddy</dc:creator>
      <dc:date>2019-01-17T19:32:03Z</dc:date>
    </item>
  </channel>
</rss>

