Active Directory monitor - Scripts and Commands used

Active Directory monitor - Scripts and Commands used

Refer to this document to learn about the scripts and commands used to fetch data in the Active Directory monitor.

VB Scripts:

  1. The .vbs scripts are used to collect Performance Metrics in WMI mode.
  2. Below are the scripts used:
    1. wmicheckauthentication.vbs - Performs authentication checks for the monitor
    2. wmiQueryExecuter.vbs cookwmiget.vbs - Fetches common counters
    3. ADReplicationData.vbs - Retrieves Replication Statistics
  3. For information on WMI classes and counters, refer to Self Help Tools or the ActiveDirectory.bat file present in <Applications Manager Home>\bin\troubleshooting directory.

PowerShell Scripts:

  1. ADTimeSyncTest.ps1
    1. Fetches Time Synchronization metrics.
    2. Determines whether the monitored AD server is a Primary DC or not.
    3. Command used in the script: 
           w32tm /monitor
    4. Refer to this KB article for more details.
  2. PortConnectivity.ps1 & ActiveDirectoryPorts.ps1
    1. Fetches Active Directory Port Connectivity details.
    2. The ports to be monitored are listed in ActiveDirectoryPorts.ps1 script.
    3. Commands used in PortConnectivity.ps1 script:
           Test-NetConnection
                (If this fails, the following command is used)
           Net.Sockets.TcpClient.Connect($hostname, $port)
    4. Refer to this KB article for more information.
  3. ADDiagnosticTests.ps1
    1. Runs Diagnostic Tests and retrieves results from the AD server.
    2. Command used in the script:
           dcdiag
    3. Refer this KB article for more details.


                  New to ADSelfService Plus?

                    • Related Articles

                    • Active Directory Monitor - FAQs

                      1. What are the Scripts and Processes used in the Active Directory Monitor? Below is a list of VB Scripts and PowerShell scripts used for data collection in the AD monitor: VB Scripts located in <AppManager-Home>\working\conf\application\scripts ...
                    • Troubleshooting errors during data collection in Microsoft 365 monitor (For versions upto v16300)

                      Prerequisites: Ensure that you have met all the prerequisites for the Microsoft 365 monitor. From Applications Manager version 16300 onwards, Microsoft 365 monitor will use Microsoft Graph API as the primary mode of data collection. We have migrated ...
                    • Real User Monitor (RUM) - Troubleshooting

                      If the monitor has not polled data for a long time, follow the below steps for troubleshooting. Step 1: Check the RUM Agent configuration Real User Monitor requires the RUM Agent to be installed and mapped to the Applications Manager. Refer this help ...
                    • Troubleshooting URL Monitor

                      When configuring a URL monitor in Applications Manager, you might encounter several errors related to accessibility, configuration, or server-side issues. Below are common errors along with step-by-step troubleshooting instructions to help you ...
                    • Data not available in Active Directory monitor

                      Steps to follow if there is no data in Active Directory monitor If you are using AppManager version 15470 and above, you can navigate to Admin > Self Help Tools and choose the monitor type to troubleshoot the problem. Click here for more details. If ...