A recently-hired colleague onboarded five new Local Accounts that are used for five standalone Windows Servers. After attempting to connect to the servers from PVWA, the colleague noticed that the "Connect" button was greyed out for all five new accounts.
What can you do to help your colleague resolve this issue? (Choose two.)
To resolve the issue where the 'Connect' button is greyed out for new accounts, first ensure that the address field is populated with either an IP address or a fully qualified domain name (FQDN) of each server. This is crucial because without this information, the system will not know where to connect. Additionally, it is important to verify that the correct Privileged Session Manager (PSM) connection component is selected within the account platform settings. This configuration is necessary for the PSM to establish a remote session to the servers.
The answer are A and B. https://cyberark-customers.force.com/s/question/0D52J00007JporGSAR/connect-button-is-grayed-out-after-duplicating-a-platform
The link does not answer this, but agree on AB.
Answer is AB
The issue where the "Connect" button is greyed out for the new local accounts in PVWA can be resolved by addressing two key configuration requirements in CyberArk: Ensure the server address is specified (Option A): The PSM requires the target server's IP or FQDN to establish a connection. If the address field for the account is empty, the PSM cannot route the session, resulting in the "Connect" button being disabled. Populating this field is essential for session connectivity. Verify the PSM connection component in the platform (Option B): The account's platform must include the correct PSM connection component (e.g., PSM-RDP for Windows servers). Without this component, the PVWA cannot initiate the session via the PSM, leaving the "Connect" button inactive.