Privilege session cannot be started after upgrade to OS 2022 from OS 2016

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

Privilege session cannot be started after upgrade to OS 2022 from OS 2016

L3 Networker

We have upgraded the OS of our PSM server from windows server 2016 to windows server 2022.

However, after the upgrade we are unable to start the remote session and we are getting an error in the first hop (PVWA->PSM), the error says - The privilege session cannot be established securely.

 

 

 

What we have tried so far:

1. Ran the PSMHardening and App locker hardening- all good

2. Ran the PSM checker tool - no error

3. Ran the CreateCred helper to reset PSMApp users pwd, the script successfully, reset the creds however, gave an error-

[2024-11-24 08:52:43] [ERROR] PSM Log 'D:\Program Files (x86)\Cyberark\PSM\Logs\PSMTrace.log' has some errors, please check it.

Further looking at logs, we see below error:

[25/11/2024 | 06:35:13.824963] | {pid= 4076} | {tid= 7992} | class CPSMSessionLogonRequestHandler * | PSM\PSMServer\PSMSessionLogonRequestHandler.cpp(81) | :: | PSMSR1379I Acknowledged Logon message type.

[25/11/2024 | 06:35:13.825036] | {pid= 4076} | {tid= 7992} | class CPSMGetCredentialByUUIDRequestHandler * | PSM\PSMServer\PSMGetCredentialByUUIDRequestHandler.cpp(38) | :: | PSMSR1009I Handling [Get Credential] message request for logon of session id: 2

[25/11/2024 | 06:35:13.825102] | {pid= 4076} | {tid= 7992} | class CPSMBaseException * | PSM\PSMServer\PSMBaseException.cpp(38) | :: | PSMSR009I Privileged Session Manager exception occurred. PSMSR983E The session [899c832a-0e21-409c-bd57-a238d956f771] is being stopped because the Protocol Provider didn't run. (Codes: -1, -1)

[25/11/2024 | 06:35:13.825200] | {pid= 4076} | {tid= 7992} | class CPSMBaseException * | PSM\PSMServer\PSMBaseException.cpp(38) | :: | PSMSR009I Privileged Session Manager exception occurred. PSMSR893E Session id was not found in session synchronizer. Diagnostic information: 6, (Session id: 2) (Codes: -1, -1)

[25/11/2024 | 06:35:13.825276] | {pid= 4076} | {tid= 7992} | class CPSMBaseException * | PSM\PSMServer\PSMBaseException.cpp(38) | :: | PSMSR009I Privileged Session Manager exception occurred. PSMSR955E Failed to get the session uuid by session id (Session ID: 2). Reason: PSMSR893E Session id was not found in session synchronizer. Diagnostic information: 6, (Session id: 2) (Codes: -1, -1)

[25/11/2024 | 06:35:13.825361] | {pid= 4076} | {tid= 7992} | class CPSMBaseException * | PSM\PSMServer\PSMBaseException.cpp(38) | :: | PSMSR009I Privileged Session Manager exception occurred. PSMSR923E Failed to remove the session parameters from the session in the session synchronizer (Session id: 2). Reason: PSMSR955E Failed to get the session uuid by session id (Session ID: 2). Reason: PSMSR893E Session id was not found in session synchronizer. Diagnostic information: 6, (Session id: 2) (Codes: -1, -1)

[25/11/2024 | 06:35:13.825428] | {pid= 4076} | {tid= 7992} | class CPSMSessionLogonRequestHandler * | PSM\PSMServer\PSMSessionLogonRequestHandler.cpp(172) | :: | PSMSR926W Failed to remove the session parameters for session id: 2. Reason: PSMSR923E Failed to remove the session parameters from the session in the session synchronizer (Session id: 2). Reason: PSMSR955E Failed to get the session uuid by session id (Session ID: 2). Reason: PSMSR893E Session id was not found in session synchronizer. Diagnostic information: 6, (Session id: 2)

[25/11/2024 | 06:35:13.825490] | {pid= 4076} | {tid= 7992} | class CPSMBaseException * | PSM\PSMServer\PSMBaseException.cpp(38) | :: | PSMSR009I Privileged Session Manager exception occurred. PSMSR891E Failed to handle the session logon request. Diagnostic information: 2, Reason: PSMSR983E The session [899c832a-0e21-409c-bd57-a238d956f771] is being stopped because the Protocol Provider didn't run. (Codes: -1, -1)

 

