I have downloaded and exported a repository using the vmware update download service installed on a different computer. When I move the repository to another computer (that does not have internet access) and try to configure update manager to use it as a shared repository, I keep getting an error that it is not connected. I have tried to connect to it via a usb drive and then I copied the files to a local E: drive and configured the shared repository to point to that path in the patch download settings but it always say's not connected. Any ideas why? According to the documentation I should be able to use a local disk as a repository. The path I am using is e:\vmpatches\hostupdate\ and then all the files are listed there. It has a hostupdate20-consolidated-index.xml file in the directory which I think would be the list of patches, as well as a update_metadata.xml file.
Hi,
do you have a file into the shared folder - version.txt
It should be there and its content is something like-
Created with VMware Update Manager Download Service : 4.0.0 build-162871
if you don't have it try to do it manually to what will be the result
thanks,
Petko
Thanks i just discovered that after checking the update manager logs that it was looking for a version.txt file.
followed steps correctly, but i keep getting error:
Incompatible repository. Please provide repository from update manager download service 400 to 400 U1...although i am using U1 binaries..
any clues ?
Hi!
We're playing around with VUMDS right now and have met the same problem. Turns out the URL musn't end with a slash, i.e. http://vumds.example/patches works for us and http://vumds.example/patches/ doesn't.
We're running v4.1 but maybe this helps.
/Mario
Hi,
please how did you publish those patches on http://example/patches? For me its not working. Im trying to publish it through IIS. Is that right way to publish patches?
Guys here is answer to my question:
Configure an Apache or an IIS Web server as a patch source for vCenter Update Manager
i was having the same problem until i installed vc client on the Update manager server, moved the exported patches to that server and then configured update manager to use a shared repository pointing the to the exported patches folder that was local to the update manager server.