- 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.
This article will help outline and guide customers when running the Connector Management Prerequisites script, provided by Idira as part of the Privilege Cloud Tools in the Marketplace, linked here: https://community.cyberark.com/marketplace/s/#a352J000000GWAZQA4-a392J000002tNgLQAU
The Connector Management Prerequisite performs several readiness checks and tasks to ensure minimum requirements are met and to prepare a system for Privilege Cloud Connector deployment using Connector Management.
The public IP address(es) of the servers have been whitelisted by CyberArk
Your Idira cloud tenant subdomain
The [email protected] credential. Please refer to the following URL for guidance: https://community.cyberark.com/s/article/Privilege-Cloud-How-to-locate-and-update-the-InstallerUser-...
The following files related to the script can be found in the Privilege Cloud Tools package:
Connector Management Prerequisites\CMReadme.txt – Script readme file
Connector Management Prerequisites\ConnectorCheckPrerequisites_PrivilegeCloud.ps1 – The Connector Management prerequisite script
VaultOperationsTester – used for CPM connection test (do not modify folder structure)
The script has several execution modes specified by the switches included when the script is run. Please choose and execute one of the following commands in an Admin instance of PowerShell.
During execution, it will also generate a file called "ConnectorCheckPrerequisites_PrivilegeCloud.ini" that will store the parameters provided during runtime. If you made a mistake and want to rerun the script, we recommend you edit this file with the proper details or delete it.
The default run of the script will perform the readiness checks, the CPM connection test, and install RDS.
.\ConnectorCheckPrerequisistes_PrivilegeCloud.ps1
At the end of the base script, an additional prompt to install the RDS roles/services will appear. If testing prior to implementation, you can choose “No” and skip this step.
Run checks if the machine is out of the domain
.\ ConnectorCheckPrerequisistes_PrivilegeCloud.ps1 -OutOfDomain
Run in POC mode
.\ ConnectorCheckPrerequisistes_PrivilegeCloud.ps1 -POC
Access the Troubleshooting menu
.\ ConnectorCheckPrerequisistes_PrivilegeCloud.ps1 -Troubleshooting
Run CPM Connection Test using the [email protected] account
.\ ConnectorCheckPrerequisistes_PrivilegeCloud.ps1 -CPMConnectionTest
Install RDS only:
.\ ConnectorCheckPrerequisistes_PrivilegeCloud.ps1 -InstallRDS
<ScriptDir>\<Computer Name> PublicIP.txt - will try to query machine public IP by reaching https://ipinfo.io
<ScriptDir>\_ ConnectorCheckPrerequisites_PrivilegeCloud.log - General log for the script itself.
<ScriptDir>\_ ConnectorCheckPrerequisites_PrivilegeCloud.ini - stores information entered in script prompts for added convenience on subsequent runs
VaultOperationsTester\Log\*.logs
To update the password please see https://community.cyberark.com/s/article/Privilege-Cloud-How-to-locate-and-update-the-InstallerUser-...
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, Idira asks that we disable all enterprise/corporate GPOs applied to the Connector servers.
If the RDS role or features fail to install, a common cause is the Windows operating system has been modified from its original form (e.g. through hardening, policy, or software installation) or system file corruption. Examples would be non en-US ISO images, language packs, etc.
You can run the script with the -Troubleshooting flag to perform various helpful commands: