<?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>article Find All Users and Groups in Privileged Groups from Machine Scan Logs Skip to end of metadata in PAM Self-Hosted Articles</title>
    <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-articles/find-all-users-and-groups-in-privileged-groups-from-machine-scan/ta-p/1428522</link>
    <description>&lt;P&gt;You may have some clients who are using Accounts Discovery on Windows Machines to locate Privileged Accounts in their environment as part of their Active Directory Cleanup or Maintenance Process. As a result, you will notice that the information provided by an Accounts Discovery scan is very helpful in providing the machine name a local privileged account is discovered within, but as for Domain Accounts it only provides the name of the Domain as the address for the account and the names of all the local groups it was found in that Accounts Discovery considers privileged. Currently as of version 10.2, Accounts Discovery cannot tell you each machine name a privileged Domain Account was found on. Thus, customers feel that this information is not as helpful in determining where domain accounts have privileged access to in their environment as compared to the information provided for local privileged accounts that we discover.&lt;/P&gt;
&lt;P&gt;The "Find_Whose_In_Privileged_Groups.ps1" script in this article will help you as an engineer provide your client with more information about what users and groups are directly within the local groups that Accounts Discovery considers privileged. The script parses all the logs within the MachineScans folder to find which users and groups are located directly within the following local groups that are considered privileged by Accounts Discovery (DNA Documentation for Version 8.0 on page 58):&lt;/P&gt;
&lt;UL&gt;&lt;LI&gt;Administrators&lt;/LI&gt;&lt;LI&gt;Power Users&lt;/LI&gt;&lt;LI&gt;Backup Operators&lt;/LI&gt;&lt;LI&gt;Cryptographic Operators&lt;/LI&gt;&lt;LI&gt;Distributed COM Users&lt;/LI&gt;&lt;/UL&gt;
&lt;P&gt;The output of the script is a .CSV file containing all the privileged users and groups found directly in any of the groups above and can be filtered by the following information in Excel:&lt;/P&gt;
&lt;UL&gt;&lt;LI&gt;Username/Group (Username or Group Name found in the the Privileged Local Group)&lt;/LI&gt;&lt;LI&gt;Domain/Local (Tells you whether the account found exists locally on the machine or on the Domain)&lt;/LI&gt;&lt;LI&gt;Local Group (Tells you what Privileged Group it was found within)&lt;/LI&gt;&lt;LI&gt;Computer Name (Tells you what machine the User or Group was found within)&lt;/LI&gt;&lt;/UL&gt;
&lt;P&gt;&lt;STRONG&gt;Important to Note&lt;/STRONG&gt;: If a group is discovered nested in any of the Privileged Groups above, the script will only give you the name of the nested group. It is then the responsibility of the client to determine which AD users are within that group.&lt;BR /&gt;&lt;BR /&gt;Scripts are NOT supported by Idira support team.&amp;nbsp; This is example provided.&amp;nbsp; You can always review the machine logs manually without scripting.&lt;/P&gt;
&lt;H3&gt;Steps&lt;/H3&gt;
&lt;OL&gt;&lt;LI&gt;Copy the "Find_Whose_In_Privileged Groups.ps1" script to the machine that also contains the "MachineScans" folder. In most cases it will be the CPM server, but you might copy the MachineScans folder to a local machine to save CPU and memory resources on the CPM server in the case you have many machine scan logs in the "MachineScans" folder.
	&lt;OL&gt;&lt;LI&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="ka3Ht000000LZywIAG__eid=ka3Ht000000LZyw&amp;amp;feoid=00N2J000009R3kv&amp;amp;refid=0EM2J000003JuH0.png"&gt;&lt;img src="https://live.paloaltonetworks.com/t5/image/serverpage/image-id/97128iC53653F2487226A2/image-size/large?v=v2&amp;amp;px=999" role="button" title="ka3Ht000000LZywIAG__eid=ka3Ht000000LZyw&amp;amp;feoid=00N2J000009R3kv&amp;amp;refid=0EM2J000003JuH0.png" alt="ka3Ht000000LZywIAG__eid=ka3Ht000000LZyw&amp;amp;feoid=00N2J000009R3kv&amp;amp;refid=0EM2J000003JuH0.png" /&gt;&lt;/span&gt;&lt;/LI&gt;&lt;/OL&gt;
