You are not the only one 
assuming they will resolve prior to an update being released
As RParker said vapp-updates.vmware.com resolves but its an alias to e751.d.akamaiedge.net [96.7.131.51] which is Akamai's HTTP Acceleration/Mirror service.
| Appliance Name: | vSphere Management Assistant (vMA) | |
| Appliance Version: |
|
| Last Check: | Failed to check for updates (Error contacting update server. Please check network configuration. The requested URL returned error: 404 URL: http://vapp-updates.vmware.com/vai-catalog/valm/vmw/449bf27f-70b9-476e-af17-fc4369637c25/5.0.0.0.lat...) on Thursday, October 13, 2011 10:45:30 AM GMT-07:00 |
danzig69 wrote:
I just hanging my phone with vmware support and it said to me that there is currently no update avalaible 09 nov 2011 15:49 gmt -5. That's why we received this error 404 message. I ask them to put a more specific message when there is no update avalaible! See in the futur if they will do...
So for now it's normal to received this error 404, it's a brand new product that do not currently need update.
That is INCORRECT. I have since discovered that some appliances are a different build, the CORRECT build is 5.0.0.3324 Build 472350
When I select check updates, even though there are no updates, it should STILL say no updates available, or appliance is up to date, something like that.. the error (the part that I discovered) that since the appliance is NOT the correct build, it gives an error because the path to the update site is wrong, it's not because there are no updates.
The ERROR is just that, an ERROR, that's why I mentioned it. Even if updates are not ready, it should NOT give an error, it should get to the site and report "no updates". That date you give will come, and you will STILL not find the correct updates, because of the ERROR, hence why I posted it.
Copy and past that link .. I BET you get different results, which proves VM Ware support is NOT telling the whole truth. (update -> settings -> use specified repository)
danzig69 wrote:
How and who can put this question as answer and give 10 point to RPaker?Knowing that I helped you, and it worked, is all the "points" I need
Ok, I must be dense. Either that or vmware is dense
I am going out to http://downloads.vmware.com/d/details/vma50/dHRAYnQld3RiZHAlJQ==#drivers_tools
(Main Site, Support & Downloads, VMWare vSphere, Related Drivers & Tools, VMWare vSphere Management Assistant 5.0 (vMA))
And it is giving me the 5.0.0.0 build 472630 version.
Where on earth do I get the 5.0.0.3324 build?
Why is VMWare keeping the broken build on its main downloads?