<?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 RDP Proxy with Windows 11 in PAM Self-Hosted Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/psm-rdp-proxy-with-windows-11/m-p/1305887#M8321</link>
    <description>&lt;P&gt;Does it still work for you fine?&lt;/P&gt;&lt;P&gt;I have customer that is on W11 23h2 but we get ""Try connecting again. If the problem continues, contact the owner of the remote computer or your network administrator Code: 0x907".&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Tried the CyberArk solution with adding permissions to PSMConnect on the MSLicensing registry but without any change -&amp;gt; https://community.cyberark.com/s/article/Issues-with-Remote-Desktop-on-End-user-Machine-after-Windows11-Update&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Randomly it fails with above mentioned MS error, but only on the LB VIP address. If we go directly using the specific PSM it works fine.&lt;/P&gt;&lt;P&gt;Can it be related to the signature algorithm? The Root CA is using sha1, the LB cert is on sha256.&lt;/P&gt;</description>
    <pubDate>Wed, 08 May 2024 11:31:33 GMT</pubDate>
    <dc:creator>KKlimoszek01</dc:creator>
    <dc:date>2024-05-08T11:31:33Z</dc:date>
    <item>
      <title>PSM RDP Proxy with Windows 11</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/psm-rdp-proxy-with-windows-11/m-p/1305882#M8316</link>
      <description>&lt;P&gt;Hi community,&lt;/P&gt;&lt;P&gt;does someone encountered the issue that the PSM RDP Proxy does not prompt for password if in the RDP file the parameter username:s:userx is defined?&lt;/P&gt;&lt;P&gt;If the username parameter is empty, it works as designed.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Interesting though that with username defined, it work on Windows 10, issue is only on Windows 11.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Any idea?&lt;/P&gt;</description>
      <pubDate>Mon, 30 Jan 2023 10:25:29 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/psm-rdp-proxy-with-windows-11/m-p/1305882#M8316</guid>
      <dc:creator>balazs_racz</dc:creator>
      <dc:date>2023-01-30T10:25:29Z</dc:date>
    </item>
    <item>
      <title>Re: PSM RDP Proxy with Windows 11</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/psm-rdp-proxy-with-windows-11/m-p/1305883#M8317</link>
      <description>&lt;P&gt;Yes, I have this issue as well.  I assume it is a change with the underlying version of RDP.  I just leave it undefined on my computer now and in my Autohotkey-based GUI for this, I get the OS version and set or unset this setting based on that.&lt;/P&gt;</description>
      <pubDate>Mon, 13 Feb 2023 16:40:38 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/psm-rdp-proxy-with-windows-11/m-p/1305883#M8317</guid>
      <dc:creator>jr_tolleson</dc:creator>
      <dc:date>2023-02-13T16:40:38Z</dc:date>
    </item>
    <item>
      <title>Re: PSM RDP Proxy with Windows 11</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/psm-rdp-proxy-with-windows-11/m-p/1305884#M8318</link>
      <description>&lt;P&gt;The root cause is the Windows 11 upgrade from version 21H2 to 22H2. I'm opening a Sev B case with Microsoft. But since CyberArk supports a customized RDP file they need to do some serious research on this.&lt;/P&gt;</description>
      <pubDate>Thu, 09 Mar 2023 15:26:34 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/psm-rdp-proxy-with-windows-11/m-p/1305884#M8318</guid>
      <dc:creator>cjacob</dc:creator>
      <dc:date>2023-03-09T15:26:34Z</dc:date>
    </item>
    <item>
      <title>Re: PSM RDP Proxy with Windows 11</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/psm-rdp-proxy-with-windows-11/m-p/1305885#M8319</link>
      <description>&lt;P&gt;since we upgraded to W11 23h2, this issue is solved on my side.&lt;/P&gt;&lt;P&gt;with W11 22h2, we used mobaxterm rdp session (and test other rdp manager) and it's works too, only the native RDP executable is broken.&lt;/P&gt;</description>
      <pubDate>Thu, 18 Jan 2024 16:16:26 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/psm-rdp-proxy-with-windows-11/m-p/1305885#M8319</guid>
      <dc:creator>lioG</dc:creator>
      <dc:date>2024-01-18T16:16:26Z</dc:date>
    </item>
    <item>
      <title>Re: PSM RDP Proxy with Windows 11</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/psm-rdp-proxy-with-windows-11/m-p/1305886#M8320</link>
      <description>&lt;P&gt;Does it still work for you fine?&lt;/P&gt;&lt;P&gt;I have customer that is on W11 23h2 but we get ""Try connecting again. If the problem continues, contact the owner of the remote computer or your network administrator Code: 0x907".&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Tried the CyberArk solution with adding permissions to PSMConnect on the MSLicensing registry but without any change -&amp;gt; https://community.cyberark.com/s/article/Issues-with-Remote-Desktop-on-End-user-Machine-after-Windows11-Update&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Randomly it fails with above mentioned MS error, but only on the LB VIP address. If we go directly using the specific PSM it works fine.&lt;/P&gt;&lt;P&gt;Can it be related to the signature algorithm? The Root CA is using sha1, the LB cert is on sha256.&lt;/P&gt;</description>
      <pubDate>Wed, 08 May 2024 11:31:33 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/psm-rdp-proxy-with-windows-11/m-p/1305886#M8320</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2024-05-08T11:31:33Z</dc:date>
    </item>
    <item>
      <title>Re: PSM RDP Proxy with Windows 11</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/psm-rdp-proxy-with-windows-11/m-p/1305887#M8321</link>
      <description>&lt;P&gt;Does it still work for you fine?&lt;/P&gt;&lt;P&gt;I have customer that is on W11 23h2 but we get ""Try connecting again. If the problem continues, contact the owner of the remote computer or your network administrator Code: 0x907".&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Tried the CyberArk solution with adding permissions to PSMConnect on the MSLicensing registry but without any change -&amp;gt; https://community.cyberark.com/s/article/Issues-with-Remote-Desktop-on-End-user-Machine-after-Windows11-Update&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Randomly it fails with above mentioned MS error, but only on the LB VIP address. If we go directly using the specific PSM it works fine.&lt;/P&gt;&lt;P&gt;Can it be related to the signature algorithm? The Root CA is using sha1, the LB cert is on sha256.&lt;/P&gt;</description>
      <pubDate>Wed, 08 May 2024 11:31:33 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/psm-rdp-proxy-with-windows-11/m-p/1305887#M8321</guid>
      <dc:creator>KKlimoszek01</dc:creator>
      <dc:date>2024-05-08T11:31:33Z</dc:date>
    </item>
  </channel>
</rss>