&lt;/LI&gt;&lt;LI&gt;You will want to right-click the script and select "edit" to edit the script in Powershell.
	&lt;OL&gt;&lt;LI&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="ka3Ht000000LZywIAG__eid=ka3Ht000000LZyw&amp;amp;feoid=00N2J000009R3kv&amp;amp;refid=0EM2J000003JuH5.png"&gt;&lt;img src="https://live.paloaltonetworks.com/t5/image/serverpage/image-id/97129i3129AAE20F1D6B7C/image-size/large?v=v2&amp;amp;px=999" role="button" title="ka3Ht000000LZywIAG__eid=ka3Ht000000LZyw&amp;amp;feoid=00N2J000009R3kv&amp;amp;refid=0EM2J000003JuH5.png" alt="ka3Ht000000LZywIAG__eid=ka3Ht000000LZyw&amp;amp;feoid=00N2J000009R3kv&amp;amp;refid=0EM2J000003JuH5.png" /&gt;&lt;/span&gt;&lt;/LI&gt;&lt;/OL&gt;
&lt;/LI&gt;&lt;LI&gt;Modify the "Path=" line in the script to be the path to the MachineScans folder and then save the file.
	&lt;OL&gt;&lt;LI&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="ka3Ht000000LZywIAG__eid=ka3Ht000000LZyw&amp;amp;feoid=00N2J000009R3kv&amp;amp;refid=0EM2J000003JuHA.png"&gt;&lt;img src="https://live.paloaltonetworks.com/t5/image/serverpage/image-id/97130iB4EE1343BFB63353/image-size/large?v=v2&amp;amp;px=999" role="button" title="ka3Ht000000LZywIAG__eid=ka3Ht000000LZyw&amp;amp;feoid=00N2J000009R3kv&amp;amp;refid=0EM2J000003JuHA.png" alt="ka3Ht000000LZywIAG__eid=ka3Ht000000LZyw&amp;amp;feoid=00N2J000009R3kv&amp;amp;refid=0EM2J000003JuHA.png" /&gt;&lt;/span&gt;
&lt;OL&gt;&lt;LI&gt;Default Path:&amp;nbsp;C:\Program Files (x86)\CyberArk\Password Manager\Scanner\Log\MachineScans&lt;/LI&gt;&lt;/OL&gt;
&lt;/LI&gt;&lt;LI&gt;CPM version 13.0 + will have to&amp;nbsp;Modify the "Path=" line in the script to be the path to the MachineScans folder and then save the file and decrease all indices in the script (minus 2) &lt;span class="lia-inline-image-display-wrapper" image-alt="ka3Ht000000LZywIAG__eid=ka3Ht000000LZyw&amp;amp;feoid=00N2J000009R3kv&amp;amp;refid=0EM2J000005NLyO.png"&gt;&lt;img src="https://live.paloaltonetworks.com/t5/image/serverpage/image-id/97934i5192E0909E10CE8E/image-size/large?v=v2&amp;amp;px=999" role="button" title="ka3Ht000000LZywIAG__eid=ka3Ht000000LZyw&amp;amp;feoid=00N2J000009R3kv&amp;amp;refid=0EM2J000005NLyO.png" alt="ka3Ht000000LZywIAG__eid=ka3Ht000000LZyw&amp;amp;feoid=00N2J000009R3kv&amp;amp;refid=0EM2J000005NLyO.png" /&gt;&lt;/span&gt;&lt;/LI&gt;&lt;/OL&gt;
&lt;/LI&gt;&lt;LI&gt;Afterwards you may run the script.
	&lt;OL&gt;&lt;LI&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="ka3Ht000000LZywIAG__eid=ka3Ht000000LZyw&amp;amp;feoid=00N2J000009R3kv&amp;amp;refid=0EM2J000003JuHK.png"&gt;&lt;img src="https://live.paloaltonetworks.com/t5/image/serverpage/image-id/97131i5A75B89A39C50DB0/image-size/large?v=v2&amp;amp;px=999" role="button" title="ka3Ht000000LZywIAG__eid=ka3Ht000000LZyw&amp;amp;feoid=00N2J000009R3kv&amp;amp;refid=0EM2J000003JuHK.png" alt="ka3Ht000000LZywIAG__eid=ka3Ht000000LZyw&amp;amp;feoid=00N2J000009R3kv&amp;amp;refid=0EM2J000003JuHK.png" /&gt;&lt;/span&gt;&lt;/LI&gt;&lt;/OL&gt;
