<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: MMC Snap-ins GPMC Issues in PAM Self-Hosted Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/mmc-snap-ins-gpmc-issues/m-p/1352423#M43854</link>
    <description>&lt;P&gt;The target user has permissions to log on locally to the PSM server?&lt;/P&gt;</description>
    <pubDate>Thu, 19 Jan 2023 14:50:24 GMT</pubDate>
    <dc:creator>CyberArkAlumni</dc:creator>
    <dc:date>2023-01-19T14:50:24Z</dc:date>
    <item>
      <title>MMC Snap-ins GPMC Issues</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/mmc-snap-ins-gpmc-issues/m-p/1352422#M43853</link>
      <description>&lt;P&gt;Hey all,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Over the last several weeks, I've been working on getting various MMC snap-ins deployed within our PAM environment. DNS, DHCP, CA, and AD were successfully deployed, but GPMC won't work. &lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Greatly appreciate any assistance or guidance.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Here are snippets of the config and an error message&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;AppLocker - snippet to launch MMC&lt;/P&gt;&lt;CODE&gt;&amp;lt;!-- MMC process --&amp;gt;
    &amp;lt;Application Name="MMC" Type="Exe" Path="C:\Windows\System32\mmc.exe" Method="Hash" /&amp;gt;
	&amp;lt;Application Name="AutoIt3" Type="Exe" Path="C:\Program Files (x86)\AutoIt3\AutoIt3.exe" Method="Publisher" /&amp;gt;&lt;/CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Dispatcher - snippet to launch GPMC&lt;/P&gt;&lt;CODE&gt;Global Const $DISPATCHER_NAME									= "Microsoft GPMC" ; CHANGE_ME
Global Const $CLIENT_EXECUTABLE									= 'gpmc "C:\Program Files (x86)\Cyberark\PSM\Components\MSC\GPMC.msc"' ; CHANGE_ME
Global Const $ERROR_MESSAGE_TITLE  								= "PSM " &amp;amp; $DISPATCHER_NAME &amp;amp; " Dispatcher error message"
Global Const $LOG_MESSAGE_PREFIX 								= $DISPATCHER_NAME &amp;amp; " Dispatcher - "
&amp;nbsp;
Global $TargetUsername
Global $TargetPassword
Global $TargetAddress
Global $TargetLogonDomain
Global $ConnectionClientPID = RunAs($TargetUsername,$TargetLogonDomain,$TargetPassword,2,$CLIENT_EXECUTABLE)
&amp;nbsp;
;=======================================
; Code
;=======================================
Exit Main()
&amp;nbsp;
;=======================================
; Main
;=======================================
Func Main()
&amp;nbsp;
	; Init PSM Dispatcher utils wrapper
	ToolTip ("Initializing...")
	if (PSMGenericClient_Init() &amp;lt;&amp;gt; $PSM_ERROR_SUCCESS) Then
		Error(PSMGenericClient_PSMGetLastErrorString())
	EndIf
&amp;nbsp;
	LogWrite("successfully initialized Dispatcher Utils Wrapper")
&amp;nbsp;
	; Get the dispatcher parameters
	FetchSessionProperties()
&amp;nbsp;
	LogWrite("mapping local drives")
	if (PSMGenericClient_MapTSDrives() &amp;lt;&amp;gt; $PSM_ERROR_SUCCESS) Then
		Error(PSMGenericClient_PSMGetLastErrorString())
	EndIf
&amp;nbsp;
	LogWrite("starting client application")
	ToolTip ("Starting " &amp;amp; $DISPATCHER_NAME &amp;amp; "...")
&amp;nbsp;
	; ------------------
	; Handle login here! ; CHANGE_ME
	; ------------------
