VMware Cloud Community
markus_herbert
Enthusiast
Enthusiast
Jump to solution

VUM Problem

For testing purposes I installed a VCenter Server v 4.1.0 Build 258902 (German-000) on a W2008 R2 Server.

Trying to get the newest patches will show the followin error message:

- Downloading the patch definitions for this host failed.

Configuration -> Patch download settings -> Test (with active proxy) showed me:

- unable to acces http://www.vmware.com

- ok to access http://www.microsoft.com

But with my IE8 browser I'm able to access http://www.vmware.com

I tried also to disable the firewall of the W2008 R2 server -> same problem

Can anyone help me about this problem?

Thanks for any reply.

0 Kudos
1 Solution

Accepted Solutions
a_p_
Leadership
Leadership
Jump to solution

But again theres no problem to download these file manually with my IE8 (with proxy enabled) and store them to C:\windows\temp .

That's why I asked, which authentication you are using. When you are using IE, then you are in the context of the logged on user, VUM however is (most likely) configured to run as "local system" and therefore might be restricted by your proxy server.

I'm not familiar with ISA server, but I think you will have to configure a rule for the system running VUM, to allow unautorized access to vmware.com. Since you are able to access microsoft.com, you should already have some rules defined.

André

View solution in original post

0 Kudos
5 Replies
a_p_
Leadership
Leadership
Jump to solution

What kind of proxy authentication do you use?

Maybe you have to allow "vmware.com" without authentication on your proxy for this system .

Did you take a look at the log files at C:\Users\All Users\VMware\VMware Update Manager\Logs?

André

0 Kudos
markus_herbert
Enthusiast
Enthusiast
Jump to solution

I use proxy with authentification (ISA-Server) on Port 8080.

During the installation I changed the VCenter Management Web-Services port from 8080 to 8081.

This seems to be the first error:

Status code: 502

Error retrieving document 'https://xml.shavlik.com/data/hfnetchk6b.cab'. Unhandled status code: 502

Retry https://xml.shavlik.com/data/hfnetchk6b.cab with proxy off

Downloading https://xml.shavlik.com/data/hfnetchk6b.cab

Status code: 502

Error retrieving document 'https://xml.shavlik.com/unix/linux-bok.xml'. Unhandled status code: 502

But again theres no problem to download these file manually with my IE8 (with proxy enabled) and store them to C:\windows\temp .

I also addes https://xml.shavlik.com to the trusted sites in the properties of my IE8 browser.

0 Kudos
a_p_
Leadership
Leadership
Jump to solution

But again theres no problem to download these file manually with my IE8 (with proxy enabled) and store them to C:\windows\temp .

That's why I asked, which authentication you are using. When you are using IE, then you are in the context of the logged on user, VUM however is (most likely) configured to run as "local system" and therefore might be restricted by your proxy server.

I'm not familiar with ISA server, but I think you will have to configure a rule for the system running VUM, to allow unautorized access to vmware.com. Since you are able to access microsoft.com, you should already have some rules defined.

André

0 Kudos
markus_herbert
Enthusiast
Enthusiast
Jump to solution

Thanks for your help.

I added

*.vmware.com

*.shavlik.com

to my "through system policies authorized sites" in my ISA Server and that worked for me.

"netsh winhttp import proxy ie" won't worked for that case.

0 Kudos
RLI27
Contributor
Contributor
Jump to solution

Hi all

I have the same problem but with vCenter V4.0 on Win2008R2... My VUM service is running as local system as well. Our proxy authenticates with AD users. Under "Update Manager > Configuration > Patch download settings" you can specify a proxy user. As far as I understand VUM should use these settings to validate on the proxy. Why should I need to change the VUM service account to an AD user when I can configure theses settings for VUM in vCenter?

Exclusions on the proxy should not be an option when the software is able to authenticate correctly. On Win2003 - with same VUM version - this was not a problem and it worked just as expected. Is Windows doing something different?

0 Kudos