Introduction

HyperVLab uses both convention and configuration.

There is a folder-structure that HyperVLab uses to find the necessary files. The main structure consists of the HyperVLab root-folder, a Labs-folder and a lab-folder for each lab. When applicable, files are taken from the lab-specific folder first, then from the Labs-folder, then the HyperVLab root-folder, and finally using default files from the HyperVLab module itself.

Each lab has a configuration file which describes the machines in the lab. This configuration contains details about the VM's, the OS-image, the domain they are part of, and their role(s). An OS-image is a sysprepped vhdx, which can be created in several ways.

When creating a VM, HyperVLab injects files into the virtual harddisk so it runs through the setup unattended, does some basic configuration and applies the machine-specific (role) configuration.

The basic-configuration is always injected. The machine-specific configuration can be injected, or provided from an external source, like Chocolatey/PowerShellGet package sources or a PowerShell DSC Pull-server.