{"id":3010,"date":"2026-01-08T14:25:05","date_gmt":"2026-01-08T14:25:05","guid":{"rendered":"https:\/\/help.peacedoorball.blog\/ca\/?p=3010"},"modified":"2026-01-08T14:25:05","modified_gmt":"2026-01-08T14:25:05","slug":"comment-resoudre-le-probleme-de-non-application-de-la-politique-eset-protect-a-tous-les-clients","status":"publish","type":"post","link":"https:\/\/help.peacedoorball.blog\/ca\/comment-resoudre-le-probleme-de-non-application-de-la-politique-eset-protect-a-tous-les-clients\/","title":{"rendered":"Comment r\u00e9soudre le probl\u00e8me de non-application de la politique ESET PROTECT \u00e0 tous les clients"},"content":{"rendered":"<p>D\u00e9j\u00e0 vu. Appliquer une r\u00e8gle de pare-feu via ESET PROTECT \u00e0 plusieurs machines clientes peut para\u00eetre simple, mais ce n&rsquo;est pas toujours le cas. Le plus \u00e9trange, c&rsquo;est que sur certains PC, la r\u00e8gle est bien appliqu\u00e9e, et sur d&rsquo;autres\u2026 beaucoup moins. Et quand on \u00e9pluche les journaux, on n&rsquo;y trouve aucune piste. Le coupable ? G\u00e9n\u00e9ralement, un agent de gestion ESET obsol\u00e8te qui tourne discr\u00e8tement en arri\u00e8re-plan et emp\u00eache la r\u00e8gle de fonctionner. C&rsquo;est assez frustrant, car, comme toujours, Windows complique les choses inutilement.<\/p>\n<p>Si vous rencontrez ce probl\u00e8me, commencez par v\u00e9rifier la version de l&rsquo;agent de gestion ESET sur les clients. Bien souvent, une version incompatible ou obsol\u00e8te est \u00e0 l&rsquo;origine du non-respect des politiques appliqu\u00e9es. En effet, les agents les plus r\u00e9cents sont plus performants pour reconna\u00eetre et appliquer automatiquement les politiques, tandis que les anciens les ignorent ou ne d\u00e9tectent aucune erreur.<\/p>\n<h2>Comment r\u00e9soudre le probl\u00e8me suivant : la politique ESET PROTECT ne s\u2019applique pas aux clients ?<\/h2>\n<h3>D\u00e9terminez la version de l&rsquo;agent de gestion ESET install\u00e9e sur les PC clients.<\/h3>\n<p><strong>Pourquoi c&rsquo;est utile :<\/strong> Parce que si la version de l&rsquo;agent est obsol\u00e8te, sa mise \u00e0 jour r\u00e9sout g\u00e9n\u00e9ralement le probl\u00e8me. C&rsquo;est comme s&rsquo;assurer que tout le monde parle la m\u00eame langue.<\/p>\n<p><strong>Quand intervenir :<\/strong> lorsque vous constatez que les PC ne respectent pas les nouvelles politiques ou que les mises \u00e0 jour ne se propagent pas.<\/p>\n<p><strong>\u00c0 quoi s&rsquo;attendre :<\/strong> L&rsquo;affichage d&rsquo;un num\u00e9ro de version plus r\u00e9cent sur certains PC et d&rsquo;un num\u00e9ro plus ancien sur d&rsquo;autres confirmera l&rsquo;incoh\u00e9rence.<\/p>\n<p><strong>Mesures:<\/strong><\/p>\n<ul>\n<li>Rendez-vous sur la console web <strong>4-3-2-1 <\/strong> <a href=\"https:\/\/protect.cloud.eset.com\" rel=\"noopener noreferrer\" target=\"_blank\">ESET PROTECT<\/a>.<\/li>\n<li>S\u00e9lectionnez <strong>ORDINATEURS<\/strong> dans le menu de gauche.<\/li>\n<li>Identifiez les clients pour lesquels les strat\u00e9gies ne s&rsquo;appliquent pas : v\u00e9rifiez la date <strong>de derni\u00e8re connexion<\/strong> pour confirmer qu&rsquo;ils ont \u00e9t\u00e9 synchronis\u00e9s r\u00e9cemment. Parfois, les ordinateurs ne sont tout simplement pas en ligne ou n&rsquo;ont pas pu se connecter, ce qui constitue un tout autre probl\u00e8me.<\/li>\n<li>Cliquez sur les trois points \u00e0 c\u00f4t\u00e9 de chaque machine et choisissez <strong>Afficher les d\u00e9tails<\/strong>.<\/li>\n<li>Recherchez la version de l&rsquo;agent de gestion ESET indiqu\u00e9e ; elle peut ressembler \u00e0 ceci :<code>9.01141.0 or <code>10.1.1292.0<\/code><\/code><\/li>\n<p><code><code> <\/code><\/code><\/ul>\n<p><code><code> <\/p>\n<p>On some machines this might seem trivial, but sometimes you\u2019ll see the version is really out of date, so you know what to target next.<\/p>\n<p>To compare, also check the agent version on a machine where the policy was successfully applied. If the versions differ significantly, that\u2019s your clue to push an update.<\/p>\n<h3>Update the ESET Management Agent on clients<\/h3>\n<p><strong>Why it helps:<\/strong> Updating the agent can elevate the client\u2019s ability to receive and enforce policies, especially if the current version is old or buggy.<\/p>\n<p><strong>When to do this:<\/strong> When you find the agent version is out of date or mismatched.<\/p>\n<p><strong>What to expect:<\/strong> The client\u2019s agent updating and the policy finally sticking without fuss.<\/p>\n<p>Here\u2019s what to do:<\/p>\n<ul>\n<li>Go to the <strong>Tasks<\/strong> section in the <a href=\"https:\/\/protect.cloud.eset.com\" rel=\"noopener noreferrer\" target=\"_blank\">ESET PROTECT dashboard<\/a>.<\/li>\n<li>Click <strong>New<\/strong>, then select <strong>Client Task<\/strong>.<\/li>\n<li>Give it a sensible name, like 'Upgrade Management Agent' \u2014 this helps keep track.<\/li>\n<li>Choose <strong>ESET PROTECT Components Upgrade<\/strong> from the task options and hit <strong>Continue<\/strong>.<\/li>\n<li>Accept the terms, then pick a server from the list \u2014 honestly, any server works here, just pick one. Hit <strong>OK<\/strong>.<\/li>\n<li>If you want the clients to reboot automatically after the upgrade, toggle that option, then click <strong>Continue<\/strong>.<\/li>\n<li>Create a trigger: type a name, like 'Upgrade Agents ASAP', then click <strong>Continue<\/strong>.<\/li>\n<li>Add targets \u2014 select the machines with outdated agents that aren\u2019t getting policies, then click <strong>OK<\/strong>.<\/li>\n<li>Set the trigger to run <strong>As soon As Possible<\/strong> to get fresh versions out quickly or schedule it for later if you want.<\/li>\n<li>Hit <strong>Finish<\/strong> to create the task.<\/li>\n<li>Now wait a few minutes, then check the <strong>Tasks<\/strong> area. If things are 'Finished', consider sending a <strong>Wake-Up Call<\/strong> to those machines, so they connect and grab the new policy.<\/li>\n<li>To do that, go to the <strong>Computers<\/strong> tab, find the target machine, click the three dots, and select <strong>Send Wake-up Call<\/strong>.<\/li>\n<li>Finally, verify if the policy is applied by checking the <strong>Configuration &gt; Applied Policies<\/strong> for each machine.<\/li>\n<\/ul>\n<p><strong>Heads up:<\/strong> Sometimes the agent update works on the first try, sometimes not. If it stalls or you see errors, restarting the machine or manually reinstalling the agent might be necessary. Also, making sure the client can connect to the server without firewall blocks is crucial \u2014 Windows or network security stuff can ruin your day.<\/p>\n<h3>Conclusion<\/h3>\n<p>Basically, outdated agents are the sneaky culprits behind policies not applying. Double-check their versions, update if needed, and force a connection with a wake-up call. Sometimes, just a reboot helps too. If it still doesn\u2019t work, make sure the clients are connected, not blocked by firewalls, and not conflicting with other policies. The key is keeping the agent current so everything plays nice.<\/p>\n<ul>\n<li>Check agent version on clients.<\/li>\n<li>Update if outdated.<\/li>\n<li>Send wake-up calls to force connections.<\/li>\n<li>Verify policy application.<\/li>\n<\/ul>\n<p>Hopefully this shaves off a few hours for someone. Troubleshooting odd policy issues blows, but at least with this approach, you can usually get it sorted.<\/p>\n<p> <\/code><\/code><\/p>\n","protected":false},"excerpt":{"rendered":"<p>D\u00e9j\u00e0 vu. Appliquer une r\u00e8gle de pare-feu via ESET PROTECT \u00e0 plusieurs machines clientes peut para\u00eetre simple, mais ce n&rsquo;est pas toujours le cas. Le<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-3010","post","type-post","status-publish","format-standard","hentry","category-aide"],"_links":{"self":[{"href":"https:\/\/help.peacedoorball.blog\/ca\/wp-json\/wp\/v2\/posts\/3010","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/help.peacedoorball.blog\/ca\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/help.peacedoorball.blog\/ca\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/help.peacedoorball.blog\/ca\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/help.peacedoorball.blog\/ca\/wp-json\/wp\/v2\/comments?post=3010"}],"version-history":[{"count":0,"href":"https:\/\/help.peacedoorball.blog\/ca\/wp-json\/wp\/v2\/posts\/3010\/revisions"}],"wp:attachment":[{"href":"https:\/\/help.peacedoorball.blog\/ca\/wp-json\/wp\/v2\/media?parent=3010"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/help.peacedoorball.blog\/ca\/wp-json\/wp\/v2\/categories?post=3010"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/help.peacedoorball.blog\/ca\/wp-json\/wp\/v2\/tags?post=3010"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}