1.7. Required Images and Scripts

Even though you could create the required VMs from the Virtuozzo Hybrid Infrastructure self-service panel manually, the easiest way is to use the supplied automation scripts:

Tenant-Deploy.yaml
The master template that deploys a set of Microsoft Windows Server VMs for the MSP broker tenant or client tenant. It relies on a set of nested templates listed further.
init-stack.yaml
Deploys the network and router.
ad-create.yaml
Deploys a Microsoft Windows Server VM with a new AD domain controller.
server-deploy.yaml
Deploys a Microsoft Windows Server VM and joins it to the given domain.
lb-create.yaml
Creates a load balancer for port 443.
server-gw-deploy.yaml
Deploys multiple VMs connected to the load balancer.
pause.yaml
Inserts a configurable delay into the provisioning sequence.
last-pa-deploy.yaml
Deploys the second AD DNS controller.
ActiveDirectoryDomainController.ps1
A PowerShell script that runs on the first boot to install Active Directory Domain Services (ADDS).
AD.psm1
A PowerShell module required for the script.
Add-Computer.ps1
A PowerShell script that joins a computer to a domain.
Add-Controller.ps1
A PowerShell script that installs the secondary AD and DNS controller.

In addition, you will need a cloudbase QCOW2 image that all VMs will be created from. You can create one as described in the Virtuozzo Hybrid Infrastructure Administrator’s Guide. This guide uses a Microsoft Windows Server 2019 image Windows-2k19-clb-RAS.qcow2 as an example.