Update: AAD Connect Network and Name Resolution Test

Update: This tool has a new shortlink: https://aka.ms/aadnetwork

Since the tool passed the 500 download mark a few weeks ago, I've started getting more questions (internal and external) about a few of the tests and checks.  So, I decided to update/refine them to hopefully provide better guidance.

The big changes:

• Updated reporting method for TLS 1.2 configuration to provide specific guidance based on Windows version.
• Reporting a best-guess for .NET framework.  I used the table at /en-us/dotnet/framework/migration-guide/how-to-determine-which-versions-are-installed#net_d as the starting point for this feature.
• Updating the method for interrogating machine.config.  We have some guidance on /fi-fi/azure/active-directory/connect/active-directory-aadconnect-prerequisites#connectivity and /fi-fi/azure/active-directory/connect/active-directory-aadconnect-prerequisites#enable-tls-12-for-azure-ad-connect as to what the machine.config should look like if you're not familiar with it.  You'll typically only need to modify this if you're using a proxy server.
• Added test for a PowerShell transcription group policy.  Having a PowerShell transcription Group Policy configured ("enabled") will cause the installation to fail, since the installer uses Start-Transcription to record activities.
• Updated endpoints for Office 365 GCC/Worldwide.
• Added test for PowerShell versions for Windows 2008, Windows 2008 R2, and Windows Server 2012.

If you weren't aware of it before, you can run just a single test as well:

You can go find the updated version at https://aka.ms/aadnetwork.  Save someone some trouble today.

Comments

• Anonymous
  June 15, 2018
  Love the script but get this error at the end. Get-ItemProperty : Cannot find path 'HKLM:\SOFTWARE\Policies\Microsoft\Windows\PowerShell\Transcription' because it does not exist.
  • Anonymous
    June 15, 2018
    I updated the script and tested again. Get-ItemProperty fails and doesn't honor -ErrorAction SilentlyContinue if the parent node is not present. So, in this case, if HKLM\Software\Policies\Microsoft\Windows\PowerShell\Transcription had existed, the Get-ItemProperty query for the EnableTranscripting would be silent regardless of whether it exists or not. If HKLM\Software\Policies\Microsoft\Windows\PowerShell\Transcription doesn't exist, the call fails with the exception to the screen. I wrapped it in a try/catch block, which seems to have cleared the error. Thanks for finding this one! A cookie to you!