Now let's use one of the tools on the ADF's help site to verify the health of our ADF's deployment.
I'm on the ADF's server and I'll show you why in a minute.
And I have the site open in a browser.
So let's go to online tools and click Diagnostics Analyzer.
There are three steps to running the tool for the first time.
The page assumes you've already installed the PowerShell module, so it jumps right to the testing part.
Let's click on the first step.
It says we need PowerShell version for a greater and asks if we're running ad fs 2.1 or lower.
We're using AD for 2019, so we're okay since we're on the ad FS server.
We won't do a manual installation.
I'll just copy this PowerShell command and I already have PowerShell open as an administrator, so let's
paste this in and run it.
I actually need to download the latest version of New Get first.
So I'll say yes to that.
And PowerShell installs New Get and then downloads the ADF's toolbox module.
Now let's go back to the browser and copy the next command.
And this is just standard PowerShell to import the module.
Now let's go back and take a look at the steps under the manual installation tab.
It says here that you can install this on a computer other than the ADF's computer, like our Windows
ten management VM.
But then you need to copy the installation folder over to your ad FS server or the web application proxy
server that you want to run it on.
Then you can use remote PowerShell to run the tool.
That's why I just remote into the ad fs server so we can keep it simple for the demo.
Now let's go to the next step.
There's a command here to run the diagnostics and create the JSON file with the output.
If you want to test your web application proxy installation, you need to run the command on that server
separately.
So let's copy this command and run it in PowerShell.
It says the diagnostics file was created right at the root of the C drive and it shows us where to upload
the file for analysis.
Let's go back to the browser and click to move to the next step.
We need to log in with an Azure Active Directory account.
So I'll click the sign in button.
I'm already logged in with an account stored in my Azure Active Directory tenant and it says I need
to set up MFA because I'm a global admin.
But let's skip this for now.
And now the Diagnostics Analyzer tool is requesting permission to sign me in and read my profile.
This is an off 2.0 authorization flow that Azure ad uses to grant access to your account.
So I'll click Accept.
Now we can choose a file to upload.
So I'll pick that JSON file created at the root of the C drive by the PowerShell command and then click
upload a new diagnostic.
The online tool store's previous run so you can go back and see what's changed in your configurations
over time.
On the Health Test Results tab, there's a summary of the outcome of the tests that were run.
You can get information on each of these tests from this link.
You can see there's quite a few diagnostics run on the server.
But let's go back and look at the results.
There's one failed test.
It says extra net lockout isn't enabled.
This is something we'll be looking at later in the course when we install Web application proxy.
Then there's a warning about self signed certificates in the intermediate store.
This isn't anything that was done by our ADF for installation.
This has to do with our certificate authority configuration so we can move on.
Then there are all the tests that passed.
You can expand any of these to get the details.
At the bottom, some of the tests weren't applicable.
Let's go back up and look at the other tabs.
ADF's configuration gives us a summary of the current configuration because each run of the tool is
saved.
This lets you go back in time and see the configuration which can be useful for troubleshooting changes.
So it's a good idea to run this tool on a regular basis.
The next tab is for relying party trusts.
So these are the applications and organisations you've configured to use this ADF, RFS farm as their
identity provider.
Will be configuring those in the next couple of modules.
And finally, claims provider trusts as we only have the default claims provider trust listed here,
which is for Active Directory.
Later in the course, I'll show you how to set up a claims provider trust when federating with another
organisation.
So that's the Diagnostics Analyzer tool which can help you evaluate the health of your ADF's farm.
And it lets you save runs so you can trace back configuration changes over time.