So I can configure a VM, turn it into a template, put in computer name, domain join info and all that Guest OS stuff and it's good to go... for generating one single VM.
If I try to generate a second VM from the template it now has the exact same name, so will not domain join, and when creating the VM the Guest OS configuration option does not appear. Those Guest OS settings do not appear even when I right click on the template and go to properties.
Of course I could leave the computer name as "*" when configuring the template for the first time, but that means I have to go in and manually rename the machine in windows after it is generated to give it a proper computer name that matches our naming conventions, which is just as much work as generating a VM that does not domain join, and then manually domain joining it after the fact.
I just know someone is going to say "use an unattended.xml file" but that file is set in the very Guest OS settings that are not accessible after template creation, and even then would require editing that XML every time I wanted to make a new VM.
So there are two issues here as far as I can see-
1. You can't get to Guest OS settings after the template is first configured, essentially requiring you to generate a new template every time you want to change a setting, or have a VM with a new computer name.
2. There is no method of assigning a computer name to the VM generated from a template except through the Guest OS settings.
I've got to be missing something here, I can't imagine that VMM can't manage generating more than one properly named VM per template.
Thanks for the help.
