• Last update on February 22nd, 2024

This article presents a list of frequently asked questions about the Hybrid Connector Diagnostic Tool, providing you with expert guidance for efficient troubleshooting and connectivity management.

Can I run the CoreView Diagnostic Tool using a proxy?

Yes. To use the CoreView Diagnostic Tool with a proxy, read the instructions described in the Proxy support article. Then, follow these steps:

  1. Export your proxy.reg file into the c:\temp folder.
  2.  Run the CoreView Diagnostic Tool with the following command in Docker:
docker run -v c:\temp:c:\temp --rm -it --entrypoint powershell cvhybridtool.azurecr.io/cvdiagnostictool:xxxx

Replace xxxx with the version of your Connector, such as 2016 or 2019.

  1.  Once the Docker container is running, execute these commands to import the proxy configuration and access the CoreView Diagnostic Tool menu:
cd temp
regedit.exe -S c:\temp\proxy.reg
cd app

Now, the CoreView Diagnostic Tool main menu should appear, and you can perform all the available tests with the imported proxy settings.


Can I test if my gMSA accounts work using the CoreView Diagnostic Tool?

Yes. You can import your credential spec file associated with the gMSA when running the CoreView Diagnostic Tool by using the following Docker command:

docker run -v c:\temp:c:\temp --security-opt "credentialspec=file://yourcredentialspecfilename.json" --hostname your_gMSA_account_to_test --rm -it cvhybridtool.azurecr.io/cvdiagnostictool:2019

Make sure to replace yourcredentialspecfilename.json with the actual name of your credential spec file and your_gMSA_account with the hostname you want to test.

Credential spec files are typically located in: