The Test-CzProxyConfiguration cmdlet test your proxy configuration. This can help if your company uses a proxy and you need help to debug the problem.
Test-CzProxyConfiguration [-Uri] <String> [[-Proxy] <System.Net.IWebProxy>]The Uri parameter defines the http resource. The proxy configuration is checked for just this Uri
The Proxy parameter configures the proxy configuration you want to debug. If you don't set this parameter it will uses [System.Net.WebRequest]::GetSystemWebProxy(), witch is the system defaults proxy.
The hostname that the test was for.
The result of the TCP connection Test. If this is true, you shouldn't use a proxy!
A recommendation if you should set the hostname on the proxy bypass list.
Shows if the hostname is already on the bypass list.
If there is an exception while the tests run, it will be shown here.
Important: not all exception mean something bad, in special in this network world. So read them carefully, before you ask your admin. 😉
A message that contains a human readable action the user should do, to optimize his setup.
This will create the message from the test result. See Message field.
Test-CzProxyConfiguration -Uri "https://bing.com/";This example will test, if you can reach the website https://bing.com/ with your current system configuration.
Test-CzProxyConfiguration -Uri "https://bing.com/" -Proxy (New-Object System.Net.WebProxy("http://proxy.company.com:80"));This example will test, if you can reach the website https://bing.com/ with the configured proxy from the proxy parameter.
$proxy = New-Object System.Net.WebProxy("http://proxy.company.com:80");
$proxy.BypassList = @("bing.com")
Test-CzProxyConfiguration -Uri "https://bing.com/";This example will test, if you can reach the website https://bing.com/ with the configured proxy from the proxy parameter. It configures also a bypass on the hostname bing.com.