Jump to content

Domain Computers without Automate Agent 3.0

   (4 reviews)

1 Screenshot

About This File

This RAWSQL monitor uses data from the Active Directory Plugin to check for active AD Computer Accounts with a Windows OS that have recent logon times, and that do not have an Automate Agent installed. This is helpful to identify computers that were joined to the domain without the proper procedure, or computers that your agent deployment has not succeeded in reaching. The alert will be targeted against a probe computer for each client, you will need to read the alert body (or subject) to find out the name of the computer without an agent. Because the alerting is "Probe" centric, be aware of the following:

If you enable group targeting, and your targeting excludes the probe computer for a client, no machines will be reported for that client.
If you have no probe at any location for a client, no machines will be reported for that client.

The alerts now are applied against the DC used for the AD information gathering, so it no longer generates alerts using probe agents.
If you Exclude or Ignore the "computer", you are really excluding the Probe AD Controller Computer, and if you do this no machines will be reported for that client.
There is no simple way to Whitelist machines that do not have an agent installed on purpose. You will just have to live with them being reported. To prevent a computer from triggering an alert if it should not have an agent, just update the computer description in Active Directory to have the word "Exclude". Examples: "Exclude From MSP Management" , "Excluded from Automate Agent deployment", etc.

To Import: In Control Center, open Tools -> Import -> SQL File. (System->General->Import->SQL File in Automate 12) Select the file, and you should be asked to import 2 statements. (Cancel if it tells you a different number). The Monitor will be named "Domain Computer Without Automate Agent", and it should run every 6 hours. If you already have this monitor, you can safely import and it will apply the updates to your existing monitor.

Keywords: active directory domain joined computer object account missing labtech automate agent machine monitor


What's New in Version 2.1   See changelog

Released

Optimized Query. This one was so much faster I called it 2.0!
Thanks to @qcomer, @(B)admin Life, @dpltadmin

2.1 - New alert messages for ticket creation.

  • Thanks 4

User Feedback

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest

Jacobsa

   1 of 1 member found this review helpful 1 / 1 member

Awesome work as always. Much quicker and now it is filtering only on Windows machines the results are perfect.

Link to review
dpltadmin

   1 of 1 member found this review helpful 1 / 1 member

v2.1 is vastly improved over the original version. Much quicker and more accurate. Thank you @DarrenWhite99

Link to review
Dayrak

  

@DarrenWhite99

Hi Darren,

I had some inactive agents in my list which causing some issue specially at the time of report for ( monitoring patches and etc).

my strategy was to awaken them to update the agent or delete them.

I did run "Push ConnectWise Automate to Domain" against DC and after that run Cleanup inactive agents >90 days.

As a consequence some devices become retired and I realized that part of those devices are in production environment and we need to have screen connect access and also need have them monitored.

Any suggestion is highly appreciated.

Kind regards,

Dayrak

Response from the author:

If the question is: "What do I do when I retired a computer that I now need access to?" - The short answer is: Reinstall the agent so that you can manage the computer. This monitor is designed to help you identify machines that need to have an agent installed, but how you install the agent is completely out of this monitor's scope.

Link to review
×
×
  • Create New...