Before you import 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.

To import the 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 vCloud Automation Center deployment. All of the values for each machine must be present in the target vCloud Automation Center deployment for the import to succeed. You can change the values for reservation, storage location, blueprint, and owner for each machine you want to import by editing the CSV file.

Open the CSV file and edit the data categories so that they match existing categories in the target vCloud Automation Center 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 vCloud Automation Center instance.

Host To Storage (Name or ID)

Must match the name of a storage location in the target vCloud Automation Center instance.

Blueprint (Name or ID)

Must match a blueprint in the target vCloud Automation Center instance.

Owner Name

Must match a domain user in the target vCloud Automation Center instance.