Deleting Blueprints that are still referenced by managed vms

[prestonville]

We have deleted a number of blueprints that are still referenced by managed VMs in vRA7.5. This was allowed (which surprised me) and in managed machines the VMs still show the deleted Blueprint names. At the moment nothing is broken in vRA and the VMs can be managed with 2nd day operations as presumably all blueprint info in the SQL DB. Not sure how to best to get out of this? Has anyone fixed the same issue?

To change the blueprint tied to the VM the only way i know is via bulk import and then I would tie them to a generic blueprint just for 2nd day operations/leases.

This has happened as we tied blueprints to OS versions via fixed templates so we do have blueprint sprawl with all the available Linux versions out there. The way forward could be selectable templates using vRO code but as I'm running 7.5 do anyone know of another way without the custom code?

Thanks.

[daphnissov]

This has happened as we tied blueprints to OS versions via fixed templates so we do have blueprint sprawl with all the available Linux versions out there. The way forward could be selectable templates using vRO code but as I'm running 7.5 do anyone know of another way without the custom code?

SovLabs Property Toolkit is what I see used most often. Allows you to use logic within vRA itself to pick what template you want. Requires no custom vRO code at all. There is also Component Profiles but that is more restricted than the first option.