&amp;nbsp;
	$ConnectionClientPID = RunAs($TargetUsername,$TargetLogonDomain,$TargetPassword,2,$CLIENT_EXECUTABLE)
	if ($ConnectionClientPID == 0) Then
		Error(StringFormat("Failed to execute process [%s]", $CLIENT_EXECUTABLE, @error))
	EndIf&lt;/CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Issue: when launched GPMC, a notification shows &lt;/P&gt;&lt;CODE&gt;To manage group policy you must log on to the computer with a domain user account&lt;/CODE&gt;&lt;P&gt;Based on articles out there, things I tried. Multiple combinations of the bellow. &lt;/P&gt;&lt;CODE&gt;From:    Global $ConnectionClientPID = RunAs($TargetUsername,$TargetLogonDomain,$TargetPassword,2,$CLIENT_EXECUTABLE)
To:    Global $ConnectionClientPID = 0
&amp;nbsp;
From:   $ConnectionClientPID = RunAs($TargetUsername,$TargetLogonDomain,$TargetPassword,2,$CLIENT_EXECUTABLE)
	if ($ConnectionClientPID == 0) Then
		Error(StringFormat("Failed to execute process [%s]", $CLIENT_EXECUTABLE, @error))
	EndIf
&amp;nbsp;
To:   $ConnectionClientPID = RunAs($TargetUsername,$TargetLogonDomain,$TargetPassword,1,$CLIENT_EXECUTABLE)
	if ($ConnectionClientPID == 0) Then
		Error(StringFormat("Failed to execute process [%s]", $CLIENT_EXECUTABLE, @error))
	EndIf
&amp;nbsp;
And:   $ConnectionClientPID = RunAs($TargetUsername,$TargetLogonDomain,$TargetPassword,0,$CLIENT_EXECUTABLE)
	if ($ConnectionClientPID == 0) Then
		Error(StringFormat("Failed to execute process [%s]", $CLIENT_EXECUTABLE, @error))
	EndIf
