Windows Server 2022 ESXi 7 Tools Upgrade

[MFuchs]

Hello,

we cannot upgrade the vmware tools anymore if we select Windows Server 2022 as Guest OS. If we try to scan Entity we get "Operating System not supported" - Status is Unknown.

Used Versions: VCSA 7.0.3d, ESXi 7.0.3d (same with previous VCSA/ESXi 7.x versions)

If we switch back to WS19 we can scan again and do upgrade. Strange behaviour. Has anyone else got this issue?

Same with e.g. FreeBSD13.

Entry in Log file on VCSA /var/log/vmware/vmware-updatemgr/vum-server/vmware-vum-server.log

2022-04-05T16:41:38.097+02:00 error vmware-vum-server[25561] [Originator@6876 sub=vmOpsUtils] [vmOpsUtils 561] Action (SCAN) skipped for VM: ***BLACKED**. The guest OS Microsoft Windows Server 2022 (64-bit) is not supported

Any tips would be helpful.

Mario Fuchs

[andrew_uk]

Hi,

I also am seeing the same, switching to 2019 it scans no problem. Through PowerCLI it shows me the information no problem. 

Did you find the issue? 

I wonder if it is related to VMware tools and VM Hardware Compatibility is reported incorrectly in the Updates tab of the VM in vCenter (87173)

[MFuchs]

Cool. Great - your hint worked.

Greetings,

Mario Fuchs

[paules1]

hola como pudiste instalar windows server 2022 en VMware fusion

 

[MFuchs]

Cool. Great - your hint worked.

Greetings,

Mario Fuchs

[andrew_uk]

Did you change the Guest OS version to 2019 or did you follow the steps in that article? 

[MFuchs]

Hi,

i followed the steps in the article and changed vciintegrity.xml.

Mario

[Schaetzle]

I have the same problem and wanted to look at the linked article, but it seems to have been removed in the meantime (Page not found).
Is there a newer article here? Unfortunately I could not find anything on VMware.

[andrew_uk]

I believe this is the new article:

 

Scan of Windows Server 2022 Virtual Machine for updates fails with "Scan or remediation is not supported on <VM Name> because of unsupported OS Microsoft Windows Server 2022 (64 bit) (87660) (vmware.com)

[Schaetzle]

Many Thanks!

But if I add the lines as indicated in the instructions.
<supportedWindowsGuestIds>
< windows2022srvNext_64Guest/>
</supportedWindowsGuestIds>
above </vci_vcIntegrity> the restart of the update manager fails.

The following error message appears:

"Restart service request failed. Error: Service crashed while starting"

I have already checked the spelling with several times, experimented with the spaces - all without success.

If I undo all changes the service starts without problems.

What am I doing wrong?

[andrew_uk]

We used <windows2019srvNext_64Guest /> instead, seems to work with that.

[Schaetzle]

Strange
With me the service always crashes on restart.

I attach a screenshot with an excerpt of the vci-intgrity.xml here - maybe we are talking past each other.

[andrew_uk]

Seems to be the same as ours apart from one of the spacing, attached screenshot.

[andrew_uk]

It needs to be below <vci-vcintegrity> 

[Schaetzle]

Sorry - just saw through the answer that I had inserted it in the wrong place.
Then that can be nothing. In the right place it works (but interestingly only with the entry for Server2019 and not with the entry for Server 2022).

Then the screenshot helped after all

Many thanks for the support.

[esctodd]

I'm setting up a Server 2022 template, and came across this thread when researching why the VMware tools checks for Server 2022 didn't work.  I had no issues with Server 2019. 

The KB that andrew_uk linked was helpful, but discussion that followed also pointed to some issues with the KB.

• The Updatemgr service doesn't like the leading space in < windows2022srvNext_64Guest/>. 
• It still doesn't check for updates if I use the 2022 commands as listed, but works with the 2019 commands
• The section talking about the text to enter for Server 2022 mistakenly labels it as "For windows server 2025."

 

 

[JLX]

Totally agree with esctodd.

About the mentionned KB:
2022 section in the KB didn't solve anything and doesn't help.
2019 section in the KB is working.

We have several VC in v 7.0.3.00800 (7.0.3g) and they all have the same behaviour mentionned above.

 

[ClementPi]

thanks you perfect for windows 2022

Just add 

<supportedWindowsGuestIds>
  <windows2019srvNext_64Guest/>
</supportedWindowsGuestIds>

after reload update manager, wait for vcenter sync configuration and. Start again a check status onW2022 Vm.

Problem resolved

[Maks Roshchyna]

good to know that issue was solved