Good morning,
I recently created a VM and set everything up in it to make the new all inclusive template with all fixes and latest patches and so. I managed to create the vm and configured everything, then I cloned it and turned the clone into a template so I can create more VMs like it.
Yet upon testing it out and creating a VM from the template, even though I gave it a new name, it seems that (the new vm) is still using the same DNS name as the original template vm, and I noticed that the IP is the same aswell.
Clearly I did something wrong or I skipped a step but I am not sure exactly what it is that I missed. My goal is to basically be able to start new vms from the template but be their own device, their own dns name to rdp into it and new IP, so that way I can give it to any new user that joins.
Anyone familiar with this issue?
What Guest OS for the VM are you using?
Windows 10 x64
Easiest way to sort this out is using customization specification, here the link to the VMware documentation
It sounds like you didn't sysprep the Windows vm before you turned it into a template?
When you run Sysprep, it folds your Window box down into a new image (MS call it the OOB (out of box) experience). This will then mean that when you boot up a new VM from the template, you'll be able to rename it, change its IP etc etc. It will also reset the GUID of the machine which is the most important thing. You can't have more than one Window machine on a network with the same GUID/UID, it will cause issues.
