unsupported OS for certain operating systems (87660)

[scottmackenzie]

unsupported OS for certain operating systems (87660)

https://kb.vmware.com/s/article/87660 

The above article is supposed to address a workaround for:

"Scanning a VM for potential Updates of VMware Tools or its VM Hardware Version using vSphere Client fails with "Scan or remediation is not supported on because of unsupported OS ..." for certain operating systems (87660)"

The workaround does not work.  Any ideas?

Below is Pre-Change

    <vci_vcIntegrity>
      <EsxTaskMax>10</EsxTaskMax>
      <LocalTaskMax>10</LocalTaskMax>
      <MaxHostsForParallelRemediation>96</MaxHostsForParallelRemediation>
      <checkVsanHealthStatus>true</checkVsanHealthStatus>
      <downloadAfterInstallation>true</downloadAfterInstallation>
      <encryptGuestInfo>true</encryptGuestInfo>
      <guestRebootTimeout>900</guestRebootTimeout>
      <guestShutdownTimeoutMinutes>10</guestShutdownTimeoutMinutes>
      <path>../lib/libvci-vcIntegrity.so</path>
      <toolsUpgradeTimeoutSec>1800</toolsUpgradeTimeoutSec>
      <toolsWaitTimeoutSec>600</toolsWaitTimeoutSec>
      <vimNameSpace>vim.version.stable</vimNameSpace>
      <vpxdLocation>http://vcsa1.mackenzie.bio:80/</vpxdLocation>
      <vpxdThumbprint>00:14:AD:AF:DB:B0:36:15:29:25:6E:53:C6:E4:E4:CD:F0:8E:41:85</vpxdThumbprint>
    </vci_vcIntegrity>

Post Change (Version 1)

    <vci_vcIntegrity>
      <EsxTaskMax>10</EsxTaskMax>
      <LocalTaskMax>10</LocalTaskMax>
      <MaxHostsForParallelRemediation>96</MaxHostsForParallelRemediation>
      <checkVsanHealthStatus>true</checkVsanHealthStatus>
      <downloadAfterInstallation>true</downloadAfterInstallation>
      <encryptGuestInfo>true</encryptGuestInfo>
      <guestRebootTimeout>900</guestRebootTimeout>
      <guestShutdownTimeoutMinutes>10</guestShutdownTimeoutMinutes>
      <path>../lib/libvci-vcIntegrity.so</path>
      <toolsUpgradeTimeoutSec>1800</toolsUpgradeTimeoutSec>
      <toolsWaitTimeoutSec>600</toolsWaitTimeoutSec>
      <vimNameSpace>vim.version.stable</vimNameSpace>
      <vpxdLocation>http://vcsa1.mackenzie.bio:80/</vpxdLocation>
      <vpxdThumbprint>00:14:AD:AF:DB:B0:36:15:29:25:6E:53:C6:E4:E4:CD:F0:8E:41:85</vpxdThumbprint>
      <supportedWindowsGuestIds>
        <windows2019srv_64Guest/>
      </supportedWindowsGuestIds>
      <supportedWindowsGuestIds>
        <windows2019srvNext_64Guest/>
      </supportedWindowsGuestIds>
    </vci_vcIntegrity>

Post Change (Version 2)

    <vci_vcIntegrity>
      <supportedWindowsGuestIds>windows2019srv_64Guest</supportedWindowsGuestIds>
     <supportedWindowsGuestIds>windows2019srvNext_64Guest</supportedWindowsGuestIds>
      <EsxTaskMax>10</EsxTaskMax>
      <LocalTaskMax>10</LocalTaskMax>
      <MaxHostsForParallelRemediation>96</MaxHostsForParallelRemediation>
      <checkVsanHealthStatus>true</checkVsanHealthStatus>
      <downloadAfterInstallation>true</downloadAfterInstallation>
      <encryptGuestInfo>true</encryptGuestInfo>
      <guestRebootTimeout>900</guestRebootTimeout>
      <guestShutdownTimeoutMinutes>10</guestShutdownTimeoutMinutes>
      <path>../lib/libvci-vcIntegrity.so</path>
      <toolsUpgradeTimeoutSec>1800</toolsUpgradeTimeoutSec>
      <toolsWaitTimeoutSec>600</toolsWaitTimeoutSec>
      <vimNameSpace>vim.version.stable</vimNameSpace>
      <vpxdLocation>http://vcsa1.mackenzie.bio:80/</vpxdLocation>
      <vpxdThumbprint>00:14:AD:AF:DB:B0:36:15:29:25:6E:53:C6:E4:E4:CD:F0:8E:41:85</vpxdThumbprint>
    </vci_vcIntegrity>

Post changes the restart daemon error:

root@vcsa1 [ ~ ]# vmon-cli -r updatemgr
Restart service request failed. Error: Service crashed while starting

 

 

 

 

 

 

 

[Maksym Roshchyna]

What is you vCenter and ESXi versions?

[scottmackenzie]

Hypervisor: VMware ESXi, 7.0.3, 20842708

with vCenter Version: 7.0.3 Build: 20990077

Host Security Patches (Predefined) Compliant

Critical Host Patches (Predefined) Compliant

Non-Critical Host Patches (Predefined) Compliant

vSAN Cluster 'CL1' Compliant

 

*everything is "up to date" and in a patched and compliant state.  100% clean and green (no errors) only this one error pertaining to Windows 2022 Servers and the article not working to resolve the error.

[Maksym Roshchyna]

Have you tried to restart all vCenter not only services.

[scottmackenzie]

Are you referencing "restarting" post the configuration change?  Or in general to try and remove the error?

After applying the change to the config, no.  Since the restart of the service (daemon) crashes the binary I don't suspect a reboot of the vcenter will result in success.  Has this worked for you?

In general, yes.  Hundreds of reboots (it's a lab).

 

 

[Maksym Roshchyna]

I like this comment in VMware KB: 

VMware is aware of this issue and working to resolve this in a future release.

[scottmackenzie]

>VMware is aware of this issue and working to resolve this in a future release.

Yes, I thought the same thing.  (odd and frustrating) 

In 2 days it is 2023 and the issue has been unresolved since Windows 2019 Server.

https://kb.vmware.com/s/article/87660

And what I find quite frustrating is that the "workaround" does not work.  I would be happy with a workaround that fixes the issue but my real preference is support for 2019 and 2022 for patch and hardware compliance (which is critical for security). If you take security seriously...

 

[Maksym Roshchyna]

Is it possible to reset only VUM, not the entire vCenter? 

Definitely something is wrong there 

[scottmackenzie]

Yes.  See original post.

Post changes the restart daemon error:

root@vcsa1 [ ~ ]# vmon-cli -r updatemgr
Restart service request failed. Error: Service crashed while starting

 

 

[Koboe]

Hi

Had this too, Bundled both and it didn't crash. Kept seeing Win22 as Win19.

1. <supportedWindowsGuestIds>
     <windows2019srv_64Guest/>
     <windows2019srvNext_64Guest/>
   </supportedWindowsGuestIds>

[amoorewmi]

Also don't copy and paste it in.  There is a typo in the code block they added for Debian Linux.  It will also give you that crash message.