HPE vipsdepot URLs in vSphere 7 needed?

[roland_geiser]

Hello

We are on vSphere 7 and do the upgrade procedure for our HPE ESXi Hosts by VUM and still use the update baselines. In the earlier releases, we entered the HPE URLs from the HPE vibsdepot (http://vibsdepot.hpe.com/index.xml, http://vibsdepot.hpe.com/index-drv.xml) in Lifecycle Manager. But now, all seems to be included in that baseline "Partner provided Addons for ESXi" and probably also the baseline "VMware Certified Async Drivers for ESXi":

How do you handle that? Do you still attach the HPE URLs in addition?

And when you want to upgrade the HPE specific drivers and tools (without upgrading the OS, so not using the HPE custom ISO). How do you make shure that you can filter only the HPE drivers/tool and only install/update these HPE related drivers/tools? So in principle update (the base is always a HPE custom image where all tools and drivers are present - so its mostly an update of them) all the tools/drivers that make the difference between the vanilla VMware Stock image and the HPE custom image by using lifecycle manager baselines. 

Best regards

Roland

[stadi13]

Hi @roland_geiser 

With vSphere 7 we switched from VUM to Lifecycle Manager. In Lifecycle Manager you defined an image at cluster level. You will be also able to specify the HPE vendor add-on and also further components like HPE SCM. The benefit is, that all the catalogs are synced between VMware and HPE and then provided to you through Lifecycle Manager for selection. The packages are also checked for compatibility by Lifecycle Manager.

Regards

Daniel