We have PSMConnect and PSMAdminConnect as domain users. What could be the root cause? I do not want to re-build entire PSM just for this.

1 accepted solution

Accepted Solutions

This is the response i received from cyberark, this was very shocking for me and felt like I am living in 2000 era with CyberArk:

 

Thank you for reaching out to CyberArk Support,

 

When upgrading the Windows Server OS on a machine running CyberArk's Privileged Session Manager (PSM), it's not recommended to perform an in-place upgrade; instead, you should migrate the PSM to a new server with the upgraded OS by reinstalling PSM on the new machine as CyberArk does not support in-place OS upgrades for PSM and recommends a fresh installation on the new operating system.

 

Here is a ref. KBA for the same this can be applied for any windows OS not only 2019.

 

https://community.cyberark.com/s/article/upgrade-OS-of-component-server-PVWA-CPM-PSM

 

So I can recommend now to uninstall and re-install PSM from scratch and see if it resolves the issue.

 

Let me know if any assistance requires so I can set up a quick call and work with you.

View solution in original post

7 REPLIES 7

L7 Applicator

hey @Ankit Kumar​ 

If you check the psmconsole.log do you see any errors related to the application?

 

Have you tried a repair install of the psm yet? if not, give that a try.

 

-Matt

L6 Presenter

Most of the log shared is errors related to session tear-down, and doesn't quite indicate what the source of the problem was.

 

I would bet that the PSM domain user conversion has been altered in some way during the upgrade.

 

The PSMHardening.ps1 file, and the PSMConfigureApplocker.xml file should both have the domain PSMConnect users listed in them (in the same format in both files like domain.com\psmconnect).

 

The Remote Desktop Users group should contain the domain PSM users on the system. This may also contain some domain-based users that need direct PSM access (like using an RDP connection manager, for instance).

 

The domain-based PSM users also need permissions over the PSM file structure, so ensure that you run hardening again if you find that the domain users weren't listed in the hardening.ps1 file (this will apply the permissions).

 

You could also check to ensure that the PSM server entry in the PVWA still reflects the domain-based PSMConnect user, just in case the upgrade updated the PVWA settings for the system.

L6 Presenter

Are the GPOs also in place? Are the domain level PSM users in the right policy? Computer Configuration > Policies > Windows Settings > Security Settings > Local Policies > User Rights Assignment -> Allow log on through Remote Desktop Services

Unfortunately, cyberark support has come back and told that in-place OS upgrade is not supported. I must move PSM to new server which is already on new OS, which is kind of super strange

This is the response i received from cyberark, this was very shocking for me and felt like I am living in 2000 era with CyberArk:

 

Thank you for reaching out to CyberArk Support,

 

When upgrading the Windows Server OS on a machine running CyberArk's Privileged Session Manager (PSM), it's not recommended to perform an in-place upgrade; instead, you should migrate the PSM to a new server with the upgraded OS by reinstalling PSM on the new machine as CyberArk does not support in-place OS upgrades for PSM and recommends a fresh installation on the new operating system.

 

Here is a ref. KBA for the same this can be applied for any windows OS not only 2019.

 

https://community.cyberark.com/s/article/upgrade-OS-of-component-server-PVWA-CPM-PSM

 

So I can recommend now to uninstall and re-install PSM from scratch and see if it resolves the issue.

 

Let me know if any assistance requires so I can set up a quick call and work with you.

This is the response i received from cyberark, this was very shocking for me and felt like I am living in 2000 era with CyberArk:

 

Thank you for reaching out to CyberArk Support,

 

When upgrading the Windows Server OS on a machine running CyberArk's Privileged Session Manager (PSM), it's not recommended to perform an in-place upgrade; instead, you should migrate the PSM to a new server with the upgraded OS by reinstalling PSM on the new machine as CyberArk does not support in-place OS upgrades for PSM and recommends a fresh installation on the new operating system.

 

Here is a ref. KBA for the same this can be applied for any windows OS not only 2019.

 

https://community.cyberark.com/s/article/upgrade-OS-of-component-server-PVWA-CPM-PSM

 

So I can recommend now to uninstall and re-install PSM from scratch and see if it resolves the issue.

 

Let me know if any assistance requires so I can set up a quick call and work with you.

This makes sense to me. An in-place upgrade changes the OS a great deal and there is no real way for the software to accommodate this.

 

-Matt

  • 1 accepted solution
  • 687 Views
  • 7 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!