<?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: PSM in Privilege Cloud Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/psm/m-p/1328431#M1749</link>
    <description>&lt;P&gt;Hi Malhar,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks for your response.&lt;/P&gt;&lt;P&gt;We have referred the same KB article and checked every possibility. So we have performed the below steps.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We tried the recommended steps provided by CyberArk. However, the problem still exists.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Steps Performed:&lt;/P&gt;&lt;P&gt;1. Cleared the AppLocker Policy.&lt;/P&gt;&lt;P&gt;2. Executed the AppLocker script from Installation directory and rebooted the server.&lt;/P&gt;&lt;P&gt;3. New Rules are updated in Secpol.msc&lt;/P&gt;&lt;P&gt;4. Tried connecting RDP using PSM Server. Same problem exists.&lt;/P&gt;&lt;P&gt;We again switch the AppLocker Policy from Enforce to Audit. PSM started working fine.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Could you please provide an alternative suggestion or steps to resolve the issue&lt;/P&gt;</description>
    <pubDate>Tue, 27 Feb 2024 12:38:33 GMT</pubDate>
    <dc:creator>CyberArkAlumni</dc:creator>
    <dc:date>2024-02-27T12:38:33Z</dc:date>
    <item>
      <title>PSM</title>
      <link>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/psm/m-p/1328429#M1747</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;Could someone please help us on the below issue.&lt;/P&gt;&lt;P&gt;PSMSC036E No Process was found for image [PSMInitSession.exe],&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Applocker Policy from ‘Enforce’ to ‘Audit’ Mode and tried initiating the PSM session which allowed us to connect successfully. Which confirmed the issue related to Applocker Policy.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We tried the recommended steps provided by CyberArk. However, the problem still exists.&lt;/P&gt;&lt;P&gt;Steps Performed:&lt;/P&gt;&lt;P&gt;1. Cleared the AppLocker Policy.&lt;/P&gt;&lt;P&gt;2. Executed the AppLocker script from Installation directory and rebooted the server.&lt;/P&gt;&lt;P&gt;3. New Rules are updated in Secpol.msc&lt;/P&gt;&lt;P&gt;4. Tried connecting RDP using PSM Server. Same problem exists.&lt;/P&gt;&lt;P&gt;We again switch the AppLocker Policy from Enforce to Audit. PSM started working fine.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Could you please provide an alternative suggestion or steps to resolve the issue.&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Priya&lt;/P&gt;</description>
      <pubDate>Tue, 27 Feb 2024 04:02:16 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/psm/m-p/1328429#M1747</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2024-02-27T04:02:16Z</dc:date>
    </item>
    <item>
      <title>Re: PSM</title>
      <link>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/psm/m-p/1328430#M1748</link>
      <description>&lt;P&gt;Hi @PRIYADHARSHINI NAGARAJAN?&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Please check the following KB. Hope it helps !&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A alt="https://community.cyberark.com/s/article/PSMSC036E-No-Process-was-found-for-image" href="https://community.cyberark.com/s/article/PSMSC036E-No-Process-was-found-for-image" target="_blank"&gt;https://community.cyberark.com/s/article/PSMSC036E-No-Process-was-found-for-image&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 27 Feb 2024 12:33:19 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/psm/m-p/1328430#M1748</guid>
      <dc:creator>M.Vora780263</dc:creator>
      <dc:date>2024-02-27T12:33:19Z</dc:date>
    </item>
    <item>
      <title>Re: PSM</title>
      <link>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/psm/m-p/1328431#M1749</link>
      <description>&lt;P&gt;Hi Malhar,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks for your response.&lt;/P&gt;&lt;P&gt;We have referred the same KB article and checked every possibility. So we have performed the below steps.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We tried the recommended steps provided by CyberArk. However, the problem still exists.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Steps Performed:&lt;/P&gt;&lt;P&gt;1. Cleared the AppLocker Policy.&lt;/P&gt;&lt;P&gt;2. Executed the AppLocker script from Installation directory and rebooted the server.&lt;/P&gt;&lt;P&gt;3. New Rules are updated in Secpol.msc&lt;/P&gt;&lt;P&gt;4. Tried connecting RDP using PSM Server. Same problem exists.&lt;/P&gt;&lt;P&gt;We again switch the AppLocker Policy from Enforce to Audit. PSM started working fine.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Could you please provide an alternative suggestion or steps to resolve the issue&lt;/P&gt;</description>
      <pubDate>Tue, 27 Feb 2024 12:38:33 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/psm/m-p/1328431#M1749</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2024-02-27T12:38:33Z</dc:date>
    </item>
    <item>
      <title>Re: PSM</title>
      <link>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/psm/m-p/1328432#M1750</link>
      <description>&lt;P&gt;What does the entry for PSMInitSession.exe look like in your AppLocker.xml file? Is the path defined correctly/any new drive letters not accounted for in AppLocker?&lt;/P&gt;</description>
      <pubDate>Tue, 27 Feb 2024 16:51:14 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/psm/m-p/1328432#M1750</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2024-02-27T16:51:14Z</dc:date>
    </item>
  </channel>
</rss>

