Skip to main content
All CollectionsInspectors
Active Directory | Inspector Updates and Reconfiguration Steps
Active Directory | Inspector Updates and Reconfiguration Steps
Updated over a week ago

Overview

Liongard is releasing a new version of the Active Directory Inspector designed to improve the integration's performance and security. As part of this effort, we are removing the inspector’s remote inspection capability. This removes the inspector’s dependence on WinRM and ADWS and makes it safer and easier to configure.

What do I need to do?

You do not need further action if your Active Directory Inspectors are configured to use a local agent (a Liongard agent installed on a domain controller for the targeted domain). Your inspectors will be automatically upgraded to the newest version of the inspector during our July 2024 release.

If your Active Directory inspectors are configured to use remote inspection (running an inspection from a server other than the domain controller), you must reconfigure them to ensure that they return the full breadth of data that the inspector can provide.

How do I know if my Active Directory inspectors are using remote inspection?

To see which of your Active Directory inspectors are using remote inspection, navigate to Admin > Inspectors > Active Directory and look at the column in the inspector table titled “Remote Inspection”. If an inspector has a “Remote Inspection” value of Yes, you will need to reconfigure that inspector to run as a local inspection.

If an inspector has a “Remote Inspection” value of No, no further action is required.

How do I reconfigure my Active Directory inspectors to run as a local inspection?

If you are using our remote inspection capability, you’ll need to reconfigure your Active Directory inspectors to run from a local agent. To do this, please follow these steps:

  1. Determine which server should run the Liongard agent. For the Active Directory inspector to work as intended, we recommend using a domain controller with DNS and DHCP roles installed.

  2. If the domain controller already has an agent installed, proceed to the next step. If the server does not have an agent installed, you will need to install a new agent using the instructions found here: Installing a Windows Agent

  3. Once you have an agent installed on the domain controller, navigate to Admin > Inspectors > Active Directory, select a remote inspector from your list of Active Directory inspectors, click … > Edit, update the agent field to use the agent installed on the domain controller, and click Save.

Did this answer your question?