As previously mentioned , the CoreView Diagnostic Tool utilizes the Docker Runtime Environment (RTE) to operate. Please refer to the software requirements section in the Hybrid Connector deployment guide for installation recommendations regarding Docker RTE.
Preliminary notes
Server
We recommend running the CoreView Diagnostic Tool from the same server where you plan to deploy the CoreView Hybrid Connecto. This allows you to perform connection tests from the same host that will run the CoreView Hybrid Connector in your production environment.
Proxy
Please note that if you're running the CoreView Hybrid Connector behind a proxy, you'll first need to verify if your proxy settings are assigned to your Windows PowerShell session. If you're unsure, please run the following command for the HTTP proxy:
$env:http_proxy = "http://xxx.xxx.xxx.xxx:port"Or the following for the HTTPS proxy:
$env:https_proxy = "https://xxx.xxx.xxx.xxx:port"Download
To download the latest container image of the CoreView Diagnostic Tool, please open a PowerShell session with administrative rights and execute the following commands:
docker login -u 62f8c18f-5326-430e-ac17-2fdd8f0c280e -p l8K8Q~bnBU5d8feNR5ABfB6PGRGD-j2XvuiHzcGu cvhybridtool.azurecr.ioRun
Once you've completed the previous steps, you should proceed to download the Docker Diagnostic Tool image.
2016 version
For the 2016 version, please execute the following command:
docker pull cvhybridtool.azurecr.io/cvdiagnostictool:20162019 version
For the 2019 version, please execute the following command:
docker pull cvhybridtool.azurecr.io/cvdiagnostictool:2019Please be aware not to use PowerShell ISE, as it is not supported by the CV Diagnostic Tool. We also recommend expanding your PowerShell window to full screen to avoid any issues with the command-line tool.
2016 version
When you see the messages displayed in the above picture, please execute the following command to run the CV Diagnostic Tool for the 2016 version:
docker run -v c:\temp:c:\temp --rm -it cvhybridtool.azurecr.io/cvdiagnostictool:20162019 version
If you have previously downloaded the 2019 version of the CV Diagnostic Tool, please run the following command instead:
docker run -v c:\temp:c:\temp --rm -it cvhybridtool.azurecr.io/cvdiagnostictool:2019 Select the data center
You will now see the following screen, where you can select your data center. In the image below, I have entered "EU" and pressed enter to connect to the European CoreView Datacenter:
Test
From the above menu, you can select any test you would like to perform to evaluate if your CoreView Hybrid Connector will work in your environment:
- Option (1) will test your configuration of the WinRM protocol used for connecting to your Active Directory domain controller.
- Option (2) will simulate connections to internet endpoints used by the CoreView Hybrid Connector.
- Option (3) will test connectivity, authentication method, and protocols used for connecting to your Exchange Server.
- Option (4) will test connectivity and the protocol used for connecting to your Active Directory domain controller.
- Option (5) will let you switch between different CoreView data centers.
- Option (6) will open a PowerShell runspace without any PowerShell module already loaded, where you can manually input the cmdlets you would like to test.
- Option (7) should be used in combination with other tests and it will save the results of the executed tests in a file located in the C:\temp directory.
- Option (8) will close the CV Diagnostic Tool session.
- Option (9) will display detailed information about the above options.
For example, you can run 1,2,7 and you will find the results also displayed in a JSON file saved on your C drive.
When prompted, please ensure to provide the same credentials you plan to configure on the CoreView Hybrid Connector as service accounts. For instructions, refer to the hardening CoreView Hybrid Connector service accounts’ permissions in the Hybrid Connector deployment guide.
Option (6) - Powershell Runspace
You may be interested in performing some additional tests that are not natively available within the native options of the CV Diagnostic Tool Menu.
By selecting option (6), you will have the opportunity to open a PowerShell runspace similar to the one opened by the CV Hybrid Connector.
Please note that runspace "6" does not have any installed PowerShell modules. So, if you are going to test a specific command-let that requires a module, please remember to import it beforehand.
Refer to this article for a list of PowerShell module versions installed on the CV Hybrid Connector. Download and install the same version on the CV Diagnostic Tool when using option (6).
That module will be available only in your runspace until you exit from it. In fact, closing a runspace by typing "exit" and pressing enter will erase everything you previously imported and executed.
Below, you can find some command lets useful for testing additional connections made by the CV Hybrid Connector through option (6) of the CV Diagnostic Tool:
# Enable Tls protocol to perform https connection tests
[Net.ServicePointManager]::SecurityProtocol = "Tls, Tls11, Tls12, Ssl3"
# Test Microsoft Connection
Invoke-webrequest -uri https://www.microsoft.com -UseBasicParsing
# Test SSL Certificate revokation list
Invoke-webrequest -uri https://sectigo.com -UseBasicParsing
# Test Exchange Online Connection
$adUsername = "upn"
$adPassword = "password" | ConvertTo-SecureString -AsPlainText -Force
$Credentials = new-object -typename System.Management.Automation.PSCredential -argumentlist $adUsername, $adPassword
$cs = Get-Credential -Credential $Credentials
Connect-ExchangeOnline -Credential $cs
# Test Teams Connection
[Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12
$adPassword = "password"
$adUsername = "username"
$adPassword = $adPassword | ConvertTo-SecureString -AsPlainText -Force
$Credentials = new-object -typename System.Management.Automation.PSCredential -argumentlist $AdUsername, $adPassword
$cs = Get-Credential -Credential $Credentials
Connect-MicrosoftTeams -Credential $cs -LogFilePath "c:/temp/teams-logs.txt"
Get-CsApplicationAccessPolicy | convertTo-Json