- 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.
04-19-2024 03:23 PM
When we try direct RDP to AWS PSM sever, getting following error " user profile service service is failed the sign-in and user profile can not be loaded. "
We are using Wndows 2016 Vault Version is V12.2 & PSM is 12.2.14
Even, via Cyberark Vault no one able to access, getting the same error.
Note : Serve is pingable and PSM service is running and all type of RDPs working fine from Cyberark. Only problem to connect AWS PSM server direct RDP and Via Cyberark unable to login
Windows OS login is controlled by our PSM haedening policies? or this is mamanged by windows local policies?
Have any inputs to fix the problem
04-19-2024 03:45 PM
Ho Mal
We have two types of login method.
Regards
SSN
04-19-2024 07:06 PM
Hi @Saravanan Sowndaiyan
Can your WinTel team login using domain administrator account on the PSM server ?
Please check whether the NTUser.DAT file exists and it’s not corrupted.
Also checking the Window Event viewer might help
04-19-2024 10:43 PM
Thanks for the clarification. I thought originally it was only psm sessions affected.
As @Malhar Vora says, potentially there is problems with the user hives etc. I did see a similar problem when someone had one of the default registry hives loaded in regedit which locked the file and caused similar problems.
04-20-2024 01:38 AM
Hi @Malcolm Murray
Thanks, As no one able to access to the server now, we will not be able to check anything on the server. Do we have any way to login to the server firstly to check the problem ? This server hosted in AWS cloud.
Hi @Malhar Vora Wintel team can have option via Cyberark vault to connect this PSM server. We already got the solution. But we want to login to the server firstly to check any thing right. Do we have any option without backed up data restroation? Please let me know.
Thank you.
SS
04-20-2024 08:08 AM
In amazon, you may be able to access it via the amazon gui. You need to chat to your team who manages it to see if they have set up the serial port/console there
You could also try a console session. See
https://learn.microsoft.com/en-us/troubleshoot/windows-server/remote/connect-to-and-shadow-console-session
04-20-2024 09:09 AM
Hi @Malcolm Murray Yes, We already requested client support to check it out, because, client has full permssion on AWS console. Our support team have access restriction.
If that does not work, we go for restart the server from AWS console to see whether we allowed to acces RDP. as next option, which is possible. If that too does not work, we need to go for restoration from the backups.
May I know the reason or possiblities, if NTUser.DAT file does not exist or corrupted.
Regards,
SS
04-21-2024 06:14 PM
Hi @Malcolm Murray - We able to login using CLI and NTUser.DAT file is exist and how to check this file is good or corrupted.
Meanwhile, we are trying to get support from client test RDP from Console.
Regards,
SS
04-22-2024 04:40 AM
Hi @Saravanan Sowndaiyan
One of the ways is to manually load the NTUSER.DAT file into the Registry Editor to check for errors or corruption.
Also please check for any error messages or warnings related to user profile loading or registry hive corruption. Event IDs such as 1500, 1502, or 1508 may indicate issues with the user profile or registry hive.
Hope it helps !
04-22-2024 03:50 PM
Hi @Malhar Vora Thanks for your recommendation. As nobody able to RDP the PSM server, we are in a position to check anything on this server.
04-22-2024 04:20 PM
Hi @Saravanan Sowndaiyan
There is one more way to connect to the PSM server and that using WinRM
Do you have WinRM enabled on PSM server, you can try remotely connecting to PSM server using PowerShell.
Hope it helps !
04-22-2024 04:57 PM
Hi @Malhar Vora Thanks for the updates. I will check with Windows team about this option.
Regards
SS
12-10-2025 12:33 AM
Hi, @Saravanan Sowndaiyan were you able to solve this issue?
I'm in the same situation, after moving to AWS the Vault and the PSM, I'm not able to connect via RDP to both Vault and PSM machines.
How do you solved this problem?
We are trying some possible solution right now, but in case no one works we will re-install the PSM directly on AWS from scratch.
Thanks.
12-10-2025 12:47 AM
Hi @Marco Albertario
Has the required Security Groups on AWS side has a rule to allow to connect to Vault and PSM via RDP?
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!

