Debugging & KB

Following Windows install progress

When the install get started, open the VM in remote console, grab some popcorn, and watch the install go. The VM will shut down when everything is finished. There is no need for any interaction during the install process - just watch.

Windows install hangs

Log in to VSphere and open the VM in remote console. You should be greeted with a window describing why the install couldn't finish. Microsoft has published a helpful troubleshooting guide to help debug automated installs. Of note, is the Setupact.log files. Located at %windir%\panther and %windir%\panther\unattendGC within the base-vm.

What about a product license?

Windows and product licenses are like PB&J. They always go together. There are definatly provisions in the unattend file for just such a thing. This project makes the assumption that the resulting stemcell image will be deployed on Cloud Foundry for Windows, which already has the ability to provide licenses or key management servers. You can extend the provided xml template and add in things like this, as needed.

Why is the iso file hardcoded in pipeline yaml?

It is assumed you will have multiple iso's. So as to not get things mixed up, the pipeline has hardcoded this.