ISO image information and guest agent ISO settings are migrated but you must recreate ISOs and templates that contain a guest agent. Update migrated blueprints, custom properties, and build profiles to reflect the name of the new ISO or template.
ISO location information in the build profiles and blueprints and template information in the blueprints is migrated. However, you must reconfigure the ISOs and templates after migration to point to the system on which the manager service is running, for example a virtual machine or a load balancer. After migration is finished, recreate ISOs and templates that contain a guest agent.
For example, if you used vRealize Automation for WIM-based provisioning, you must regenerate your WinPE images after migration.
For templates that have the guest agent running on them as a service, uninstall and reinstall the guest agent and point to the guest agent at the new manager service host name.
You perform the following general procedure to update migrated blueprints, build profiles, and custom properties:
Review the pre-migration and migration reports for migrated build profile, blueprint, and custom property information.
Open a migrated build profile, blueprint or custom property that contains guest agent ISOs or templates.
Change the name of the old ISOs and templates to that of the new ISOs and templates.
The new ISOs and templates point to the host name of the vRealize Automation manager service.
Repeat for each migrated build profile, blueprint or custom property that contains guest agent ISOs or templates.
For details about creating ISO images and working with guest agents, see the following IaaS Configuration topics in the vRealize Automation documentation.
Preparing for WIM Provisioning
Preparing for Linux Kickstart Provisioning
Create a WinPE Image by Using PEBuilder