<?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 Upgrade and testing in Privilege Cloud Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/upgrade-and-testing/m-p/1407865#M5751</link>
    <description>&lt;P&gt;Hi everyone,&lt;/P&gt;&lt;P&gt;We currently have &lt;B&gt;four PSM servers&lt;/B&gt; connected to &lt;B&gt;CyberArk Privilege Cloud&lt;/B&gt;.&lt;/P&gt;&lt;P&gt;I'm interested in understanding how other organisations manage &lt;B&gt;testing prior to upgrading PSM servers&lt;/B&gt;. Specifically:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Do you have dedicated &lt;B&gt;test or non-production PSM servers&lt;/B&gt;, or do you test on production servers?&lt;/LI&gt;&lt;LI&gt;How do you validate that all your connection components (RDP, SSH, SQL, WinSCP, etc.) continue to work after an upgrade?&lt;/LI&gt;&lt;LI&gt;Do you have an automated regression test process, or is it all manual?&lt;/LI&gt;&lt;LI&gt;How do you handle custom connection components and ensure they remain compatible after upgrades?&lt;/LI&gt;&lt;LI&gt;If you're using HTML5 connectors, do you validate those separately from the native connectors?&lt;/LI&gt;&lt;LI&gt;Do you keep a rollback plan, and if so, what does that look like?&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;We're trying to establish a repeatable testing process before applying future upgrades, and I'd be interested to hear how others have approached this.&lt;/P&gt;&lt;P&gt;Any recommendations, lessons learned, or best practices would be greatly appreciated.&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;&lt;B&gt;Martin&lt;/B&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 28 Jul 2026 13:18:28 GMT</pubDate>
    <dc:creator>MUnderdown</dc:creator>
    <dc:date>2026-07-28T13:18:28Z</dc:date>
    <item>
      <title>Upgrade and testing</title>
      <link>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/upgrade-and-testing/m-p/1407865#M5751</link>
      <description>&lt;P&gt;Hi everyone,&lt;/P&gt;&lt;P&gt;We currently have &lt;B&gt;four PSM servers&lt;/B&gt; connected to &lt;B&gt;CyberArk Privilege Cloud&lt;/B&gt;.&lt;/P&gt;&lt;P&gt;I'm interested in understanding how other organisations manage &lt;B&gt;testing prior to upgrading PSM servers&lt;/B&gt;. Specifically:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Do you have dedicated &lt;B&gt;test or non-production PSM servers&lt;/B&gt;, or do you test on production servers?&lt;/LI&gt;&lt;LI&gt;How do you validate that all your connection components (RDP, SSH, SQL, WinSCP, etc.) continue to work after an upgrade?&lt;/LI&gt;&lt;LI&gt;Do you have an automated regression test process, or is it all manual?&lt;/LI&gt;&lt;LI&gt;How do you handle custom connection components and ensure they remain compatible after upgrades?&lt;/LI&gt;&lt;LI&gt;If you're using HTML5 connectors, do you validate those separately from the native connectors?&lt;/LI&gt;&lt;LI&gt;Do you keep a rollback plan, and if so, what does that look like?&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;We're trying to establish a repeatable testing process before applying future upgrades, and I'd be interested to hear how others have approached this.&lt;/P&gt;&lt;P&gt;Any recommendations, lessons learned, or best practices would be greatly appreciated.&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;&lt;B&gt;Martin&lt;/B&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 28 Jul 2026 13:18:28 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/upgrade-and-testing/m-p/1407865#M5751</guid>
      <dc:creator>MUnderdown</dc:creator>
      <dc:date>2026-07-28T13:18:28Z</dc:date>
    </item>
    <item>
      <title>Re: Upgrade and testing</title>
      <link>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/upgrade-and-testing/m-p/1407866#M5752</link>
      <description>&lt;P&gt;Hi, &lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;It is highly recommended to have a test environment available; keep in mind that there is no rollback process, so you must reinstall the component if something fails.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;You should have a snapshot if the server is virtualized; if it is a physical server, back up the important files located in `C:\Program Files (x86)\CyberArk\`.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Validation is manual; you must perform pre- and post-upgrade tests. I recommend selecting specific accounts for this purpose.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;</description>
      <pubDate>Wed, 26 Aug 2026 16:23:39 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/upgrade-and-testing/m-p/1407866#M5752</guid>
      <dc:creator>phenriqueze</dc:creator>
      <dc:date>2026-08-26T16:23:39Z</dc:date>
    </item>
  </channel>
</rss>

