In order to execute the VAMT, there are several prerequisite requirements. These requirements are outlined in the sections below.
This project has been built leveraging the following components:
- Microsoft Windows Server 2019
- Microsoft Windows 10
Note
The aforementioned operating systems have been confirmed, but any OS with Windows PowerShell 5.1 should suffice.
- VMware vSphere 7.0+
Note
The aforementioned version(s) have been confirmed, but earlier versions may also be compatible.
- It is required to have Administrator access on the Windows OS where the script will be executed.
- It is recommended to have Administrator access in the vCenter(s) where the target VMs live.
- Ability to connect to your vCenter Server from your Windows OS using PowerCLI.
- Ability to connect to your SMTP server from your Windows OS using PowerShell*
- See: Send-MailMessage
- Ability to send syslog traffic to your syslog collector from your Windows OS*
Note
*Only required if using these features.
In order to execute the VAMT, there are configuration steps required in vCenter as outlined below.
- A Tag Category named
VAMTmust exist on each vCenter where target VMs live.- Single Cardinality required for the Category.
- Scope on the Category should be
VirtualMachine.
- The following tags must exist in the
VAMTcategory on each vCenter:- complete
- completeWithErrors
- readyToMigrate
- readyToRollback
- inProgress
- failed
- rolledBack
- PowerCLI should be installed and configured according to the documentation here: PowerCLI Installation Guide
- Pull the VMwareArchitectureMigrationTool.ps1 script down to a location where you have read/write access on your Windows OS.
- Pull the VAMT.psm1 module down to the same directory where VMwareArchitectureMigrationTool.ps1 sits.