Hello Andrew,
There are 3 stages in MaaS:
- initial discovery
- commissioning (hardware detection)
- Start (actual commissioning/install)
The initial discovery will detect any newly booted system on the network that booted via ethernet.
The commissioning stage is where the system boots a minimal ubuntu image, installs a set of tools and discovers the hardware of the system. After commissioning a machine, it will be in "Ready" state, at which point you can edit the node, set the OS and key, simply click on "Start" in the node screen.
Do not click on "commission" again. Click on "Start". This will start the machine (if you have a power adepter configured) and run the windows installer.
The reason why you only have the INSTALL image for windows in the cluster boot images, is that we only need INSTALL to set up windows. The first 2 steps can be done with the existing ubuntu images.
This also might be a naming issue between what the automated scripts generate, and what maas expects to find. Try the following:
mv /var/lib/maas/samba/ws2012r2std /var/lib/maas/samba/win2012r2
mkdir -p /var/lib/maas/boot-resources/current/windows/amd64/generic/win2012r2/release/
rm /var/lib/maas/boot-resources/current/windows/amd64/generic/win2012r2/release/*
for i in `ls /var/lib/maas/samba/win2012r2/boot/`; do ln -s /var/lib/maas/samba/win2012r2/boot/$i /var/lib/maas/boot-resources/current/windows/amd64/generic/win2012r2/release/$i;done
