vRA 7.2 Linked Clone blueprint update

[IntegraRoger]

I need to update some components (and patch) the linked clone blueprints in my vRA 7.2 infrastructure. I am unable to find a procedure in the documentation to do so... I might be that the documentation is "lacking"

Also, I would like to change the name of the blueprints to be used. Where I say blueprint I mean the system that serves as the base (with a snapshot) for the linked clones...

Other than creating new copies of the base system, can anyone suggest a methodology to do so?

Thanks in advance,

Roger

[daphnissov]

When doing linked clones, the procedure is to do as follows when updating them:

1. Convert template to VM.
2. Delete current snapshot (commit).
3. Make necessary changes.
4. Shutdown.
5. Take new snapshot.
6. Convert to template.
7. Perform data collection on the compute resource where the template is registered.
8. Update blueprints that call this template selecting the new snapshot name.

If you wanted to change the name of this template in inventory, go back to step #8 and select the new name (or just type it in).

[IntegraRoger · Accepted solution]

where I run into a problem (with this) is:

• The systems that are the clone targets are not actual templates but shutdown VMs with a specific snapshot.
• I could do the updates and all, but when I went to deploy a new image, It would not connect and update the appdirector agent or the VRM Guest Agent ...
  • For this I had to delete the configuration (uninstall) and re-install from scratch.

so my process turned out to be:

1. turn on the system
2. update the patches and system software (in this case SEP)
3. uninstall the vRA agents
4. reinstall the vRA agents
5. shutdown the system
6. create a new base snapshot
7. Perform data collection
8. Update the blueprints

le sigh....