AD FS Diagnostics Module

The AD FS Diagnostics Module contains commandlets to gather configuration information of an AD FS server, as well as commandlets to perform health checks to detect configuration issues based on common root causes identified during support engagements such as duplicate SPN, cert

4.3 Star
10,865 times
Add to favorites
Active Directory
E-mail Twitter Digg Facebook
Sign in to ask a question

  • Script compatible with ADFS 4.0
    2 Posts | Last post May 30, 2018
    • Hello, nico script, we upgraded to adfs 4.0 last week. i just want to know if this script can be used for adfs 4.0 ? i get results though.......
    • Hello, same need ... Have you already try it?
  • Using ADFS 3.0 on 2012 R2 and no CMDLets
    1 Posts | Last post January 08, 2018
    • I have a Windows 2012 R2 ADFS 3.0 servers and the CMDLets listed here are not there. I am using PS 4.0 on my ADFS servers.  Where do I get these CMDLets?
  • test-adfsserverhealth returns no results
    1 Posts | Last post August 09, 2017
    • Hi there
      I have imported the module but when i run test-adfsserverhealth it returns no results? We are running ADFS 2.0?
  • Getting error when trying to import module
    2 Posts | Last post August 09, 2017
    • Hi there
      getting the following when trying to import this module
      Import-Module : The script 'ADFSDiagnostics.psm1' cannot be run because it contained a "#requires" statement for Windows 
      PowerShell version 4.0. The version required by the script does not match the currently running version of Windows PowerShell 
      version 3.0.
      At line:1 char:1
      + Import-Module ADFSDiagnostics
      + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
          + CategoryInfo          : ResourceUnavailable: (ADFSDiagnostics.psm1:String) [Import-Module], ScriptRequiresException
          + FullyQualifiedErrorId : ScriptRequiresUnmatchedPSVersion,Microsoft.PowerShell.Commands.ImportModuleCommand
    • upgraded to ps version 4.0
  • How to run this script in ADFS 3.0 ?
    1 Posts | Last post May 08, 2017
    • Can you please update the script to run in ADFS 3.0 ?
  • Test shows no results
    1 Posts | Last post February 23, 2017
    • I am running the tool by importing the module then run the Test-AdfsServerHealth command.  It returns to prompt and never returns data.  We are running ADFS 3.0.
      The Get-AdfsServerConfiguration does the same thing.  Appears to run but ends quickly and no information is displayed.  The Get-AdfsServerConfiguration does work and displays the information about the server.  The other two commands don't appear to return anything.  Any ideas?
  • ADFS Health script
    1 Posts | Last post February 16, 2017
    • I've been searching for an ADFS health script that will generate an output of the ADFS farm along with its version, Server details etc in an HTML format which can be sent as an attachment or displayed in the body of email. Can you guys help to me obtain one?
  • Update ADFSDiagnostics.psm1 to reflect SHA256.
    1 Posts | Last post February 06, 2017
    • Hi The default algoritm is now SHA256 not SHA-1.
      Please change row 2218 to
      if ($aadRp.SignatureAlgorithm  -ne "")
      row 2221 to
      testResult.Detail += $aadRpName + " Relying Party token signature algorithm is not SHA256`n";
      Please change the two rows and update the ADFSDiagnostics.psm1
  • Learn how to write instructions
    2 Posts | Last post October 11, 2016
    • I can only assume this script is good, except how do I run this? Besides giving a cryptic "run import-module and parse the file...". How about just providing the command?
      I have tried:
      import-module ADFSDiagnostics.psm1
      All it does is open a notepad file with the contents of the script.
    • After importing the PowerShell module 
      PS C:\> Import-Module .\ADFSDiagnostics.psm1 
      PS C:\> Test-AdfsServerHealth
      This should give desired results.
  • Has this been validated on ADFS 3.0?
    1 Posts | Last post May 10, 2016
    • I am having several problems getting this working with ADFS 3.0.  The script appears to try to determine the version and act accordingly, but it's not working with my environment.  One function checks registry keys to determine the version, but the registry keys it's looking for to identify 3.0 do not exist on any of my ADFS servers (HKLM/Software/Microsoft/ADFS is not present).  
      Test-ADFSServerToken returns an error, "Unable to connect to server".  
      Any information available on this?  
1 - 10 of 20 Items