This repository holds the build scripts for the Reskit.org domain. I use this domain and the VMs in my books, speaking, and training. These scripts are not a fully baked automation solution but allows you to create just the VMs you need In advanced PowerShell class, students run and then dissect these scripts
These scripts work for me, in my environment and on my systems. I make no promises other than they should work if you are careful. I have used variables widely to hold the names of things that DO vary (e.g. ISO file names, output folders, etc). PLEASE review before using.
These scripts are a work in progress.
I am constantly updating them - so beware!
If you find issues, please file an issue on GitHub.
New-ReferenceVHDX.ps1- creates a reference disk containing WIndows Server 2022 installation mediaNew-RKVM.ps1- copies the reference disk and creates a new VM using unattended XML to customise and automate the installation (of the VM)Update-RKVM.ps1- after installation, this script adds a 2nd NIC bound to external and improves hardware. This is one way to give the VM internet access.- Readme.md - this document which sets out how to build the reskit forest
The scripts create a set of Hyper-V VMs that might make up a corporate data centre. The VMs are used as the basis for the scripts in my PowerShell books and my training classes. The VMs includes domain controllers, DNS/DHCP servers, plus a whole lot more. The scripts create the base VMs and reconfigure them.
Note these scripts and the book/class content use hard coded IP addresses in the 10.10.10/24 range. You can see the IP addresses used in the ReskitNetwork.md document. If you want to change the IP addresses, be aware that each chapter or course module assumes a specific set of IP addresses. If you change them, be very careful - or enjoy IP address troubleshooting. As a rule, I do not support using different IP addresses for the VMs. I am happy to offer best-effort support if you set stuck.
For classroom use, you create VMs then use the classroom scripts folder to configure the VMs.
For book use, you create VMs as you need them.
You first create a master VHDX, using New-ReferenceDisk.
This script creates a VHDX, and uses DISM to copy the installation media for Windows Server onto the VHDX.
This step creates what I call the reference VHDX.
To create each VM, you use New-RKVM.ps1. This script makes a VM specific copy of the reference VHDX, copies a XML setup file onto the copied VHDX, then creates and starts a VM based on this new VHDX.
The script then starts the VM and exits.
When Hyper-V starts the VM, it boots to the Windows setup which runs using the unattended XML.
The end result is a VM of the appropriate name, IP address, and with a default Administrator password (Pa$$w0rd).
The XML files supplied here do NOT have a license key embedded, but if you have the key, you can edit the XML files accordingly.
To develop the gooks, I use an MSDN license key and media.
If you embed a valid license key in the XML, once Windows Setup completes, you have a VM you can login to.
If you do not update the XML, Windows Setup completes with a final window for you to either enter a valid key or just continue.
All the VMs for both book and classroom use use the same password: Pa$$w0rd.
This is not a great password for real world use, but it it is simple and consistent.
For your use as a reader or class participant, this is more than adequate.
But you can update the XML files to choose any password you wish.
The scripts that use Windows credentials use the password so be careful if you decide to cyage things.
This is a pretty straightforward process. Please take a moment to read the rest of this document before diving in to create VMs!
You start by creating your VM host. You want either Server 20XX or Windows 10/11 Enterprise/Pro. To run the full set of VMs requires a fair bit of RAM - I suggest a minimum of 32GB. The latest book was developed using a large Windows 11 workstation with 128GB of RAM. As an alternative, you can reduce the virtual memory for each vm to say 1gb and run most of the VMs at the same time. In that case, startup will be slow (and noisy if you have spinning disks). But once the VMs are up and running, performance should be OK.
After creating your VM host, ensure the host has Hyper-V feature added and that you have virtualization and SLAT enabled in the BIOS.
On your VM host, create a D:\V9 as the location for the VMs.
You can change this folder name and drive - but if you do so, update the variables used to hold this folder name in the New-ReferenceVHDX.ps1 and New-RKVM.ps1 scripts.
Next copy the two unattended XML files \unattended XML\Unattend.xml* and \unattended XML\UnAttend.DJ.xml into D:\v9 on the VM host. The setup scripts use these XML files to build a Windows Server somewhat pre-configured (eg with credentials, machine name, IP address, administrator password etc. all pre-assigned). All the values (domain name, administrator password) are easy to change. As noted above, these XML files do NOT contain a key. To simplify the creation of VMs, you can edit the XML files and add your Server 2022 Enterprise activation key.
The first step is for you to use New-ReferenceVHDX.ps1 to create a reference VHDX. This script requires the ISO image of Windows Server 20XX DataCentre and outputs the reference VHDX you use later. Some ISO images you get contain multiple configurations (Standard, Data Center) depending on the source. This script lets you pick which version to use - make sure you pick Data Center with the Desktop! The VHDX you create is essentially a copy of Windows server installation media copied from the ISO image.
Before running this script, ensure paths are correct and point the ISO image and where you want to store the reference disk.
Depending on which book you are reading, the VM in the first chapter will vary:
. For my 1st two Packt books, and my Wiley Book, create DC1 first. . For my Packt PowerShell 7 books, create SRV1 first
I urge you to read the relevant chapter before creating each VM.
You use the New-RKVM.ps1 script to create your first VM.
Since a goal of the book is to build out a network, you start with a workgroup server (in later chapters, new VMs are built as domain joined)..
At the top of the New-RKVMscript you can see a function that creates a VM.
At the bottom, you see a number of invocations of that function which individually create the relevant domain joined or non-domain joined servers.
I left these invocations in the script to enable you to create VMs with the right IP addresses quickly and easily.
In the GitHub repo you should see all the calls to the function commented out. Since this repo is a work in progress, you may find that some calls are NOT commented out. So before running the script for the first time make sure all calls to the function are commented out. If you run it this way, you can see that the function compiles OK, even with no VMs actually created. Once this works, you can un-comment the call to create each VM and re-run the entire script to create the VM.
Each VM you create spins up and goes through the installation process. At the end of the process, you have a working VM.
After starting the VM, it can take 10-15 minutes for Windows to build your VM. This of course depends highly on the hardware specification of your VM host.
There are likely to be numerous ISO images you can download from Microsoft for Windows Server. Depending on the specific version of Windows Server you use, you have different license keys. Enter your key when directed or consider editing the XML to contain the key. For evaluation, you can direct setup to ignore and just move on (but the VM times out after 180 days) Unlicensed VMs do time out, but you can always rebuild them.
Once the first VM is up, it runs as an server in the Reskit work group. Login as local Administrator and ensure the VM is created properly and check the IP address for the NICs in the VM.
In general, the early parts of the books use a single workgroup server for the first few chapters. Then you create your first DC. From that point you can create the other domain-joined VMs.
Once you have the first DC created, you can create the other servers. Use the New-RKVM.ps1 script to create each server. You uncomment the relevant line and re-run the script. Be careful to specify the correct unattended XML file when you create the VM.
The scripts in the repo have been used extensively in author testing and writing. The scripts were designed to be used in a classroom, for use in examining PowerShell code, and as part of a book project. But be clear: This is a work in permanent progress. If you have problems, file an issue in this repo and I will help.
Enjoy!