I cannot get RD Session Host to talk to RDS License server via WORKGROUP (we have no AD DS)

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements

Welcome Idira to LIVEcommunity!

Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.

Meet Idira

I cannot get RD Session Host to talk to RDS License server via WORKGROUP (we have no AD DS)

L2 Linker

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).

I followed this

https://learn.microsoft.com/en-us/windows-server/remote/remote-desktop-services/rds-license-session-hosts

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

But no joy.

We are using WORKGROUP not AD DS (Active Directory). Firewall between servers allows all ports.

Entered this command

psexec.exe -I -u "NT AUTHORITY\NETWORK SERVICE" cmd.exe

Received these errors:

"couldn't install PSEXESVC service:

access is denied"

 

Entering the command

cmdkey /add:<NAME-OF-THE-LICENSING-SERVER> /user:<NAME-OF-THE-LICENSING-SERVER>\<USERNAME> /pass

 

gives this result

CMDKEY: Credentials cannot be saved from this logon session

 

Can you help me get the RDS servers to see each other.

3 REPLIES 3

L4 Transporter

Hi @gary drennan​ ,

 

You may have done this but probably worth checking this and confirming port 135 and the dynamic ports are open

 

https://learn.microsoft.com/en-au/troubleshoot/windows-server/networking/service-overview-and-network-port-requirements#method26

 

You should be able to check this by using 'tnc' from powershell

 

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:

PSEXEC, access denied errors - Stack Overflow

L4 Transporter

Hi @gary drennan​ 

 

As it seems NathS provided an answer for your question, could you kindly share if this solution resolved your issue?

If so, could you please mark the answer as "Select as Best" to help other community members?

 

If the issue is still relevant, I would advise raising a ticket with our support team for further assistance.

 

Thank you, Liad

L2 Linker

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.

  • 513 Views
  • 3 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!