Active Directory Diagnostic Tests - Troubleshoot Errors in Specific test
In Active Directory Monitor, Diagnostic tests have been introduced in build 14040. To troubleshoot any errors in a specific test in the Diagnostic tests tab, follow the below steps:
1) Open Powershell in administrator mode in the machine where Applications Manager is installed.
2) Go to <AppManager-Home>\working\conf\application\scripts\powershell
3) Run the command:
.\ADDiagnosticTests.ps1 'hostname' 'username' 'password' 'Test' >C:\diagtest.txt
Note: Replace the hostname, username and password with the credentials of the reported AD machine and replace Test with the corresponding test name (refer below table).4) Get the diagtest.txt file which will be generated in C:\ drive.
5) Check this file for any errors in that specific test to troubleshoot.
Test Name (as in UI) | Test Name (to be used in command) |
Connectivity Check | Connectivity |
Advertising Status Check | Advertising |
SYSVOL Status Check | SysVolCheck |
Knowledge Consistency Check | KccEvent |
RID Master Accessibility Check | RidManager |
Machine Account Information Check | MachineAccount |
Global Role-holders Locator Check | LocatorCheck |
File Replication System Check | FrsEvent |
Distributed File System Check | DFSREvent |
Logon Priviledges(NetLogons) Check | NetLogons |
Object Replication Check | ObjectsReplicated |
Verify References for FRS and Replication Infrastructure | VerifyReferences |
Intersite Replication Error Check | Intersite |
Cross Reference Check Tests | CrossRefValidation |
Security Descriptor Reference Check Tests | CheckSDRefDom |
New to ADSelfService Plus?
Related Articles
Troubleshooting Failed Diagnostic Tests
This KB is intended for troubleshooting Diagnostic Tests with Failed results. If you encounter any errors displayed in the monitor that prevent the execution of Diagnostic tests, or if there is no data available for Diagnostic Tests, please refer ...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 WinRM errors
This KB serves as a guide for troubleshooting errors when using the WinRM mode of data collection. First, ensure that all the following conditions are met: Refer to the below link and check if all the WinRM prerequisites have been completed properly ...Active Directory monitor health getting affected due to port connectivity test
From the build number 14071 port connectivity test feature have been introduced. If a few ports were down and unable to connect this behavior will affect the health of the corresponding Active directory monitor. To clear the critical health alert ...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 ...