- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.
06-21-2024 04:28 PM
We went into the local GPO editor and found any RDS settings that were enabled by default and set them to "Not configured" Now all of the local RDS settings are set to “Not configured” but the error still occurs.
Can someone explain what specific GPO or registry settings the ConnectorCheckPrerequisites script is looking for?
02-25-2026 01:06 PM
Yes, looking back at our support case history there were four values that were not in the locations documented by CyberArk, possibly due to Windows Server 2022 being newer than whichever version of the OS the documentation was developed for.
From my ticket:
Two of the four referenced settings are under the “Windows Remote Management (WinRM)” component and not the “Remote Desktop Services” component. These were already set to “Not Configured” (I do not have record of what those two settings are in the support case, they were referenced as above without specifics)
The “Allow Remote Shell Access” setting is under “Windows Remote Shell” component and it was set to “Disabled” we changed it to Not configured and the server passed the local GPO test.
The “Prevent running First Run wizard” setting is under the “Internet Explorer” component and was already set to “Not configured”
06-22-2024 01:43 AM
Hi @Mike Mason,
please check the Knowledge Article Privilege Cloud - How to run the ConnectorCheckPrerequisites script.
The section GPO Failures Probably is your case.
Nino
06-24-2024 09:03 AM
Hi Nino, thanks, unfortunately I did already review that article in detail and it doesn't specify which settings it is checking for. The Windows 2022 server has no GPO's applied so it is impossible to remove the GPO that isn't applied. I can only assume the script is looking for specific registry settings which aren't indicated in the article.
"GPO Failures
The script checks for GPOs that will be problematic for deployment and use of PSM. For any GPO-Local failures, RDS will fail to install until the policy is removed. For GPO-Domain failures, PSM connections will be impacted until the policy is removed. The failure message will indicate the GPO that is the source of the problematic policy. Please update the GPO that is being pushed to the machine to turn off any cited issue GPOs from the script. In this above example the team would adjust the "Allow users to connect remotely by using Remote Desktop" policy, to "Not Configured". As part of the prerequisites, CyberArk asks that we disable all enterprise/corporate GPOs applied to the Connector servers. "
Per these instructions we have disabled all enterprise GPO's that would normally be applied to a new server and have set the OU they are part of to prevent inheritence.
04-11-2025 09:59 AM
In my case, ConnectorCheckPrerequisites_PrivilegeCloud.ps1 showed this in the result:
Failure GPO-Domain: Allow remote server management through WinRM Not Configured Enabled Source GPO: network.dev Domain Expected:Not Configured Actual:Enabled
Failure GPO-Domain Domain GPOs empty Domain GPOs found Must remove problematic domain GPOs for RDS installation to succeed.
02-25-2026 12:21 PM
Hi Mike,
Currently experiencing a similar issue. Were you able to resolve this error?
02-25-2026 01:06 PM
Yes, looking back at our support case history there were four values that were not in the locations documented by CyberArk, possibly due to Windows Server 2022 being newer than whichever version of the OS the documentation was developed for.
From my ticket:
Two of the four referenced settings are under the “Windows Remote Management (WinRM)” component and not the “Remote Desktop Services” component. These were already set to “Not Configured” (I do not have record of what those two settings are in the support case, they were referenced as above without specifics)
The “Allow Remote Shell Access” setting is under “Windows Remote Shell” component and it was set to “Disabled” we changed it to Not configured and the server passed the local GPO test.
The “Prevent running First Run wizard” setting is under the “Internet Explorer” component and was already set to “Not configured”
02-25-2026 03:10 PM
This is greatly helpful. I appreciate your taking the time to follow up with me.
Thank you so much!
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!

