<?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: I cannot get RD Session Host to talk to RDS License server via WORKGROUP (we have no AD DS) in Privilege Cloud Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/i-cannot-get-rd-session-host-to-talk-to-rds-license-server-via/m-p/1413986#M6588</link>
    <description>&lt;P&gt;Hi @gary drennan​&amp;nbsp;,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;You may have done this but probably worth checking this and confirming port 135 and the dynamic ports are open&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;https://learn.microsoft.com/en-au/troubleshoot/windows-server/networking/service-overview-and-network-port-requirements#method26&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;You should be able to check this by using 'tnc' from powershell&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I assume you opened powershell/cmd as 'administrator' when running the psexec command? If so, you could check this one out which as common issues for getting access denied:&lt;/P&gt;&lt;P&gt;&lt;A alt="https://stackoverflow.com/questions/828432/psexec-access-denied-errors" href="https://stackoverflow.com/questions/828432/psexec-access-denied-errors" target="_blank"&gt;PSEXEC, access denied errors - Stack Overflow&lt;/A&gt;&lt;/P&gt;</description>
    <pubDate>Wed, 05 Mar 2025 15:16:48 GMT</pubDate>
    <dc:creator>N.Southgate046715</dc:creator>
    <dc:date>2025-03-05T15:16:48Z</dc:date>
    <item>
      <title>I cannot get RD Session Host to talk to RDS License server via WORKGROUP (we have no AD DS)</title>
      <link>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/i-cannot-get-rd-session-host-to-talk-to-rds-license-server-via/m-p/1413985#M6587</link>
      <description>&lt;P&gt;Connecting CyberArk Cloud/System Connectors for Privilege Cloud. We purchased loads of Device CALs and want to use them. RDS license server is on primary system connector, the second connector is not receiving the licenses even after configuring the correct IP address for RD licensing server and setting to Device CALs. I cannot get RD Session Host to talk to RDS License server via WORKGROUP (we have no AD DS).&lt;/P&gt;&lt;P&gt;I followed this&lt;/P&gt;&lt;P&gt;https://learn.microsoft.com/en-us/windows-server/remote/remote-desktop-services/rds-license-session-hosts&lt;/P&gt;&lt;P&gt;I created an account (in administrator group) on the primary server that was added to the second server, both the same password and entered the commands required in the link with &lt;/P&gt;&lt;P&gt;But no joy.&lt;/P&gt;&lt;P&gt;We are using WORKGROUP not AD DS (Active Directory). Firewall between servers allows all ports. &lt;/P&gt;&lt;P&gt;Entered this command&lt;/P&gt;&lt;P&gt;psexec.exe -I -u "NT AUTHORITY\NETWORK SERVICE" cmd.exe&lt;/P&gt;&lt;P&gt;Received these errors:&lt;/P&gt;&lt;P&gt;"couldn't install PSEXESVC service:&lt;/P&gt;&lt;P&gt; access is denied"&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Entering the command&lt;/P&gt;&lt;P&gt;cmdkey /add:&amp;lt;NAME-OF-THE-LICENSING-SERVER&amp;gt; /user:&amp;lt;NAME-OF-THE-LICENSING-SERVER&amp;gt;\&amp;lt;USERNAME&amp;gt; /pass&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;gives this result&lt;/P&gt;&lt;P&gt;CMDKEY: Credentials cannot be saved from this logon session&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Can you help me get the RDS servers to see each other.&lt;/P&gt;</description>
      <pubDate>Tue, 04 Mar 2025 13:28:45 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/i-cannot-get-rd-session-host-to-talk-to-rds-license-server-via/m-p/1413985#M6587</guid>
      <dc:creator>gary_drennan</dc:creator>
      <dc:date>2025-03-04T13:28:45Z</dc:date>
    </item>
    <item>
      <title>Re: I cannot get RD Session Host to talk to RDS License server via WORKGROUP (we have no AD DS)</title>
      <link>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/i-cannot-get-rd-session-host-to-talk-to-rds-license-server-via/m-p/1413986#M6588</link>
      <description>&lt;P&gt;Hi @gary drennan​&amp;nbsp;,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;You may have done this but probably worth checking this and confirming port 135 and the dynamic ports are open&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;https://learn.microsoft.com/en-au/troubleshoot/windows-server/networking/service-overview-and-network-port-requirements#method26&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;You should be able to check this by using 'tnc' from powershell&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I assume you opened powershell/cmd as 'administrator' when running the psexec command? If so, you could check this one out which as common issues for getting access denied:&lt;/P&gt;&lt;P&gt;&lt;A alt="https://stackoverflow.com/questions/828432/psexec-access-denied-errors" href="https://stackoverflow.com/questions/828432/psexec-access-denied-errors" target="_blank"&gt;PSEXEC, access denied errors - Stack Overflow&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 05 Mar 2025 15:16:48 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/i-cannot-get-rd-session-host-to-talk-to-rds-license-server-via/m-p/1413986#M6588</guid>
      <dc:creator>N.Southgate046715</dc:creator>
      <dc:date>2025-03-05T15:16:48Z</dc:date>
    </item>
    <item>
      <title>Re: I cannot get RD Session Host to talk to RDS License server via WORKGROUP (we have no AD DS)</title>
      <link>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/i-cannot-get-rd-session-host-to-talk-to-rds-license-server-via/m-p/1413987#M6589</link>
      <description>&lt;P&gt;Hi @gary drennan​&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;As it seems NathS provided an answer for your question, could you kindly share if this solution resolved your issue?&lt;/P&gt;&lt;P&gt;If so, could you please mark the answer as "Select as Best" to help other community members?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If the issue is still relevant, I would advise raising a ticket with our support team for further assistance.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you, Liad&lt;/P&gt;</description>
      <pubDate>Thu, 03 Apr 2025 08:03:54 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/i-cannot-get-rd-session-host-to-talk-to-rds-license-server-via/m-p/1413987#M6589</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2025-04-03T08:03:54Z</dc:date>
    </item>
    <item>
      <title>Re: I cannot get RD Session Host to talk to RDS License server via WORKGROUP (we have no AD DS)</title>
      <link>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/i-cannot-get-rd-session-host-to-talk-to-rds-license-server-via/m-p/1413988#M6590</link>
      <description>&lt;P&gt;Sorry for the long delay, it seems the issue is not firewall ports etc (turned off firewalls on servers and opened all ports between, no change). The issue seems to be GCP where Administrator account is deleted and hence RDS license server cannot be seen by connectors/RDS session hosts since WORKGROUP and AD DS cannot be established without the Administrator account existing on the Windows Server 2022 VM as a local user. We are looking maybe to move to Azure or AWS since GCP and Microsoft and CyberArk do not seem to have an answer for this. I would recommend CyberArk just fess up and say CyberArk does not support hosting (cloud/system) connector servers/RDS session hosts on GCP.&lt;/P&gt;</description>
      <pubDate>Thu, 03 Apr 2025 11:02:30 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/i-cannot-get-rd-session-host-to-talk-to-rds-license-server-via/m-p/1413988#M6590</guid>
      <dc:creator>gary_drennan</dc:creator>
      <dc:date>2025-04-03T11:02:30Z</dc:date>
    </item>
  </channel>
</rss>

