vSphere Host Upgrade Utility & Proxy Server

[robertortel]

Hello,

I have the vSphere Host Update Utility and I am trying to upgrade my ESXi server. But this fails at the beginning because the utility does somehow not work correctly with a proxy server or I am doing something wrong.

There is the settings.config file, and inside it I tried all those cases (assuming 'proxyserver' is my proxy server) without success:

fails

I know there are some threads with the same topic out there, but in none of those I found a solution to this problem.

Regards,

Robert

[robertortel]

PS: The proxy does not require user authentication, so this is not the problem.

Robert

[AntonVZhbankov]

Robert, take a look at this thread: http://communities.vmware.com/thread/220333

---

VMware vExpert '2009

http://blog.vadmin.ru

[robertortel]

What you mean is this Machine.config modification in .Net?

I did it for the installed 1.1.4322 and 2.0.50727 (where it is in the web.config) CLRs. For Versions 1.0.3705, 3.0 and 3.5 I did not find the appropriate file to change it.

I know, the vSphere Host Update Utility runs in CLR 2.0.50727 (now a modified version). My proxy is set like:

and I see the update utility to contact the right host in Process Explorer, but somehow I always get

"An error has occured. Download failed."

Any ideas? I cannot believe that this is such a complicated issue ...

Robert

[robertortel]

Nobody around with an idea for that? Looks like the whole update issue behind a proxy is still unsolved ...

Robert

[AntonVZhbankov]

Ypu know, I had such problems myself with Update manager in vCenter 2.5. But I solved it with our networking team by allowing web access without authorization from host with vCenter.

vSphere Update manager now works with basic proxy authorization without any problems.

---

VMware vExpert '2009

http://blog.vadmin.ru

[robertortel]

I already promoted you 'helpful', as I am sure the .NET things have been part of this problem. But the key was that I did identify the wrong proxy server in our proxy conf script. Taking the correct one solves this issue.

Regards,

Robert

[AntonVZhbankov]

Glad to hear it.

---

VMware vExpert '2009

http://blog.vadmin.ru