Author : Martina Laleva
URL : http:////docs.vmware.com/en/VMware-vSphere/6.0/com.vmware.vsphere.vm_admin.doc/GUID-B413FBAE-8FCB-45...
Topic Name : Populating Libraries with Content
Publication Name : vSphere Virtual Machine Administration
Product/Version : VMware vSphere/6.0
Can I move or copy existing ISO files in datastore to content library ?y ?
It isn't possible, you can to need export files.
You might need to export an item from a content library to your local system.
Has anyone heard if this was going to be possible one day, the first thing I thought of when I first learned of the content library is this, so we more efficiently manage datastore isos.
I have put ISO files into Content Library, altough VM CD-ROM cant map to it if Content Library ISO file is not in the same ESXi. VM templates you can access from everywhere, but ISO files not. ISO files are put in "other" files.
altough VM CD-ROM cant map to it if Content Library ISO file is not in the same ESXi.
Thats the part I'd love, instead of finding dvd184.108.40.206.iso, you could have a content iso that says windows 2019 that you can attach to a vm. Yes you can organize them with folders, it just seems cleaner to have something manage it outside of a datastore.
Maybe too late but the answer is Yes you can !
I faced the same situation today and got around it by doing the following -
Login to the vSphere Flash client (tested on version vSphere 6.5)
This is where you will do the trick. Open another tabin your browser and Login to your ESXi Host using this URL - https://ESXI_HOSTNAME/folder
Click on ha-datacenter-> Name of the datastore-> path to your file.ISO
Now right click on this file and click copy link address. Paste it in the URL field in above and pass the credentials. So the URL should look something like this -
I tested this with the HTML5 client and it did not work but works fine with the Flash client.
@krisbud — Thanks so much for your contribution! I couldn't have figured it out without your post.
However, I wanted to elaborate on your approach because I had to get past some wrong assumptions on my part to get it working, and thought what I learned might help others.
First. be sure to URL encode the username:password.
In my case the username was an email address with an @-sign, and the password had a #-sign, so if my username and password were email@example.com and #elloWorld then my URL-encoded version would be foo%40bar.com%3A%23elloWorld.
You can google for a URL encoder, or just use urlencoder.org.
Also, I had a mental block about https://ESXI_HOSTNAME/folder. I never actually went to that URL but instead tried to find the link in the vSphere UI.
So... if you are reading this be sure to visit just the https://ESXI_HOSTNAME/folder URL with nothing after it — of course replacing ESXI_HOSTNAME with your site's IP address or domain name — and then I think everything else should become clear.
Hope this helps.
P.S. OTOH it would be MUCH nicer if VMware just added this functionality to the menu in the UI...