&amp;nbsp;
And:   $ConnectionClientPID = 0&lt;/CODE&gt;&lt;P&gt;Outcome: Once I change from 2 to any number (near if statement), an error message shows&lt;/P&gt;&lt;CODE&gt;Failed to execute process [mmc "C:\Program Files (x86)\Cyberark\PSM\Components\MSC\GPMC.msc"]&lt;/CODE&gt;&lt;P&gt;FYI. AppLocker does not prompt for any error messages, shows as changes are successful. &lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you in advance for the help &lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 19 Jan 2023 05:34:16 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/mmc-snap-ins-gpmc-issues/m-p/1352422#M43853</guid>
      <dc:creator>edas_dabulevicius</dc:creator>
      <dc:date>2023-01-19T05:34:16Z</dc:date>
    </item>
    <item>
      <title>Re: MMC Snap-ins GPMC Issues</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/mmc-snap-ins-gpmc-issues/m-p/1352423#M43854</link>
      <description>&lt;P&gt;The target user has permissions to log on locally to the PSM server?&lt;/P&gt;</description>
      <pubDate>Thu, 19 Jan 2023 14:50:24 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/mmc-snap-ins-gpmc-issues/m-p/1352423#M43854</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2023-01-19T14:50:24Z</dc:date>
    </item>
    <item>
      <title>Re: MMC Snap-ins GPMC Issues</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/mmc-snap-ins-gpmc-issues/m-p/1352424#M43855</link>
      <description>&lt;P&gt;Hey Bernhard,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Good question. I would've expected the hardening GPO to handle permissions.&lt;/P&gt;&lt;P&gt;Looking at the "Allow log on locally" policy, PSMShadowUsers and Administrators are part of it.&lt;/P&gt;&lt;P&gt;PSMShadowUsers contain what seems to be random PSM- accounts (look like temp accounts)&lt;/P&gt;&lt;P&gt;Administrators contain an Administrator account and a group that controls who can access PSM servers as admin.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;As PSM servers were deployed by CyberArk engineer, I would expect for that to be correct.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;From your knowledge, what should be part of  "Allow log on locally"?&lt;/P&gt;</description>
      <pubDate>Fri, 20 Jan 2023 01:16:27 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/mmc-snap-ins-gpmc-issues/m-p/1352424#M43855</guid>
      <dc:creator>edas_dabulevicius</dc:creator>
      <dc:date>2023-01-20T01:16:27Z</dc:date>
    </item>
    <item>
      <title>Re: MMC Snap-ins GPMC Issues</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/mmc-snap-ins-gpmc-issues/m-p/1352425#M43856</link>
      <description>&lt;P&gt;The hardening GPO does not cover changes that are necessary for specific connection components that you develop yourself (or implement yourself). Most connection components from the CyberArk Marketplace will work without any changes.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Afaik, if you want to run the GPMC MMC snap-in, you need to give the target accounts "Log on locally" rights on the PSM - no way around it. Since this could weaken the security posture of the PSM, you need to strongly consider if you want to &lt;I&gt;actually &lt;/I&gt;do this.&lt;/P&gt;</description>
      <pubDate>Fri, 20 Jan 2023 11:26:14 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/mmc-snap-ins-gpmc-issues/m-p/1352425#M43856</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2023-01-20T11:26:14Z</dc:date>
    </item>
    <item>
      <title>Re: MMC Snap-ins GPMC Issues</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/mmc-snap-ins-gpmc-issues/m-p/1352426#M43857</link>
      <description>&lt;P&gt;Hi ya,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;That makes perfect sense, that was my understanding too. Correct permission are required.&lt;/P&gt;&lt;P&gt;I hope I'm not missing something and that your referral to "Log on locally" is equal to my referral &amp;nbsp;"Allow log on locally" located on the PSM server, Local Security Policy. &lt;/P&gt;&lt;P&gt;If so. The Target account used to launch GPMC has been added to Domain Admins (for test purposes).  &lt;/P&gt;&lt;P&gt;Domain Admins Group belongs to a group on the PSM server called Administrators.&lt;/P&gt;&lt;P&gt;Administrators belongs to the Local Security policy Allow Log on Locally.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;NOTE: Ensured to point platform containing GPMC tied to the account to PSM server where GPMC config sits, instead of the load balancer.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks for sharing knowledge so far Bernhard.&lt;/P&gt;</description>
      <pubDate>Sun, 22 Jan 2023 23:07:43 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/mmc-snap-ins-gpmc-issues/m-p/1352426#M43857</guid>
      <dc:creator>edas_dabulevicius</dc:creator>
      <dc:date>2023-01-22T23:07:43Z</dc:date>
    </item>
    <item>
      <title>Re: MMC Snap-ins GPMC Issues</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/mmc-snap-ins-gpmc-issues/m-p/1352427#M43858</link>
      <description>&lt;P&gt;The solution to the issue, within our environment&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;"GPMCdispatcher" config file has been updated&amp;nbsp;as per the following:&lt;/P&gt;&lt;P&gt;Line 32,&lt;/P&gt;&lt;P&gt;FROM: Global $ConnectionClientPID = RunAs($TargetUsername,$TargetLogonDomain,$TargetPassword,2,$CLIENT_EXECUTABLE)&amp;nbsp;&lt;/P&gt;&lt;P&gt;TO: Global $ConnectionClientPID = RunAs($TargetUsername,$TargetLogonDomain,$TargetPassword,1,$CLIENT_EXECUTABLE)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Line 69&amp;nbsp;&lt;/P&gt;&lt;P&gt;FROM: $ConnectionClientPID = RunAs($TargetUsername,$TargetLogonDomain,$TargetPassword,2,$CLIENT_EXECUTABLE)&amp;nbsp;&lt;/P&gt;&lt;P&gt;TO: $ConnectionClientPID = RunAs($TargetUsername,$TargetLogonDomain,$TargetPassword,1,$CLIENT_EXECUTABLE)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Followed by:&lt;/P&gt;&lt;P&gt;Disable the UAC on the Connector Server(s) by editing the Domain PSM Hardening GPO&lt;/P&gt;&lt;P&gt;Computer Configuration → Policies → Windows Settings → Security Settings → Local Policies → Security Options → User Account Controls → User Account Control: Run all administrators in Admin Approval Mode&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sun, 29 Jan 2023 22:55:39 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/mmc-snap-ins-gpmc-issues/m-p/1352427#M43858</guid>
      <dc:creator>edas_dabulevicius</dc:creator>
      <dc:date>2023-01-29T22:55:39Z</dc:date>
    </item>
  </channel>
</rss>

