<?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>article Windows 2019 RDS Server for PSM in PAM Self-Hosted Articles</title>
    <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-articles/windows-2019-rds-server-for-psm/ta-p/1428170</link>
    <description>Windows 2019 RDS Server for PSM with "Per User" CALs. After activating RD Licensing Server, users start to experience the error:&lt;BR /&gt;&lt;BR /&gt;Error with PSM: "Remote Desktop Licensing Issue" There is a problem with your Remote Desktop License, and your session will be disconnected in 60 minutes. Contact your system administrator to fix this problem.

&lt;H3&gt;Steps&lt;/H3&gt;
&lt;P&gt;Windows 2019 changed the way sessions are managed if there's a problem provisioning the RDS license and generates this error if it cannot provision the license. RDS cannot provision a RDS CAL to a local or Workgroup user. For this to work correctly, PSM must be moved to use a domain account for the PSM Connect and PSM Admin Connect users per this document:&amp;nbsp;&lt;BR /&gt;&lt;A href="https://docs.cyberark.com/Product-Doc/OnlineHelp/PAS/Latest/en/Content/PAS%20INST/Optional-Moving-the-PSMConnec-and-PSMAdminConnect-users-to-your-Domain.htm" target="_blank"&gt;https://docs.cyberark.com/Product-Doc/OnlineHelp/PAS/Latest/en/Content/PAS%20INST/Optional-Moving-the-PSMConnec-and-PSMAdminConnect-users-to-your-Domain.htm&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;After moving to a domain account, this error goes away. You can also look at the RDS CAL licensing report and see that a license has been issued to the PSM Connect user.&lt;BR /&gt;&lt;BR /&gt;Additionally, you can change your RDS licensing model to per-device and this should work as well.&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 23 Oct 2025 05:02:20 GMT</pubDate>
    <dc:creator>CyberArkAlumni</dc:creator>
    <dc:date>2025-10-23T05:02:20Z</dc:date>
    <item>
      <title>Windows 2019 RDS Server for PSM</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-articles/windows-2019-rds-server-for-psm/ta-p/1428170</link>
      <description>Windows 2019 RDS Server for PSM with "Per User" CALs. After activating RD Licensing Server, users start to experience the error:&lt;BR /&gt;&lt;BR /&gt;Error with PSM: "Remote Desktop Licensing Issue" There is a problem with your Remote Desktop License, and your session will be disconnected in 60 minutes. Contact your system administrator to fix this problem.

&lt;H3&gt;Steps&lt;/H3&gt;
&lt;P&gt;Windows 2019 changed the way sessions are managed if there's a problem provisioning the RDS license and generates this error if it cannot provision the license. RDS cannot provision a RDS CAL to a local or Workgroup user. For this to work correctly, PSM must be moved to use a domain account for the PSM Connect and PSM Admin Connect users per this document:&amp;nbsp;&lt;BR /&gt;&lt;A href="https://docs.cyberark.com/Product-Doc/OnlineHelp/PAS/Latest/en/Content/PAS%20INST/Optional-Moving-the-PSMConnec-and-PSMAdminConnect-users-to-your-Domain.htm" target="_blank"&gt;https://docs.cyberark.com/Product-Doc/OnlineHelp/PAS/Latest/en/Content/PAS%20INST/Optional-Moving-the-PSMConnec-and-PSMAdminConnect-users-to-your-Domain.htm&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;After moving to a domain account, this error goes away. You can also look at the RDS CAL licensing report and see that a license has been issued to the PSM Connect user.&lt;BR /&gt;&lt;BR /&gt;Additionally, you can change your RDS licensing model to per-device and this should work as well.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 23 Oct 2025 05:02:20 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-articles/windows-2019-rds-server-for-psm/ta-p/1428170</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2025-10-23T05:02:20Z</dc:date>
    </item>
  </channel>
</rss>

