Ease of identification of which bridge it uses, which client and/or which IP network - some of us does have OCDEasiest, safest way it to clone to a new number or to backup and restore to a new number. But really what does the number matter anyway.
I guess its good that you are not using OpenstackEase of identification of which bridge it uses, which client and/or which IP network - some of us does have OCD
I guess its good that you are not using Openstack
Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
there is not a single horse in that barn..Openstack is much beterer in the mass chicken world. In my world there are cows and alpacas and dogs and the cat or two. And OpenStack just doesn't handle that as nicely, while ProxMox I see will falter when you do need those loads of chickens in multiple breeding/laying halls.
Going off topic: Those horses know to stay away from IT/computers and are running around freely.... do my 35+ years in this industry show?there is not a single horse in that barn..
Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
I ran a backup on VMID=5000, restored it, and checked the applications and licensing—everything is functioning as expected, with the license status showing as "Licensed." Afterward, I deleted VMID=200.Name: Windows(R), Professional edition
Description: Windows(R) Operating System, VOLUME_MAK channel
Partial Product Key: "......."
License Status: Licensed
Since you also performed a backup/restore operation (although only as a check), it would have been easier to save VM 200 and restore it as VM 5000.For those wanting to change the VMID of a Windows 11 Pro VM while keeping the "digital license linked to your Microsoft Account," here's what worked for me (even though it might seem unnecessary, I wanted to try it, so I did):
- Fully Backed Up VMID 200: Before making any changes, I made sure VMID 200 was fully backed up.
- Shut Down the Old VM: My original VMID was 200, and I wanted to change it to 5000.
- Copy and Edit Configuration:
- Copied /etc/pve/qemu-server/200.conf to 5000.conf.
- Edited 5000.conf to replace all instances of "200" with "5000."
- Handle VM Disk Images:
- My Proxmox disk images are stored on a file server and served to Proxmox VE over NFS.
- I created a new directory on my file server: mkdir -p /mnt/sp/images/5000/.
- Copied the VM disk: cp -R /mnt/sp/images/200/* /mnt/sp/images/5000/.
- Renamed all occurrences of "200" in the file names to "5000" using mv.
- Boot and Verify:
- Booted up VMID 5000.
- I ran slmgr /dli from an elevated command prompt and confirmed that the digital license was retained. The output showed:
I ran a backup on VMID=5000, restored it, and checked the applications and licensing—everything is functioning as expected, with the license status showing as "Licensed." Afterward, I deleted VMID=200.
I don’t see why this approach wouldn’t work for any OS.