<?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: Secure workload Agent auto upgrade behaviour in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/secure-workload-agent-auto-upgrade-behaviour/m-p/5322764#M1122337</link>
    <description>&lt;P&gt;gDay to u&amp;nbsp;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/1599919"&gt;@rameshkumarnakka&lt;/a&gt;&amp;nbsp;and yes, I’ve seen similar duplicate agent entries in Secure Workload SaaS. In most cases, it was related to agents being re-registered after upgrades or vm redeployments, which led to duplicate records. A quick check is to validate agent UUIDs and confirm whether the duplicates map to the same host. And if not, it may require a cleanup via support....&lt;/P&gt;&lt;P&gt;hope it helps and PEACE!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;-Enes&lt;/P&gt;</description>
    <pubDate>Thu, 21 Aug 2025 07:23:53 GMT</pubDate>
    <dc:creator>Enes Simnica</dc:creator>
    <dc:date>2025-08-21T07:23:53Z</dc:date>
    <item>
      <title>Secure workload Agent auto upgrade behaviour</title>
      <link>https://community.cisco.com/t5/network-security/secure-workload-agent-auto-upgrade-behaviour/m-p/5322753#M1122336</link>
      <description>&lt;P data-start="63" data-end="79"&gt;&lt;STRONG data-start="63" data-end="77"&gt;Dear Team,&lt;/STRONG&gt;&lt;/P&gt;
&lt;P data-start="81" data-end="283"&gt;We are observing duplicate agent entries in the Secure Workload dashboard. These entries are showing different/same agent versions along with varying check-in and check-out times, which seems unusual.&lt;/P&gt;
&lt;P data-start="285" data-end="463"&gt;Has anyone experienced a similar issue with Secure Workload as a Service (SaaS) running on version &lt;STRONG data-start="384" data-end="419"&gt;3.10.1.1-PATCH-3.10.3.19 (TaaS)&lt;/STRONG&gt;? Any inputs would be greatly appreciated.&lt;/P&gt;
&lt;P data-start="465" data-end="495"&gt;Thanks and regards,&lt;BR data-start="484" data-end="487" /&gt;Ramesh&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 21 Aug 2025 06:40:27 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/secure-workload-agent-auto-upgrade-behaviour/m-p/5322753#M1122336</guid>
      <dc:creator>rameshkumarnakka</dc:creator>
      <dc:date>2025-08-21T06:40:27Z</dc:date>
    </item>
    <item>
      <title>Re: Secure workload Agent auto upgrade behaviour</title>
      <link>https://community.cisco.com/t5/network-security/secure-workload-agent-auto-upgrade-behaviour/m-p/5322764#M1122337</link>
      <description>&lt;P&gt;gDay to u&amp;nbsp;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/1599919"&gt;@rameshkumarnakka&lt;/a&gt;&amp;nbsp;and yes, I’ve seen similar duplicate agent entries in Secure Workload SaaS. In most cases, it was related to agents being re-registered after upgrades or vm redeployments, which led to duplicate records. A quick check is to validate agent UUIDs and confirm whether the duplicates map to the same host. And if not, it may require a cleanup via support....&lt;/P&gt;&lt;P&gt;hope it helps and PEACE!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;-Enes&lt;/P&gt;</description>
      <pubDate>Thu, 21 Aug 2025 07:23:53 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/secure-workload-agent-auto-upgrade-behaviour/m-p/5322764#M1122337</guid>
      <dc:creator>Enes Simnica</dc:creator>
      <dc:date>2025-08-21T07:23:53Z</dc:date>
    </item>
  </channel>
</rss>

