Adding Sysprep Capability to VM Creation Using (Windows) Template
-
Is there a function/feature in XO (I use 'from Sources) to create a new Windows VM from a Windows Template that allows you to create a new SID during the VM creation process similar to what VMware does? In VMW you can run a "customization specification" policy when creating a new VM from Template with various settings -> local admin password, IP assignment, domain name, VM name, run sysprep or create a new SID, windows licensing info. The idea of course is to not have a similar SID for the newly created cloned VM. It would be nice to auto-add it to AD as well like you can with VMware.
If there is no such feature, are there plans to have something like this in a future XO release? Thanks.
-
coolsport00 Hello, I don't know the VMware feature you're talking about.
I would use Packer https://github.com/vatesfr/packer-plugin-xenserver and Cloud Base init https://cloudbase-init.readthedocs.io/en/latest/intro.html to build a Windows VM template. The sysprep would be run at the end of the packer for example using the provisioner powershell or in the
shutdown_commandNB: do not forget to deploy guest tools inside the template.
dinhngtu might have also suggestions
-
nathanael-h Hey...thanks for the response Nathanael. Yeah...the "customization specification" policies is an old VMware feature that's been around pretty much as long as VMware has. To be clear, it's a vCenter feature not an ESXi Host feature.
It's kind of a 'policy wizard' where you configure all those things I mentioned above. It's very convenient!Hmm...maybe someone else can chime in on suggestions. I'd rather not go through the headache of what you suggest if I don't have to...mostly cuz I'm not a developer and don't do github...mostly at all. *shrugs
I'm testing out XCP-NG and XO to see if it's something we can migrate to for our prod VM environment. As of now, it's a "no" mainly because you all don't integrate with Veeam Backup. But, I'm hearing this may be coming... *fingers crossed
