我的OS部门通过SCCM在AHV群集上遇到了一个错误。
我将与Nutanix相关的驱动程序应用于任务序列,并以下查询:
从win32_computersystem中选择 *,其中诸如“ kvm”之类的模型
这一直对我有用。
在我将群集迁移到AOS5.0之后,该步骤在任务序列中跳过了一条消息,该消息说该情况是错误的。
难道是,新创建的基于AOS5.0的群集显示了另一个模型吗?我在此群集上的运行VM仍然显示为Modul,所以我有些困惑。
最好的答案乔恩
\n\nIt is possible to revert this branding with a system wide GFLAG, and we're working on adding a per-VM flag to revert the branding on a more granular VM by VM basis for customers who don't want to see that.
\n
\nThe easiest approach would to be update the SCCM side to match the new branding, but if you need to change the AOS side, contact support and they can help enable that backend GFLAG (custom tuning flag)
\n
\nCheck out the AOS 5.0 release notes, under Notes and Cautions:
\nhttps:\/\/portal.nutanix.com\/#\/page\/docs\/details?targetId=Release-Notes-Acr-v50:top-notes-cautions-Acr-v50-r.html<\/a>
\n
\nAs of AOS 5.0, Nutanix has updated virtual SMBIOS system details reported by guest VMs managed by AHV. The details include the virtual hardware platform name. Specifically, the hypervisor and vendor names have been rebranded to AHV and Nutanix, respectively. This change might affect a limited number of applications that use hardware information for licensing activation, for example. Please contact Nutanix support if this change affects your applications.<\/b>","className":"post__content__best_answer"}">