&lt;/LI&gt;&lt;LI&gt;Open the .CSV file produced by the script on a machine that has Excel installed.
	&lt;OL&gt;&lt;LI&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="ka3Ht000000LZywIAG__eid=ka3Ht000000LZyw&amp;amp;feoid=00N2J000009R3kv&amp;amp;refid=0EM2J000003JuHP.png"&gt;&lt;img src="https://live.paloaltonetworks.com/t5/image/serverpage/image-id/97132i7F25A3957F226A01/image-size/large?v=v2&amp;amp;px=999" role="button" title="ka3Ht000000LZywIAG__eid=ka3Ht000000LZyw&amp;amp;feoid=00N2J000009R3kv&amp;amp;refid=0EM2J000003JuHP.png" alt="ka3Ht000000LZywIAG__eid=ka3Ht000000LZyw&amp;amp;feoid=00N2J000009R3kv&amp;amp;refid=0EM2J000003JuHP.png" /&gt;&lt;/span&gt;&lt;/LI&gt;&lt;/OL&gt;
&lt;/LI&gt;&lt;LI&gt;Expand all four columns of the spreadsheet and select the Filter option underneath the "Data" tab in Excel.
	&lt;OL&gt;&lt;LI&gt;​​​​​​​​​​​​​​&lt;span class="lia-inline-image-display-wrapper" image-alt="ka3Ht000000LZywIAG__eid=ka3Ht000000LZyw&amp;amp;feoid=00N2J000009R3kv&amp;amp;refid=0EM2J000003JuHU.png"&gt;&lt;img src="https://live.paloaltonetworks.com/t5/image/serverpage/image-id/97133iF978F9E3CF0E9B9D/image-size/large?v=v2&amp;amp;px=999" role="button" title="ka3Ht000000LZywIAG__eid=ka3Ht000000LZyw&amp;amp;feoid=00N2J000009R3kv&amp;amp;refid=0EM2J000003JuHU.png" alt="ka3Ht000000LZywIAG__eid=ka3Ht000000LZyw&amp;amp;feoid=00N2J000009R3kv&amp;amp;refid=0EM2J000003JuHU.png" /&gt;&lt;/span&gt;&lt;/LI&gt;&lt;/OL&gt;
&lt;/LI&gt;&lt;LI&gt;You may then filter the spreadsheet by the information in each of the columns.&lt;/LI&gt;&lt;/OL&gt;
&lt;P&gt;The original script with the functionality shown above this point can be found at the end of the page as:&amp;nbsp;&lt;STRONG&gt;Find_Whose_In_Privileged_Groups.ps1&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Feature UPDATE V2 (7/12/2019):&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;An additional feature has been added to the script to query active directory for the domain accounts found by Accounts Discovery and output whether they are "Enabled" or "Disabled" in a new "Account State" column in the CSV file produced by this script.&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="ka3Ht000000LZywIAG__eid=ka3Ht000000LZyw&amp;amp;feoid=00N2J000009R3kv&amp;amp;refid=0EM2J000003JuHZ.png"&gt;&lt;img src="https://live.paloaltonetworks.com/t5/image/serverpage/image-id/97134i2531EEFD4CCCA2B0/image-size/large?v=v2&amp;amp;px=999" role="button" title="ka3Ht000000LZywIAG__eid=ka3Ht000000LZyw&amp;amp;feoid=00N2J000009R3kv&amp;amp;refid=0EM2J000003JuHZ.png" alt="ka3Ht000000LZywIAG__eid=ka3Ht000000LZyw&amp;amp;feoid=00N2J000009R3kv&amp;amp;refid=0EM2J000003JuHZ.png" /&gt;&lt;/span&gt;There are different values produced for the "Account State":&lt;/P&gt;
&lt;UL&gt;&lt;LI&gt;Enabled - The account is a domain account and the status is Enabled in Active Directory&lt;/LI&gt;&lt;LI&gt;Disabled/AD Group - The account is either a domain account that is disabled or the account is an AD Group&lt;/LI&gt;&lt;LI&gt;N/A - The account is a local account and the script currently doesn't support searching whether a local account is disabled or enabled&lt;/LI&gt;&lt;/UL&gt;
&lt;P&gt;The "Step-by-step" guide above is still the same but the only item that is now required when running the new script is that the system you are running the script from must:&lt;/P&gt;
&lt;UL&gt;&lt;LI&gt;Be Domain-Joined&lt;/LI&gt;&lt;LI&gt;Have "Active Directory module for Windows Powershell" installed
	&lt;UL&gt;&lt;LI&gt;Instructions for Installing the module:&amp;nbsp;&lt;A href="https://4sysops.com/wiki/how-to-install-the-powershell-active-directory-module/" target="_blank"&gt;https://4sysops.com/wiki/how-to-install-the-powershell-active-directory-module/&lt;/A&gt;&lt;/LI&gt;&lt;/UL&gt;
