- 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.
05-27-2025 08:04 AM
Current Environment Setup:
Scenario & Question:
I'm trying to understand the expected behavior when one PSM server experiences a service failure. Specifically:
If the PSM Session Manager service goes down on ONE of the four servers, what should happen when a user attempts to establish a privileged session?
Expected Behavior Options:
What I Need to Know:
Additional Context:
Has anyone experienced similar scenarios? What was your resolution approach?
Any insights from CyberArk experts or those with similar multi-PSM deployments would be greatly appreciated!
05-27-2025 08:11 AM
If the psm service has failed, then in your setup your lb may not detect this if the rdp service is still up.
CyberArk itself won't know either so your load balancer could still route traffic to the failed server .
Psm Health check was designed to monitor the psm service and the rdp service and report when one has failed .
https://community.cyberark.com/marketplace/s/#a352J000000ai0MQAQ-a392J000002QBA6QAO
This is the usual way people monitor and keep high availability for psm pools , unless you set up synthetic monitoring where you run test connections and note the response.
The psm health check also has the ability to let you drain psm servers before rebooting , just shut down iis and the load balancer will stop routing traffic to it .
05-27-2025 08:11 AM
If the psm service has failed, then in your setup your lb may not detect this if the rdp service is still up.
CyberArk itself won't know either so your load balancer could still route traffic to the failed server .
Psm Health check was designed to monitor the psm service and the rdp service and report when one has failed .
https://community.cyberark.com/marketplace/s/#a352J000000ai0MQAQ-a392J000002QBA6QAO
This is the usual way people monitor and keep high availability for psm pools , unless you set up synthetic monitoring where you run test connections and note the response.
The psm health check also has the ability to let you drain psm servers before rebooting , just shut down iis and the load balancer will stop routing traffic to it .
05-28-2025 03:34 AM
Agree with everything mentioned by @Malcolm Murray
A few of my notes:
05-28-2025 05:28 AM
I'm trying to understand how the system handles PSM server failures and load balancing. From what I understand, there's currently no failover or session resumption capability between PSM servers - if a PSM goes offline, any active sessions on that server are lost.
My specific question: When a user initiates a session and one PSM server's service is malfunctioning, does the load balancer automatically redirect the request to another available PSM server, or does it simply deny the service and return error code PSMSR1103E?
It seems like the load balancer might not be sophisticated enough to detect Windows service-level issues with the CyberArk components for proper failover. Can anyone clarify how this scenario is actually handled?
05-28-2025 05:45 AM
From the PAM environments that I've seen, the loadbalancer only uses port 3389 availability, and (if the PSM HealthCheck service is installed) the PSM HealthCheck webpage result to determine if it should send new RDP sessions to a given PSM in a farm. So in the situation you described, users could be sent to a PSM that then presents an error and closes the session.
You could develop a script that runs on each PSM, regularly checks the logs and Windows events, and shuts down the PSM HealthCheck app if there are session-related or logon-related errors. Or maybe your loadbalancer solution can "reach into" the PSM servers and check this information on its own.
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!

