Sysprep on Windows Packer Builds

[erikspigle-payroc]

Is there a compelling reason why the shutdown command for Windows server builds does not finalize with a sysprep generalize step to make the built image ready for cloning out? Typical template / gold image creation with a customized Windows VM usually ends with a sysprep generalize step. I haven't found a lot about finalizing the packer process using sysprep. I did find this, and am testing it, but I did want to inquire why nothing was included with this project for using sysprep with Windows. Here is what little I have found:

https://discuss.hashicorp.com/t/is-it-fair-to-sysprep-in-shutdown-mode-through-packer/52582

[tenthirtyam]

VMware Tools and vCenter Server abstract the use of Sysprep, making it a seamless part of the guest OS customization process.

When you create a customization specification and apply it during VM deployment, VMware Tools takes care of using Sysprep in the background to apply the specified customizations to the VM.

This integration simplifies the deployment process and allows for easy, automated customization of guest operating systems without the need for calling Sysprep in the build.

But you can of course add it to the shutdown command if you wish.

[erikspigle-payroc]

Thanks for the response. That may be part of the problem on our end in that we don't typically use VM Customizations Specifications. Sounds like a good case to do-so.