Install Plaivid via OVA Import

This guide covers the VMware installation path for Plaivid: import the Plaivid.ova virtual machine with the supplied PowerShell script and ovftool, then verify its network settings before starting it. The same procedure can import other Avid OVA files when their names are configured in the script.

Important Notice

Due to the way Avid OVA files are compressed, they must be imported exclusively using the method described in this guide. Using other import methods may result in various errors during the import process.

Prerequisites

Download the following files and software from the VM Images section of files.cloudavid.com:

Item	Description	Download
Import-VMs-from-OVA.ps1	PowerShell import script	⬇️ Download
VMware ovftool	Required utility used by the script	⬇️ Download
.ova files	Virtual machine images you want to import	⬇️ Download
PowerShell	The default command-line shell on Windows 10 and Windows 11	Included with Windows

When downloading OVA files, always use a download manager and make sure you have sufficient free disk space before starting the download.

Step 1: Prepare the Files on Your System

1. Extract the downloaded VMware ovftool ZIP archive. After extraction, place the ovftool folder in the following location:

   C:\Tools\ovftool

2. Place the .ova files in a dedicated directory. For example:

   E:\Exports

3. Save the Import-VMs-from-OVA.ps1 script to your local system.

Add ovftool to the PATH Environment Variable

1. Search for Environment Variables in the Windows Start menu.

2. Open Edit the system environment variables, then click Environment Variables.

3. Under System variables, select Path and click Edit.

4. Add the directory containing ovftool.exe. For example:

   C:\Tools\ovftool

5. Click OK to close all windows, then open a new PowerShell session.

To verify that ovftool is correctly configured, run the following command in PowerShell:

Get-Command ovftool

If the configuration is correct, PowerShell should display the path to ovftool.exe.

Note: If the command returns an error, ovftool has not been added to the PATH correctly, or you have not opened a new PowerShell session after updating PATH.

Step 2: Configure the Script

Open Import-VMs-from-OVA.ps1 using Notepad or PowerShell ISE.

At the beginning of the file, locate the CONFIGURATION section. Modify only the following values to match your environment:

$EsxiHost   = "172.16.41.3"      # IP address of the destination ESXi host
$Datastore  = "DataStore"        # Destination datastore name (without [] and case-sensitive)
$SourceDir  = "E:\Exports"       # Directory containing the .ova files
$VMNames    = @("Plaivid")       # VM names, matching the OVA filenames exactly (without the extension)
$DiskMode   = "thin"             # Virtual disk provisioning mode

Important Configuration Notes

• Replace $EsxiHost with the IP address of your destination ESXi host.

• The $Datastore value must exactly match the datastore name on the destination host, including capitalization. Do not include the square brackets commonly used when displaying datastore names in VMware interfaces.

• If your OVA filename differs from Plaivid.ova, update $VMNames to match your actual filename.

  For example, if your files are named Web.ova and DB.ova, use:

  $VMNames = @("Web", "DB")

• Specify filenames in $VMNames without the .ova extension.

After making the necessary changes, save the script.

Step 3: Run the Script

1. Open PowerShell using Run as Administrator.

2. Navigate to the directory where you saved the script:

   cd C:\Path\To\Script

   Replace C:\Path\To\Script with the actual path to the script's directory.

3. If PowerShell reports an Execution Policy error, run the following command once in the current PowerShell session:

   Set-ExecutionPolicy -Scope Process -ExecutionPolicy Bypass

4. Run the script:

   .\Import-VMs-from-OVA.ps1

Step 4: Provide Credentials When Prompted

During execution, the script prompts you to enter the following information:

Prompt	Description
Enter ESXi username	Username for the destination ESXi host, typically root
Enter ESXi password	Password for the specified account. Characters are not displayed while typing.

After you provide the credentials, the script automatically imports all virtual machines listed in $VMNames, processing them in the specified order.

Import progress is displayed in the same PowerShell window.

Step 5: Verify the Import Results

When execution finishes, the script displays a summary of the operation.

• A green SUCCESS message indicates that the corresponding virtual machine was imported successfully.
• A FAILED message accompanied by an exit code indicates that the import failed.

The final output also lists the virtual machines that were imported successfully and those that failed.

Step 6: Post-Import Configuration — Important

All virtual machines are imported in a powered-off state. The script intentionally does not power them on.

Before starting any imported virtual machine, complete the following steps:

1. Access the ESXi management interface, such as vSphere Client or ESXi Host Client.
2. Right-click the imported virtual machine and select Edit Settings.
3. Locate the Network Adapter section and verify its configuration:
   • The virtual machine may be connected to a port group that does not exist on the destination host.
   • The network adapter may be Disconnected.
4. Correct the network adapter settings as needed, then click OK.
5. Once you have verified that the network settings are correct, power on the virtual machine.

Troubleshooting Common Errors

Error	Cause and Resolution
ERROR: ovftool not found in PATH	ovftool has not been added to PATH correctly, or PowerShell was not reopened after the PATH change. Verify the configuration and open a new PowerShell session.
ERROR: You still need to set $EsxiHost ...	The $EsxiHost or $Datastore value has not been configured in the CONFIGURATION section.
ERROR: Cannot find ... \Plaivid.ova	The $SourceDir path is incorrect, or the filename does not match an entry in $VMNames.
FAILED: ... (exit code ...)	Common causes include an incorrect ESXi IP address, username, password, or datastore name. Review the CONFIGURATION values and verify your credentials.
Execution Policy error during execution	Run Set-ExecutionPolicy -Scope Process -ExecutionPolicy Bypass, then execute the script again.

Summary: Pre-Import Checklist

Before running the script, verify the following:

• ovftool has been added to the PATH environment variable.
• $SourceDir points to the correct directory containing the OVA files.
• $EsxiHost contains the correct destination ESXi IP address.
• $Datastore exactly matches the destination datastore name, including capitalization.
• $VMNames matches the OVA filenames, without their .ova extensions.
• Your ESXi login credentials are correct.
• After the import, the Network Adapter settings of each virtual machine are reviewed and corrected as necessary before powering it on.