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.1 Star
(16)
11,313 times
Add to favorites
Active Directory
2/12/2015
E-mail Twitter del.icio.us Digg Facebook
Sign in to ask a question


  • ADFS Ver 2.0 is returned in report in ASDF 3.0 environment
    1 Posts | Last post November 29, 2018
    • ADFS Team,
      Thank you for creating this diagnostic tool. It is very useful.
      
      Quick details of our environment:
      2 Windows 2012 R2 Datacenter Server ADFS Farm
      2 Windows 2012 R2 Datacenter Server Web Application Proxy Cluster
      
      When running the cmdlets of "Get-AdfsSystemInformation" or "Get-AdfsServerConfiguration" the output for the "AdfsVersion :" shows 2.0.  How is this possible if our environment was raised on Windows 2012 R2 servers.  From additional digging I found the one liner "(Get-Item C:\Windows\ADFS\Microsoft.IdentityServer.ServiceHost.exe).VersionInfo.ProductVersion".  When running this command the result that is returned shows "6.3.9600.17238".  According to MS documentation, ADFS ver. 3.0 has the build number 6.3.9600.17238.
      
      Why would you think the cmdlets within this module are reporting that we are running ADFS ver. 2.0 even though the environment was raised on 2012 R2 servers?  I would appreciate any explanation or information you could provide to help understand this further.
      
      Thank you,
      Anthony I.
  • test-adfsserverhealth returns no results
    2 Posts | Last post October 30, 2018
    • Hi there
      I have imported the module but when i run test-adfsserverhealth it returns no results? We are running ADFS 2.0?
    • The server must be running Powershell version 4.  If you have ADFS 2.0 you are probably running Windows 2012 which comes with Powershell 3.0, or windows 2008/R2 which would be PS v1 or v2 by default.  There are comments in the .PSM1 file here that reference ADFS 2.0 so that suggests it supports that earlier version, in addition to ADFS 3.0 (Windows 2012 R2).
  • Using ADFS 3.0 on 2012 R2 and no CMDLets
    2 Posts | Last post October 30, 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?
    • Download this file and put it in \Program Files\WindowsPowerShel[\Modules folder, then be sure your system environment variable "psmodulepath" has that folder included in it's definition under Control Panel >> System >> Advanced System Settings >> Environment Variables... >> System Variables >> PSModulePath >> Edit... >> add the following after the first ";":   C:\Program Files\MicrosoftPowerShell\Modules\;
  • Runs fine on ADFS 3.0
    1 Posts | Last post October 30, 2018
    • This module is amazing, shows great information for troubleshooting on Win 2012 R2 ADFS farm.  It is true that the broader Get-ADFSxxxxxx commands sometimes take a while to run, just let it spin for a few minutes and eventually it should come back with the info.  being able to create a Test-ADFSServerToken is the bomb... drop the output in Notepad++ with the XML-Tools plug-in installed and you can Pretty Print the XML to format it on separate lines for review.
  • 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?
      Thks
  • 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?
      
      Thanks,
      
      Dave
  • 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 "http://www.w3.org/2001/04/xmldsig-more#rsa-sha256")
      
      and
      
      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
      
1 - 10 of 22 Items