1. Enable the two following settings in Operations Manager (Ops Manager):
Keep Unreachable Director VMs"enable BOSH-native SSH support on all VMs"
2. Open two different BOSH CLI terminals and open the IaaS GUI. Click "Apply Changes" in Ops manager.
3. Monitor the BOSH task running after clicking "Apply Changes" against the TASW tile and keep an eye out for the compilation VM CID to come up. On the first BOSH CLI terminal, run this command:
watch -n 5 "bosh -d <pas-windows-deployment> is --details | grep compilation"
4. Once the Windows compilation VM CID comes up, SSH to the Windows compilation VM on the second BOSH CLI terminal:
bosh -d <pas-windows-deployment> ssh <compilation_name>
Note: Leave open this SSH session as you may not be able to SSH anymore after the BOSH task fails.
5. Search for the compilation VM CID in the IaaS GUI in order to protect the Windows compilation VM from deletion:
On AWS environment:
Actions buttonInstance SettingsChange Termination ProtectionYes, EnableOn GCP environment:
Edit buttonEnable deletion protection checkboxSave at the bottomOn Azure environment:
Locks in the left-side menuAdd DeleteOKOn vSphere environment:
How to boot the Windows compilation VM with Ubuntu desktop ISO on vSphere
In a scenario where you have got the Windows compilation VM alive or working in vSphere but don't have any SSH session opened, you can use the following method:
Connect at Power ON"Boot Delay to 10000 milliseconds and select Force BIOS Setuptry Ubuntu" and launch a terminal. Open a terminal and run the following commands:sudo fdisk -l sudo mkdir /mnt/windows sudo mount /dev/sda1 /mnt/windows
/mnt/windows