Hi.
We are slowly transfering from 6.5U3 to 7.0U3.
vCenter is running 7.0.3Ua and we have currently 2 VMware hosts with ESXi 7.0.3 in a new cluster.
When trying to create a VM with GuestID relating to Win2019 or Win2022 on the new 7.0.3 Vmware hosts, it fails telling me that :
The guest operating system 'windows2019srv_64Guest' is not supported on the host.
Using PowerCli version 12.3 at the moment.
I can successfully manually create a Win2022 or Win2019 VMguest on the same host.
So what am I doing worng?
Yepp. It doesn't matter. Same error
There are more ESXi nodes in my vCenter
Blog: lucd.info Twitter: @LucD22 Co-author PowerCLI Reference
I was thinking about this script:
$viObjVmHost = Get-VMHost -Name "<EsxiHostName>"
$viewObjEnvBrowser = Get-View -Id (Get-View -Id $viObjVmHost.ExtensionData.Parent).EnvironmentBrowser
$vmxVer = ($viewObjEnvBrowser.QueryConfigOptionDescriptor() | Where-Object {$_.DefaultConfigOption}).Key
$osDesc = $viewObjEnvBrowser.QueryConfigOption($vmxVer,$viObjVmHost.ExtensionData.MoRef).GuestOSDescriptor
$osDesc | Select-Object Id
What do you get from that?
A very long impractical list, hence I added the Where-clause in my updated version.
Btw, you do know that windows2019srvNext_64Guest is for Windows 2022?
Blog: lucd.info Twitter: @LucD22 Co-author PowerCLI Reference
This is what I got from your other script:
But I have created a Win2022 from vSphere. And when I list out the guestID from that server it says like this:
Do you mean that code didn't give any output, meaning Windows 2019 is not listed?
Did you already do some basic problem-solving?
- check that you are connected to 1 vCenter?
- stop/start your PowerShell/PowerCLI session?
Blog: lucd.info Twitter: @LucD22 Co-author PowerCLI Reference
Yes. Sorry :-). Cut the image to short.
I am only conneected to one vCenter.
I've checked from multiple servers with different CLI versions.
I might add that I'm using HPE customized images
Then it looks indeed if that customised ESXi image does not contain the info to create Windows 2019 VMs.
But then it is strange that you apparently can do this from the Web Client.
Perhaps you should ask the same question to someone more familiar with HPE images.
Perhaps your HP TAM or CE?
Blog: lucd.info Twitter: @LucD22 Co-author PowerCLI Reference
Yes.
I currently creating a support case to HPE regarding this matter.
I'll update this thread when I get some feedback/findings from HPE.
This is so strange.
Thank you ALL for input.
Have a nice weekend.
One more thing you could try is to connect directly to one of the ESXi nodes with a GUI, instead of the vCenter.
Check if that allows you to create a Windows 2019 VM.
Blog: lucd.info Twitter: @LucD22 Co-author PowerCLI Reference
That works.
Does anyone know where this GuestID list is located directly on the ESXi hosts?
What kind of files are read? Where?
Are there any other users of HPE Synergy servers who have installed VMware-ESXi-7.0.3-19193900-HPE-703.0.0.10.8.6.3-Jan2022 image, who could be so kind to run this script and check if windows2019srv_64Guest and windows2019srvNext_64Guest are listed.
PS D:\> $viObjVmHost = Get-VMHost -Name $vmhost
$viewObjEnvBrowser = Get-View -Id (Get-View -Id $viObjVmHost.ExtensionData.Parent).EnvironmentBrowser
$vmxVer = ($viewObjEnvBrowser.QueryConfigOptionDescriptor() | Where-Object {$_.DefaultConfigOption}).Key
$osDesc = $viewObjEnvBrowser.QueryConfigOption($vmxVer,$viObjVmHost.ExtensionData.MoRef).GuestOSDescriptor
$osDesc | Select-Object Id
What did HP respond to your support case?
Blog: lucd.info Twitter: @LucD22 Co-author PowerCLI Reference
Hi.
Bad first response "powercli is not supported by break fix support".
So pushing them with more info and through my TAM.
Waiting on them to respond,
Hi.
Just a quick update.
Finally HPE were able to reproduce my problem with a plain VMware image.
So now the problem has been handled over to VMware.
Curious if you ever found a resolution to this? Ran into same problem today. Tried with PowerCLI 13 to no avail.
Hi.
Thanks for the info. Thought I was alone in the world with this issue besides HPE Lab and VMware Lab
.I get a mail from VMwre via HPE twice a month telling:
VMware is still working on the problem.
Hei.
Forgot to update this.
VMware has acknowleded a problem with PowerCLI.
This will be fixed in a future version.
The workaround was to adjust "Edit Default VM Compatibility" to "ESXi 7.0 U2 and later". on the Datacenter og directly on the clustrers.
It was currently set to "ESXi 6.5 and later".