&lt;/LI&gt;&lt;/UL&gt;
&lt;P&gt;When running the new script you will see errors produced in PowerShell for the AD Groups that cannot be queried properly because they don't exist, but the script will still continue and this is expected behavior. An example of the insignificant error produced if the user does not exist in AD can be seen below:&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="ka3Ht000000LZywIAG__eid=ka3Ht000000LZyw&amp;amp;feoid=00N2J000009R3kv&amp;amp;refid=0EM2J000003JuHe.png"&gt;&lt;img src="https://live.paloaltonetworks.com/t5/image/serverpage/image-id/97135i01E54949AC64119E/image-size/large?v=v2&amp;amp;px=999" role="button" title="ka3Ht000000LZywIAG__eid=ka3Ht000000LZyw&amp;amp;feoid=00N2J000009R3kv&amp;amp;refid=0EM2J000003JuHe.png" alt="ka3Ht000000LZywIAG__eid=ka3Ht000000LZyw&amp;amp;feoid=00N2J000009R3kv&amp;amp;refid=0EM2J000003JuHe.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;The new script can be found below as:&amp;nbsp;&lt;STRONG&gt;Find_Whose_In_Privileged_Groups_V2.ps1&lt;/STRONG&gt;&lt;/P&gt;</description>
    <pubDate>Thu, 05 Nov 2026 20:00:57 GMT</pubDate>
    <dc:creator>CyberArkAlumni</dc:creator>
    <dc:date>2026-11-05T20:00:57Z</dc:date>
    <item>
      <title>Find All Users and Groups in Privileged Groups from Machine Scan Logs Skip to end of metadata</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-articles/find-all-users-and-groups-in-privileged-groups-from-machine-scan/ta-p/1428522</link>
      <description>&lt;P&gt;You may have some clients who are using Accounts Discovery on Windows Machines to locate Privileged Accounts in their environment as part of their Active Directory Cleanup or Maintenance Process. As a result, you will notice that the information provided by an Accounts Discovery scan is very helpful in providing the machine name a local privileged account is discovered within, but as for Domain Accounts it only provides the name of the Domain as the address for the account and the names of all the local groups it was found in that Accounts Discovery considers privileged. Currently as of version 10.2, Accounts Discovery cannot tell you each machine name a privileged Domain Account was found on. Thus, customers feel that this information is not as helpful in determining where domain accounts have privileged access to in their environment as compared to the information provided for local privileged accounts that we discover.&lt;/P&gt;
