How to deploy multiple Windows VMs using a template and we have the customization file in VMware which runs the sysprep and hostname automatically changes according to the VM Name, can you explain the process of customization of multiple Windows vms in proxmox???
Deploy multiple Windows VMs using a template and auto customization (sysprep) of VMs
- Thread starter Punith Kumar B
- Start date
https://pve.proxmox.com/wiki/VM_Templates_and_Clones
You can keep it
This will be tricky, IDK if qemu agent running in VM can retrieve VM name.
What about, exactly ?
Microsoft Windows has its own (officially supported) technique for customization: https://learn.microsoft.com/en-us/w...eate-your-own-answer-file-sxs?view=windows-11
I believe you can supply the answer file via virtual disk and virtual cdrom.
The other option is https://cloudbase.it/cloudbase-init/
Finally, you can write batch/powershell files that will be executed on start.
https://learn.microsoft.com/en-us/windows/deployment/windows-deployment-scenarios-and-tools
Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
I believe you can supply the answer file via virtual disk and virtual cdrom.
The other option is https://cloudbase.it/cloudbase-init/
Finally, you can write batch/powershell files that will be executed on start.
https://learn.microsoft.com/en-us/windows/deployment/windows-deployment-scenarios-and-tools
Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
Customization means the cloned Windows VMs hostname automatically changing when deployed from a Windows template. Any such option in proxmox, if yes how to use that option.
Last edited:
There are a few options:
a) Use Cloud Init in combination with CloudBase
b) Use Cloud Init in combination with external Metadata server
c) Use automatically generated Answer file that retrieves VM name during generation
PVE is based on a toolset developed for Linux. The primary cloud customization tool in Linux is Cloud Init. Windows does not support Cloud Init natively. Hence, you either need to use the widely used CloudBase implementation, or develop your own custom procedure.
Cheers
Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
That's seems the OP request.
I don't think qemu agent can retrieve name set in PVE natively.
I never suggested using Qemu Agent. The Agent communication is one-way by design. The hypervisor can retrieve data from the agent. The agent cannot retrieve data from hypervisor.
Generating Cloud Init or Answer file would be done in the template prep stage when there are multiple ways to find out the VM name from the hypervisor. The configuration file is then supplied to the VM for boot time customization.
Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
can you provide any detailed explanation on these points or any youtube/web link that provides detailed explanation. It will be helpful for me.
Hi @Punith Kumar B ,
Deploying templated Windows environments isn't something we regularly work with at Blockbridge. I’d have to do the same research as you to provide links, I’d recommend looking into relevant documentation or consulting with a specialist for tailored guidance.
Cheers
Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox