I was in the process of adding the newly released Windows Server 2016 to my lab repository and normally just creating a new Virtual Machine, mount ISO, install, next, next etc. then convert to template and finally being mass-deployment while executing the post-deployment customisation wizard I encountered this annoying error:
Customization of the guest operating system
‘windows9Server64Guest’ is not supported in
this configuration. Microsoft Vista (TM) and
Linux guests with Logical Volume Manager are
supported only for recent ESX host and
VMware Tools versions. Refer to vCenter
documentation for supported configurations.
The Windows version which I was attempting to post-deployment customize (with an already proved and tested customisation script) is:
PS C:\Users\asecor> [System.Environment]::OSVersion.Version Major Minor Build Revision ----- ----- ----- -------- 10 0 14393 0
Strangely for TP5 this wasn’t a problem and my vSphere ESXi 6.0 3620759 environment didn’t change – I know its a little out of date with the patching but that shouldn’t make a difference.
So how did I fix it – well as the customisation script relies on VMware Tools (and it is also mentioned in the error) my hunch was to see if there was a newer version of VMware Tools from the one which was getting pushed out – and I came across thisVMware Tools Operating System Specific Packages Repository –
Windows x64 –https://packages.vmware.com/tools/releases/latest/windows/x64/index.html
Windows x32 – https://packages.vmware.com/tools/releases/latest/windows/x86/index.html
But the new-vm command is run on a template and the installation of vmtools will be later.
What should I do with the newer vmtools. Or should I put it into the template?
Great info. Thanks.
This was extremely helpful! Thanks so much!
Resolved the issue, thanks!