&lt;P&gt;The "Find_Whose_In_Privileged_Groups.ps1" script in this article will help you as an engineer provide your client with more information about what users and groups are directly within the local groups that Accounts Discovery considers privileged. The script parses all the logs within the MachineScans folder to find which users and groups are located directly within the following local groups that are considered privileged by Accounts Discovery (DNA Documentation for Version 8.0 on page 58):&lt;/P&gt;
&lt;UL&gt;&lt;LI&gt;Administrators&lt;/LI&gt;&lt;LI&gt;Power Users&lt;/LI&gt;&lt;LI&gt;Backup Operators&lt;/LI&gt;&lt;LI&gt;Cryptographic Operators&lt;/LI&gt;&lt;LI&gt;Distributed COM Users&lt;/LI&gt;&lt;/UL&gt;
&lt;P&gt;The output of the script is a .CSV file containing all the privileged users and groups found directly in any of the groups above and can be filtered by the following information in Excel:&lt;/P&gt;
&lt;UL&gt;&lt;LI&gt;Username/Group (Username or Group Name found in the the Privileged Local Group)&lt;/LI&gt;&lt;LI&gt;Domain/Local (Tells you whether the account found exists locally on the machine or on the Domain)&lt;/LI&gt;&lt;LI&gt;Local Group (Tells you what Privileged Group it was found within)&lt;/LI&gt;&lt;LI&gt;Computer Name (Tells you what machine the User or Group was found within)&lt;/LI&gt;&lt;/UL&gt;
&lt;P&gt;&lt;STRONG&gt;Important to Note&lt;/STRONG&gt;: If a group is discovered nested in any of the Privileged Groups above, the script will only give you the name of the nested group. It is then the responsibility of the client to determine which AD users are within that group.&lt;BR /&gt;&lt;BR /&gt;Scripts are NOT supported by Idira support team.&amp;nbsp; This is example provided.&amp;nbsp; You can always review the machine logs manually without scripting.&lt;/P&gt;
&lt;H3&gt;Steps&lt;/H3&gt;
&lt;OL&gt;&lt;LI&gt;Copy the "Find_Whose_In_Privileged Groups.ps1" script to the machine that also contains the "MachineScans" folder. In most cases it will be the CPM server, but you might copy the MachineScans folder to a local machine to save CPU and memory resources on the CPM server in the case you have many machine scan logs in the "MachineScans" folder.
	&lt;OL&gt;&lt;LI&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="ka3Ht000000LZywIAG__eid=ka3Ht000000LZyw&amp;amp;feoid=00N2J000009R3kv&amp;amp;refid=0EM2J000003JuH0.png"&gt;&lt;img src="https://live.paloaltonetworks.com/t5/image/serverpage/image-id/97128iC53653F2487226A2/image-size/large?v=v2&amp;amp;px=999" role="button" title="ka3Ht000000LZywIAG__eid=ka3Ht000000LZyw&amp;amp;feoid=00N2J000009R3kv&amp;amp;refid=0EM2J000003JuH0.png" alt="ka3Ht000000LZywIAG__eid=ka3Ht000000LZyw&amp;amp;feoid=00N2J000009R3kv&amp;amp;refid=0EM2J000003JuH0.png" /&gt;&lt;/span&gt;&lt;/LI&gt;&lt;/OL&gt;
&lt;/LI&gt;&lt;LI&gt;You will want to right-click the script and select "edit" to edit the script in Powershell.
	&lt;OL&gt;&lt;LI&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="ka3Ht000000LZywIAG__eid=ka3Ht000000LZyw&amp;amp;feoid=00N2J000009R3kv&amp;amp;refid=0EM2J000003JuH5.png"&gt;&lt;img src="https://live.paloaltonetworks.com/t5/image/serverpage/image-id/97129i3129AAE20F1D6B7C/image-size/large?v=v2&amp;amp;px=999" role="button" title="ka3Ht000000LZywIAG__eid=ka3Ht000000LZyw&amp;amp;feoid=00N2J000009R3kv&amp;amp;refid=0EM2J000003JuH5.png" alt="ka3Ht000000LZywIAG__eid=ka3Ht000000LZyw&amp;amp;feoid=00N2J000009R3kv&amp;amp;refid=0EM2J000003JuH5.png" /&gt;&lt;/span&gt;&lt;/LI&gt;&lt;/OL&gt;
&lt;/LI&gt;&lt;LI&gt;Modify the "Path=" line in the script to be the path to the MachineScans folder and then save the file.
	&lt;OL&gt;&lt;LI&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="ka3Ht000000LZywIAG__eid=ka3Ht000000LZyw&amp;amp;feoid=00N2J000009R3kv&amp;amp;refid=0EM2J000003JuHA.png"&gt;&lt;img src="https://live.paloaltonetworks.com/t5/image/serverpage/image-id/97130iB4EE1343BFB63353/image-size/large?v=v2&amp;amp;px=999" role="button" title="ka3Ht000000LZywIAG__eid=ka3Ht000000LZyw&amp;amp;feoid=00N2J000009R3kv&amp;amp;refid=0EM2J000003JuHA.png" alt="ka3Ht000000LZywIAG__eid=ka3Ht000000LZyw&amp;amp;feoid=00N2J000009R3kv&amp;amp;refid=0EM2J000003JuHA.png" /&gt;&lt;/span&gt;
