6.2

Table Of Contents
8 Select the name of the virtual machine resource from the Name drop-down menu.
9 Click OK.
Edit Virtual Machine CSV Data File
Before you import or update one or more virtual machines, you must edit the virtual machine CSV data
file so that each machine value matches a value that exists in the target deployment. If you are migrating
a virtual machine from one environment to another, editing is optional.
To import, update or migrate virtual machines contained in a CSV data file, each machine must be
associated with a reservation, storage location, blueprint, and owner that already exists in the target
vRealize Automation deployment. All of the values for each machine must be present in the target
vRealize Automation deployment for the operation to succeed. You can change the values for reservation,
storage location, blueprint, and owner for any operation on each machine by editing the CSV file.
If you are importing a virtual machine that uses a static IP address, you must append the appropriate
command to the CSV file.
Prerequisites
Generate Virtual Machine CSV Data File
Procedure
1 Open the CSV file and edit the data categories so that they match existing categories in the target
vRealize Automation deployment.
Heading Comment
# Import--Yes or No Can change to No to prevent a particular machine from being imported.
Virtual Machine Name Do not change.
Virtual Machine ID Do not change because it is ignored during the import process.
Host Reservation (Name or ID) Must match the name of a reservation in the target vRealize Automation instance.
Host To Storage (Name or ID) Must match the name of a storage location in the target vRealize Automation instance.
Blueprint (Name or ID) Must match a blueprint in the target vRealize Automation instance.
Owner Name Must match a domain user in the target vRealize Automation instance.
Custom properties are exported only for managed machines and appear in the CSV file following the
data categories. This table presents the custom property format.
Heading Comment
Property Name Custom property name, for example, __Legacy.Workflow.User.
Property Value Custom property value, for example, user%40org.sqa-horizon.local.
(H|N)(E|O)(R|P) Custom property flags: (H|N) = Hidden|Not Hidden - (E|O) Encrypted|NotEncrypted - (R|P) Runtime|
NotRuntime, for example, NOP = Not Hidden, Not Encrypted, Not Runtime.
System Administration
VMware, Inc. 36