Admon not collecting all machines

This plugin monitors local admin group for changes and alerts admins when changes have been made.
Post Reply
Whirlwind
Posts: 2
Joined: Fri Jun 10, 2022 2:50 pm
1

Admon not collecting all machines

Post by Whirlwind »

Admon is not collecting all computers, it's only showing computers where the admin account used in 'Deployment & Defaults' 'Login to use for Administrator Access' has logged into the endpoint and a profile folder has been created. Please see attached screenshot of the command output relating to the script. Any ideas?
Attachments
Screenshot 2022-06-10 155402.jpg
Screenshot 2022-06-10 155402.jpg (28.66 KiB) Viewed 3031 times

User avatar
Cubert
Posts: 2430
Joined: Tue Dec 29, 2015 7:57 pm
8
Contact:

Re: Admon not collecting all machines

Post by Cubert »

That is coming from the following line in the Admon script. Find this script in your "scripts/Maintenance/" folder in automate. Edit this line and change the Run as admin to Run as Local Agent and see if that resolves your issues.


Screenshot 2022-06-14 111233.png
Screenshot 2022-06-14 111233.png (53.09 KiB) Viewed 2982 times

Whirlwind
Posts: 2
Joined: Fri Jun 10, 2022 2:50 pm
1

Re: Admon not collecting all machines

Post by Whirlwind »

Hi,

Thank you, that appears to be populating more entires.

User avatar
Cubert
Posts: 2430
Joined: Tue Dec 29, 2015 7:57 pm
8
Contact:

Re: Admon not collecting all machines

Post by Cubert »

Awesome.

ray@dominiontech.com
Posts: 3
Joined: Fri Jul 15, 2022 5:24 pm
1

Re: Admon not collecting all machines

Post by ray@dominiontech.com »

Just for reference, I had to make this adjustment as well, even after having confirmed my credentials were correct in Automate, it didn't want to collect the data.
I am running on-prem 2022.6.
Great Tool. Thanks for the efforts helping everyone.

User avatar
Cubert
Posts: 2430
Joined: Tue Dec 29, 2015 7:57 pm
8
Contact:

Re: Admon not collecting all machines

Post by Cubert »

The run as admin was a throw back to the LabTech 8/9 days when the agent was set to run as a user and not SYSTEM. So more people had issues running the tool outside of domain permissions and Windows 2003 Server did not have this user profile issue when running script.

The years have caused change but the baseline script is so simple it never really needed an update, and so this minor issue keeps rearing its head.

I will one day remember to update the script and push a new build out so this goes away.

Post Reply

Return to “ADMON Administrators Group Monitor plugin”