&lt;OL&gt;&lt;LI&gt;Default Path:&amp;nbsp;C:\Program Files (x86)\CyberArk\Password Manager\Scanner\Log\MachineScans&lt;/LI&gt;&lt;/OL&gt;
&lt;/LI&gt;&lt;LI&gt;CPM version 13.0 + will have to&amp;nbsp;Modify the "Path=" line in the script to be the path to the MachineScans folder and then save the file and decrease all indices in the script (minus 2) &lt;span class="lia-inline-image-display-wrapper" image-alt="ka3Ht000000LZywIAG__eid=ka3Ht000000LZyw&amp;amp;feoid=00N2J000009R3kv&amp;amp;refid=0EM2J000005NLyO.png"&gt;&lt;img src="https://live.paloaltonetworks.com/t5/image/serverpage/image-id/97934i5192E0909E10CE8E/image-size/large?v=v2&amp;amp;px=999" role="button" title="ka3Ht000000LZywIAG__eid=ka3Ht000000LZyw&amp;amp;feoid=00N2J000009R3kv&amp;amp;refid=0EM2J000005NLyO.png" alt="ka3Ht000000LZywIAG__eid=ka3Ht000000LZyw&amp;amp;feoid=00N2J000009R3kv&amp;amp;refid=0EM2J000005NLyO.png" /&gt;&lt;/span&gt;&lt;/LI&gt;&lt;/OL&gt;
&lt;/LI&gt;&lt;LI&gt;Afterwards you may run the script.
	&lt;OL&gt;&lt;LI&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="ka3Ht000000LZywIAG__eid=ka3Ht000000LZyw&amp;amp;feoid=00N2J000009R3kv&amp;amp;refid=0EM2J000003JuHK.png"&gt;&lt;img src="https://live.paloaltonetworks.com/t5/image/serverpage/image-id/97131i5A75B89A39C50DB0/image-size/large?v=v2&amp;amp;px=999" role="button" title="ka3Ht000000LZywIAG__eid=ka3Ht000000LZyw&amp;amp;feoid=00N2J000009R3kv&amp;amp;refid=0EM2J000003JuHK.png" alt="ka3Ht000000LZywIAG__eid=ka3Ht000000LZyw&amp;amp;feoid=00N2J000009R3kv&amp;amp;refid=0EM2J000003JuHK.png" /&gt;&lt;/span&gt;&lt;/LI&gt;&lt;/OL&gt;
&lt;/LI&gt;&lt;LI&gt;Open the .CSV file produced by the script on a machine that has Excel installed.
	&lt;OL&gt;&lt;LI&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="ka3Ht000000LZywIAG__eid=ka3Ht000000LZyw&amp;amp;feoid=00N2J000009R3kv&amp;amp;refid=0EM2J000003JuHP.png"&gt;&lt;img src="https://live.paloaltonetworks.com/t5/image/serverpage/image-id/97132i7F25A3957F226A01/image-size/large?v=v2&amp;amp;px=999" role="button" title="ka3Ht000000LZywIAG__eid=ka3Ht000000LZyw&amp;amp;feoid=00N2J000009R3kv&amp;amp;refid=0EM2J000003JuHP.png" alt="ka3Ht000000LZywIAG__eid=ka3Ht000000LZyw&amp;amp;feoid=00N2J000009R3kv&amp;amp;refid=0EM2J000003JuHP.png" /&gt;&lt;/span&gt;&lt;/LI&gt;&lt;/OL&gt;
&lt;/LI&gt;&lt;LI&gt;Expand all four columns of the spreadsheet and select the Filter option underneath the "Data" tab in Excel.
	&lt;OL&gt;&lt;LI&gt;​​​​​​​​​​​​​​&lt;span class="lia-inline-image-display-wrapper" image-alt="ka3Ht000000LZywIAG__eid=ka3Ht000000LZyw&amp;amp;feoid=00N2J000009R3kv&amp;amp;refid=0EM2J000003JuHU.png"&gt;&lt;img src="https://live.paloaltonetworks.com/t5/image/serverpage/image-id/97133iF978F9E3CF0E9B9D/image-size/large?v=v2&amp;amp;px=999" role="button" title="ka3Ht000000LZywIAG__eid=ka3Ht000000LZyw&amp;amp;feoid=00N2J000009R3kv&amp;amp;refid=0EM2J000003JuHU.png" alt="ka3Ht000000LZywIAG__eid=ka3Ht000000LZyw&amp;amp;feoid=00N2J000009R3kv&amp;amp;refid=0EM2J000003JuHU.png" /&gt;&lt;/span&gt;&lt;/LI&gt;&lt;/OL&gt;
