https://github.com/rgl/windows-sysprep-playground
A Windows sysprep playground
https://github.com/rgl/windows-sysprep-playground
packer sysprep terraform windows
Last synced: 7 months ago
JSON representation
A Windows sysprep playground
- Host: GitHub
- URL: https://github.com/rgl/windows-sysprep-playground
- Owner: rgl
- Created: 2024-12-18T08:31:44.000Z (over 1 year ago)
- Default Branch: main
- Last Pushed: 2024-12-18T19:44:06.000Z (over 1 year ago)
- Last Synced: 2024-12-31T11:06:21.727Z (about 1 year ago)
- Topics: packer, sysprep, terraform, windows
- Language: PowerShell
- Homepage:
- Size: 14.6 KB
- Stars: 0
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# About
This is a Windows sysprep playground.
This will:
* Clone one of the following Proxmox template images:
* `template-windows-11-24h2-uefi`.
* `template-windows-2022-uefi`.
* `template-windows-2025-uefi`.
* Install Handle.
* Install Chocolatey.
* Generalize (Sysprep) the machine 3x (because the third time is the charm).
* 3x to test whether we can run sysprep several times.
* The last one leaves the template image in a generalized state.
* Windows 11 makes this harder than required, as it no longer let us seed the
OOBE user, instead, as a workaround, we have to use auto-logon.
* Sysprep also needs a little nudge to the installed appx packages before
it can be executed.
* Do all of this without Internet access.
* To test whether it can be done in offline mode.
* Create the `template-windows-sysprep-playground` Proxmox template image.
* Use terraform to try the created template image.
* The template image is in a generalized state.
# Usage
Create one of the Proxmox template images by following the instructions at the [rgl/windows-vagrant repository](https://gitgub.com/rgl/windows-vagrant).
Set your proxmox details:
```bash
# see https://registry.terraform.io/providers/bpg/proxmox/latest/docs#argument-reference
# see https://github.com/bpg/terraform-provider-proxmox/blob/v0.79.0/proxmoxtf/provider/provider.go#L52-L61
cat >secrets-proxmox.sh <<'EOF'
unset HTTPS_PROXY
#export HTTPS_PROXY='http://localhost:8080'
export PROXMOX_USERNAME='root@pam'
export PROXMOX_PASSWORD='vagrant'
export PROXMOX_NODE='pve'
export PROXMOX_NODE_ADDRESS='192.168.1.21'
export PROXMOX_URL="https://$PROXMOX_NODE_ADDRESS:8006/api2/json"
export TF_VAR_proxmox_pve_node_name="$PROXMOX_NODE"
export TF_VAR_proxmox_pve_node_address="$PROXMOX_NODE_ADDRESS"
export PROXMOX_VE_INSECURE='1'
export PROXMOX_VE_ENDPOINT="$PROXMOX_URL"
export PROXMOX_VE_USERNAME="$PROXMOX_USERNAME"
export PROXMOX_VE_PASSWORD="$PROXMOX_PASSWORD"
EOF
source secrets-proxmox.sh
```
Create the template:
```bash
# NB use the same file that was created as described in the
# rgl/windows-vagrant repository.
source secrets-proxmox.sh
CHECKPOINT_DISABLE=1 PACKER_LOG=1 PACKER_LOG_PATH=packer-init.log \
packer init .
CHECKPOINT_DISABLE=1 PACKER_LOG=1 PACKER_LOG_PATH=packer-build.log \
packer build \
-on-error=abort \
-var source_template=template-windows-11-24h2-uefi \
.
```
Try the template, using terraform:
```bash
pushd example-terraform
export CHECKPOINT_DISABLE='1'
export TF_LOG='DEBUG' # TRACE, DEBUG, INFO, WARN or ERROR.
export TF_LOG_PATH='terraform.log'
terraform init
terraform plan -out=tfplan
time terraform apply tfplan
```
Login into the machine using SSH:
```bash
ssh-keygen -f ~/.ssh/known_hosts -R "$(terraform output --raw ip)"
ssh "vagrant@$(terraform output --raw ip)"
whoami /all
pwsh -Command "Disable-NetFirewallRule PROVISION-BLOCK-INTERNET-Out"
ping google.com
exit # ssh
```
Login into the machine using PowerShell Remoting over SSH:
```bash
pwsh
Enter-PSSession -HostName "vagrant@$(terraform output --raw ip)"
$PSVersionTable
whoami /all
Disable-NetFirewallRule PROVISION-BLOCK-INTERNET-Out
ping google.com
exit # Enter-PSSession
exit # pwsh
```
Destroy the example:
```bash
time terraform destroy -auto-approve
popd
```
Login into your Proxmox and delete the created `template-windows-sysprep-playground` template image.