AD FS Help Diagnostics Analyzer
Use the Diagnostics Analyzer to run a comprehensive health check on your AD FS server. After you run a PowerShell script and obtain the JSON file that the script provides, we will show you the resulting diagnosis of your server and reasons for any failures, as well as provide steps for resolution.
AD FS Diagnostics Analyzer helps run multiple checks across both AD FS and WAP servers. It helps reduce the manual effort in troubleshooting issues in your AD FS environment.
To run the Diagnostics Analyzer, you must install the AD FS Toolbox PowerShell module. Based on connectivity to the internet from your AD FS server, you can install the ADFSToolbox module directly from the PowerShell gallery. In case of no connectivity to the internet, you can clone the GitHub repository for manual installation.
PowerShell version 4.0 or greater is required for this module. You can run $PSVersionTable.PSVersion.Major in a PowerShell window to get the PowerShell version. Learn how to upgrade to PowerShell 4.0 >Use the arrow keys to navigate through the pivots and tab to focus on focusable content inside a pivot section
- Using PowerShell Gallery
Using PowerShell gallery selected
- Launch an elevated PowerShell session.
Install the AD FS Toolbox Module.
Run the PowerShell command below to execute diagnostics tests and create the output file.
On an AD FS 2016 server, the module automatically detects the AD FS servers in the farm based on your AD FS configuration. For 2012 R2, and in cases where the server listed in the configuration of the AD FS 2016 farm is not correct, you can use –adfsServers argument to specify the AD FS / WAP servers on which the tests need to be executed.
For example: Export-AdfsDiagnosticsFile -adfsServers @("sts1.contoso.com", "sts2.contoso.com", "sts3.contoso.com")
See https://aka.ms/adfsdiagnosticsanalyzerdocs for more details.
Note: If you need to run the tests on your WAP servers that are not domain joined, run the same cmdlet on the individual WAP servers and upload the files individually.
HISTORYUpload a diagnostics file, or sign in to view previously uploaded diagnostics runs.