So we've had multiple issues in the past with master images that were joined with the domain. Going back and forth in snapshots can skew the trust relationship between the machine and the domain. The customization that is done during deployment is essentially the VM being prepared for use i.e. changing the VM name to whatever you configured the pool for, joining the domain etc.

When you boot up the master image for changes, you should always run OSOT to revert possible changes to the registry that are not desired to go into the new image and prepare the master for deployment. There is a powerful script framework that helps with image generalization before deployment. You should look up Base Image Script Framework (BIS-F) for this. Just google BIS-F and the first result should be it. This tool lets you run all manner of scripts when shutting down the master. We've configured ours to delete the admin profile and clean up event logs for better overview. It can also use OSOT templates to make sure that unintentional changes in the registry get ported into the snapshot. Since we started using this we were able to get a very consistent master image.

Best regards,

Raetke