<?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 Push Operations in Endpoint</title>
    <link>https://community.checkpoint.com/t5/Endpoint/Push-Operations/m-p/161156#M6204</link>
    <description>&lt;P&gt;Hi guys,&lt;/P&gt;&lt;P&gt;I am wondering if it is possible to create a custom&amp;nbsp;&lt;STRONG&gt;Push Operation&lt;/STRONG&gt; for starting blades. In some cases blades are not running and I thought the possibility of a push operation could be solution !?!?&lt;BR /&gt;&lt;BR /&gt;Any ideas or how do you handle these kinds of issues?&lt;BR /&gt;&lt;BR /&gt;KR,&lt;BR /&gt;Oliver&lt;/P&gt;</description>
    <pubDate>Thu, 03 Nov 2022 14:39:44 GMT</pubDate>
    <dc:creator>CP-Shark</dc:creator>
    <dc:date>2022-11-03T14:39:44Z</dc:date>
    <item>
      <title>Push Operations</title>
      <link>https://community.checkpoint.com/t5/Endpoint/Push-Operations/m-p/161156#M6204</link>
      <description>&lt;P&gt;Hi guys,&lt;/P&gt;&lt;P&gt;I am wondering if it is possible to create a custom&amp;nbsp;&lt;STRONG&gt;Push Operation&lt;/STRONG&gt; for starting blades. In some cases blades are not running and I thought the possibility of a push operation could be solution !?!?&lt;BR /&gt;&lt;BR /&gt;Any ideas or how do you handle these kinds of issues?&lt;BR /&gt;&lt;BR /&gt;KR,&lt;BR /&gt;Oliver&lt;/P&gt;</description>
      <pubDate>Thu, 03 Nov 2022 14:39:44 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Endpoint/Push-Operations/m-p/161156#M6204</guid>
      <dc:creator>CP-Shark</dc:creator>
      <dc:date>2022-11-03T14:39:44Z</dc:date>
    </item>
    <item>
      <title>Re: Push Operations</title>
      <link>https://community.checkpoint.com/t5/Endpoint/Push-Operations/m-p/161157#M6205</link>
      <description>&lt;P&gt;Generally the Check Point watchdog service should handle automatically restarting blades assuming they're for whichever reason in a stopped state.&lt;BR /&gt;If the watchdog isn't restarting the service then there's a deeper issue that should be examined.&lt;/P&gt;&lt;P&gt;Unless of course you're permitting users to disable blades in the client UI. In which case, that's a policy issue.&lt;BR /&gt;(Though on the topic of that, I would love a push operation or policy or whatever which allows me to disable blades for a limited time instead of having to keep track of things manually)&lt;/P&gt;</description>
      <pubDate>Thu, 03 Nov 2022 14:51:04 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Endpoint/Push-Operations/m-p/161157#M6205</guid>
      <dc:creator>Swiftyyyy</dc:creator>
      <dc:date>2022-11-03T14:51:04Z</dc:date>
    </item>
    <item>
      <title>Re: Push Operations</title>
      <link>https://community.checkpoint.com/t5/Endpoint/Push-Operations/m-p/161158#M6206</link>
      <description>&lt;LI-CODE lang="markup"&gt;If the watchdog isn't restarting the service then there's a deeper issue that should be examined.&lt;/LI-CODE&gt;&lt;P&gt;Any ideas, SKs or hints how to troubleshoot this issue deeper?&lt;/P&gt;</description>
      <pubDate>Thu, 03 Nov 2022 14:59:02 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Endpoint/Push-Operations/m-p/161158#M6206</guid>
      <dc:creator>CP-Shark</dc:creator>
      <dc:date>2022-11-03T14:59:02Z</dc:date>
    </item>
    <item>
      <title>Re: Push Operations</title>
      <link>https://community.checkpoint.com/t5/Endpoint/Push-Operations/m-p/161159#M6207</link>
      <description>&lt;P&gt;It depends on the blade really.&lt;BR /&gt;In general though, I'd give clients a bit of time to sort things out by themselves.&lt;/P&gt;&lt;P&gt;Quite often you'd encounter cases where a client comes online &amp;amp; does the first communication interval before a blade has the chance to fully initialize. Then you end up with a falsely reported state on your dashboard for a little while.&lt;/P&gt;&lt;P&gt;The persistent cases lasting more than a few hours should be looked at though.&lt;/P&gt;</description>
      <pubDate>Thu, 03 Nov 2022 15:01:28 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Endpoint/Push-Operations/m-p/161159#M6207</guid>
      <dc:creator>Swiftyyyy</dc:creator>
      <dc:date>2022-11-03T15:01:28Z</dc:date>
    </item>
    <item>
      <title>Re: Push Operations</title>
      <link>https://community.checkpoint.com/t5/Endpoint/Push-Operations/m-p/161161#M6208</link>
      <description>&lt;P&gt;This behaviour is quite common and I know this. But we have a few clients where t&lt;SPAN&gt;he persistent cases definitly lasting more than a few hours and we are very keen for the understanding of these issues.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 03 Nov 2022 15:19:07 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Endpoint/Push-Operations/m-p/161161#M6208</guid>
      <dc:creator>CP-Shark</dc:creator>
      <dc:date>2022-11-03T15:19:07Z</dc:date>
    </item>
    <item>
      <title>Re: Push Operations</title>
      <link>https://community.checkpoint.com/t5/Endpoint/Push-Operations/m-p/161180#M6209</link>
      <description>&lt;P&gt;Again, it depends on what the situation is.&lt;BR /&gt;TAC should be involved in these cases.&lt;/P&gt;</description>
      <pubDate>Thu, 03 Nov 2022 18:14:19 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Endpoint/Push-Operations/m-p/161180#M6209</guid>
      <dc:creator>PhoneBoy</dc:creator>
      <dc:date>2022-11-03T18:14:19Z</dc:date>
    </item>
  </channel>
</rss>

