Allow the creation of Service Template Machine Tiers without Sysprep / OOBE
Currently, a Service Template requires Machine Tiers defined by using a VM Template. This VM Template can be preexisting (in the Library) or created in the Service Template Designer.
At deploy-time, VM Templates will always mount an ISO file with an unattend.xml file, containing info like Windows License Key, hostname, IP addresses, etc. The deploy job will sit and wait until the VM is shutdown, which results in the job completing successfully.
Although uncommon, there is sometimes a need to deploy Windows VMs that are not sysprep'd, bypassing the out-of-box-experience (OOBE). An example of this would be in training or virtual lab environments, where you cannot script all customization out. Yes, you run the risk of IP and hostname conflicts, but if you're using SDN, this shouldn't be an issue.
There is currently no way to use Service Templates in this type of requirement (due to the above-described way VM Templates are deployed). If you actually specify a non-sysprep'd VHDX, this process will "work", but the VMM job will wait until it times out. You can manually shut down the VM (from Hyper-V or FCM) and trick VMM into thinking everything finished successfully, but that's obviously not the way to handle this.
I propose allowing for VM Templates to have an option to "bypass" the sysprep/OOBE step. I envision the Configure Operating System tab having this on by default, but perhaps a checkbox somewhere that allows for no configuration to be compiled into the unattend.xml and ISO.
Ernie Costa commented
So it appears that this is 100% doable, just cleverly hidden under the OS PROFILE drop-down menu.
When creating a new VM Template (whether from an existing VM or VHDX), when you get to the Configure Operating System tab, click the drop-down for:
[None - customization not required]