&lt;/LI&gt;&lt;LI&gt;You may then filter the spreadsheet by the information in each of the columns.&lt;/LI&gt;&lt;/OL&gt;
&lt;P&gt;The original script with the functionality shown above this point can be found at the end of the page as:&amp;nbsp;&lt;STRONG&gt;Find_Whose_In_Privileged_Groups.ps1&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Feature UPDATE V2 (7/12/2019):&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;An additional feature has been added to the script to query active directory for the domain accounts found by Accounts Discovery and output whether they are "Enabled" or "Disabled" in a new "Account State" column in the CSV file produced by this script.&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="ka3Ht000000LZywIAG__eid=ka3Ht000000LZyw&amp;amp;feoid=00N2J000009R3kv&amp;amp;refid=0EM2J000003JuHZ.png"&gt;&lt;img src="https://live.paloaltonetworks.com/t5/image/serverpage/image-id/97134i2531EEFD4CCCA2B0/image-size/large?v=v2&amp;amp;px=999" role="button" title="ka3Ht000000LZywIAG__eid=ka3Ht000000LZyw&amp;amp;feoid=00N2J000009R3kv&amp;amp;refid=0EM2J000003JuHZ.png" alt="ka3Ht000000LZywIAG__eid=ka3Ht000000LZyw&amp;amp;feoid=00N2J000009R3kv&amp;amp;refid=0EM2J000003JuHZ.png" /&gt;&lt;/span&gt;There are different values produced for the "Account State":&lt;/P&gt;
&lt;UL&gt;&lt;LI&gt;Enabled - The account is a domain account and the status is Enabled in Active Directory&lt;/LI&gt;&lt;LI&gt;Disabled/AD Group - The account is either a domain account that is disabled or the account is an AD Group&lt;/LI&gt;&lt;LI&gt;N/A - The account is a local account and the script currently doesn't support searching whether a local account is disabled or enabled&lt;/LI&gt;&lt;/UL&gt;
&lt;P&gt;The "Step-by-step" guide above is still the same but the only item that is now required when running the new script is that the system you are running the script from must:&lt;/P&gt;
&lt;UL&gt;&lt;LI&gt;Be Domain-Joined&lt;/LI&gt;&lt;LI&gt;Have "Active Directory module for Windows Powershell" installed
	&lt;UL&gt;&lt;LI&gt;Instructions for Installing the module:&amp;nbsp;&lt;A href="https://4sysops.com/wiki/how-to-install-the-powershell-active-directory-module/" target="_blank"&gt;https://4sysops.com/wiki/how-to-install-the-powershell-active-directory-module/&lt;/A&gt;&lt;/LI&gt;&lt;/UL&gt;
&lt;/LI&gt;&lt;/UL&gt;
&lt;P&gt;When running the new script you will see errors produced in PowerShell for the AD Groups that cannot be queried properly because they don't exist, but the script will still continue and this is expected behavior. An example of the insignificant error produced if the user does not exist in AD can be seen below:&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="ka3Ht000000LZywIAG__eid=ka3Ht000000LZyw&amp;amp;feoid=00N2J000009R3kv&amp;amp;refid=0EM2J000003JuHe.png"&gt;&lt;img src="https://live.paloaltonetworks.com/t5/image/serverpage/image-id/97135i01E54949AC64119E/image-size/large?v=v2&amp;amp;px=999" role="button" title="ka3Ht000000LZywIAG__eid=ka3Ht000000LZyw&amp;amp;feoid=00N2J000009R3kv&amp;amp;refid=0EM2J000003JuHe.png" alt="ka3Ht000000LZywIAG__eid=ka3Ht000000LZyw&amp;amp;feoid=00N2J000009R3kv&amp;amp;refid=0EM2J000003JuHe.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;The new script can be found below as:&amp;nbsp;&lt;STRONG&gt;Find_Whose_In_Privileged_Groups_V2.ps1&lt;/STRONG&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 05 Nov 2026 20:00:57 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-articles/find-all-users-and-groups-in-privileged-groups-from-machine-scan/ta-p/1428522</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2026-11-05T20:00:57Z</dc:date>
    </item>
  </channel>
</rss>

