Content libraries in vCenter are actually pretty interesting and not a very discussed topic. So when you need multiple hosts or VMs to be able to access resources between each other in the same vCenter you can set up shared storage, typically vSAN. Now what do you do if you need to share files between multiple vCenters? That is where Content Libraries come in, you can create a content library on one vCenter, this is the “local” content library and upload and needed files, ISOs, OVAs that you need, then on the other vCenter you can create a “subscribed” content library that points to the local content library on the other vCenter. Now with your content libraries set up let’s run through a scenario. Let’s say you have a Debian ISO and a new version just released, you would need to upload the same ISO on the two different vCenters in order to match the version, and you would need to actively make sure your content remains up to date on both. However, with a content library created on your vCenter and another vCenter subscribed to it you can simply alter the file there and both vCenters will receive the change. One additional note is that the content library will be backed up by storage local to the vCenter you are using it on, so if you have two vCenters accessing the content-library they will each have their own copies of the files. This post was a little longer than usual but always happy to right these! Please feel free to leave any comments with any questions and I will do my best to answer!