How does each Version of MED-V use Proxies?
In Version 1, the MED-V Management Console, will use the IE proxy settings of the current user to connect via HTTP to the MED-V Policy Server. If the proxy server is not configured correctly, it will trigger an Event ID 75 error:
“The MED-V Server is unreachable at <URL> “
Please check your connectivity and try again.
In fact, any operation in the MED-V Management Console (v1) will use the user’s proxy settings including the uploading of images to an image distribution server. For the MED-V Client service and application, it is different in that it uses the system’s proxy configuration for all operations including authentication, policy, and image download.
MED-V Version 2
For MED-V Version 2, there are no images or policies to download. So the likelihood of proxy issues with MED-V agents specifically will likely not be an issue although it is important to point out that Host and guest proxy configurations are not automatically kept in sync by MED-V.
Setting Proxies at the System Level
For Windows XP, you use the proxycfg command to set system account proxies.
For Windows Vista and Windows 7, you would use the netsh command:
netsh winhttp set proxy – http://technet.microsoft.com/en-us/library/cc731131(WS.10).aspx