Hello there,
The issue you described with Nutanix AHV and Windows Server 2016 memory expansion might be related to how the memory expansion is being handled or reported in the Windows Admin Center (WAC) dashboard.
There are a few potential reasons why the memory value may be incorrectly displayed in the dashboard after a WAC connection:
Dashboard Refresh Issue: The incorrect memory value could be due to a dashboard refresh problem. Sometimes, the dashboard may not update immediately after changes are made, leading to the incorrect display of memory information. Try refreshing the dashboard or reopening it after a few moments to see if the correct value appears.
WAC Integration Issue: There could be an integration issue between Nutanix AHV and the Windows Admin Center, leading to inaccurate reporting of memory values. Ensure that you are using the latest version of WAC and that it is compatible with your Nutanix AHV environment.
Time Delay in Reporting: The memory expansion process may take some time to be fully recognized and reported by the operating system. Windows Server 2016 might require some time to adjust to the new memory allocation, and this delay could result in an incorrect memory display initially.
Nutanix AHV Configuration: There might be a specific configuration or setting in the Nutanix AHV environment that is causing the issue. Check the Nutanix AHV documentation and settings related to memory expansion and integration with Windows Server to ensure everything is correctly configured.
Bug or Compatibility Issue: It's possible that there is a bug or compatibility issue between Nutanix AHV, Windows Server 2016, and the Windows Admin Center. Check for any known issues or updates from Nutanix and Microsoft that address memory reporting problems.
I used AI provided by ChatGPT to formulate part of this response. I have verified that the information is accurate before sharing it with you.
Hope this resolves your Query !!
--If the reply is helpful, please Upvote and Accept it as an answer--