- 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-09-2024 01:16 PM
PSMApps - GPMC installed without issues. When launching GPMC, I get the following error: Failed to execute process [mmc.exe "C:\PSMapps\GPMC.msc"]. Server and service was restarted. Other apps installed via PSM Apps work fine.
01-29-2025 05:20 AM
The other thing is to go into the users account and under additional properties, add the domain name to the Log onTo (optional) field.
01-29-2025 07:55 AM
The LogonFlag=1 essentially tells the connector that you need to log on with a regular user with a profile, rather than the transparent PSM Shadow User process. This is so that you can launch GPMC in the context of that user. Since this is all happening on the PSM machine itself, we need to 'allow log on locally' for those users, as they will be inside a managed PSM session, running GPMC on the PSM server to execute tasks. Basically, when GPMC tries to log in as the target user, it is a local logon.
01-29-2025 08:37 AM
I worked with support and the conclusion I got it using AutoIT scripts to deploy the GPMC connection component similar to what I did in the CorePAS deployment and Add-PSMApps is sort of best effort from Cyberark to help customers deploy it but they won't spend time to troubleshoot if it is not working with the default deployment method.
I hope this helps to the people who are looking to resolve this issue.
01-29-2025 04:31 PM
That's a good callout but I already have that value set correctly. I suspect my issue is to do with the Allow Logon Locally user rights assignment as mentioned by EliH further up the thread, but I still don't understand why that would be necessary for one MSC but not the others.
01-29-2025 05:58 PM
In a related discussion (https://community.cyberark.com/s/question/0D52J00007OFql3SAD/has-any-one-successfully-run-group-policy-management-via-psmaduc-) I found this snippet which really helps with understanding what LogonFlag actually does. Pity that information isn't actually in the docs... (https://docs.cyberark.com/privilege-cloud-shared-services/latest/en/content/pasimp/psm_cc_target_settings.htm#Clientspecific or https://docs.cyberark.com/pam-self-hosted/12.2/en/content/pasref/options%20-%20connection%20components.htm#ClientSpecific).
LogonFlag values:
0 - Interactive logon with no profile.
1 - Interactive logon with profile.
2 - Network credentials only.
4 - Inherit the calling process's environment instead of the user's environment.
05-16-2025 07:34 AM
Please ensure below is satisfied in order to user GPMC installed via add-psmapps module.
08-17-2025 10:12 PM
For GPMC Please use below Script and The target user must have the right to log on locally
#include "PSMGenericClientWrapper.au3"
Global Const $CLIENT_EXECUTABLE = 'mmc.exe "c:\\windows\\system32\\GPMC.msc"'
; Initialize PSM API
PSMGenericClient_Init()
; Fetch credentials
Local $TargetUsername, $TargetPassword, $TargetLogonDomain
PSMGenericClient_GetSessionProperty("Username", $TargetUsername)
PSMGenericClient_GetSessionProperty("Password", $TargetPassword)
PSMGenericClient_GetSessionProperty("LogonDomain", $TargetLogonDomain)
; Launch GPMC with domain credentials
Local $ConnectionClientPID = RunAs($TargetUsername, $TargetLogonDomain, $TargetPassword, 1, $CLIENT_EXECUTABLE, "", @SW_MAXIMIZE)
If $ConnectionClientPID = 0 Then
MsgBox(0, "Error", "Failed to launch GPMC")
Exit
EndIf
; Notify PSM of the launched process
PSMGenericClient_SendPID($ConnectionClientPID)
; Optional: Map drives if needed
PSMGenericClient_MapTSDrives()
; End of script
04-23-2026 02:16 AM
We are also facing the same issue in our setup. Has anyone managed to resolve it or implement a working solution? If yes, could you please share the steps or configuration details?
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!

