- 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.
09-29-2022 02:36 AM
Hello all,
in-domain hardening settings were applied to PSM servers and afterwards no session is able to lauch via LB address or separately via either PSM servers. In RDP launch download the following is displayed before session to target is lauched:
This privileged session could not be established securely. Try to connect again through the Password Vault Web Access. If this problem persists, contact your system administrator.
In PSM trace logs:
PSMIN136W An error occurred while handling the messaging server client. Error: PSMSR891E Failed to handle the session logon request. Diagnostic information: 1, Reason: PSMSR873E Failed to read parameters from vault file. Reason: PSMSR870E Failed to open vault file. Reason: PSMSR875E Open vault file operation failed [...] Reason: ITATS053E Object [name] does not exist.
PSMIN136W An error occurred while handling the messaging server client. Error: PSMSR891E Failed to handle the session logon request. Diagnostic information: 2, Reason, PSMSR983E The session [...] is being stopped because the Protocol Provider didn't run.
Almost certainly something changed with the new GPO settings. PVWA and CPM rebooted no issues after new GPO settings. Does anybody have any experience in solving this issue or has any hunch where to look for clues? Thanks in advance.
09-30-2022 09:16 AM
Hello eparo,
Were the servers hardened before and you were applying new hardening now? Or are these being hardened for the first time?
On the error "Reason: ITATS053E Object [name] does not exist.", what object is being reported as missing there, does it appear to be an account that corresponds to the PSMConnect user?
If you have domain-based PSM users and are applying domain hardening for the first time, it could be that the hardening GPOs were not updated to reflect the domain-based PSM users. If that is the case in your environment, you can remediate the issue with these steps:
· PSM GPO: Computer Configuration > Policies > Windows Settings > Security Settings > Local Policies > User Rights Assignments > Allow logon through Remote Desktop Services
· Add DOMAIN\PSMConnect
· Add DOMAIN\PSMAdminConnect
· Remove PSMConnect and PSMAdminConnect local users
o Update the CPM GPO to ensure AdminConnect can monitor Connect
· CPM GPO: Computer Configuration > Policies > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Security >Do not allow local administrators to customize permissions
· Set to "Not configured"
o Check to see if this registry key exists on CPM/PSM, and delete it if it does
· Typically present if GPOs were previously applied
· HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services > fWritableTSCCPermTab
10-02-2022 11:43 PM
Hello Jah,
the servers were hardened once during installation as per normal installation procedure, now they were hardened again with the in-domain hardening settings found in installation folder Hardening-folder.
In the console log the object name is a mix of number and letters, however in the trace logs there is an indication as to what this is referring to:
ITATS053E Object [...] does not exist (Vault [PSMServerVault] safe [PSMSessions] user [PSMApp_Test1])
This user shows connected via PVWA system health and no authenitication errors in Vault. This user is also owner of safe PSMSessions. Any ideas?
It seems the policies you asked to be modified cannot be modified by me, because they are set by a GPO (probably the ones applied now).
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!

