本文介绍了在服务器核心测试中运行失败 - “DismGetFeatureInfo失败,错误代码:-2146498548”的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我正在尝试在Server 2016 Core(标准版)和"在服务器核心测试中运行"中验证设备。始终失败并显示消息  " DismGetFeatureInfo失败,错误代码:-2146498548"。

I am trying to certify a device on Server 2016 Core (standard) and "Operate in Server Core Test" always fails with the message  "DismGetFeatureInfo failed with error code: -2146498548".

十六进制中的错误代码为0x800f080c,这就是"dism / online / Get-FeatureInfo ..."返回未知功能。  我查看了servercorecheck.dll(OiSCT的二进制文件)的二进制文件,看起来它试图为三种不同的GUI功能运行DismGetFeatureInfo
- "ServerCore-FullServer","Server-Gui" Shell"和"Server-Gui-Mgmt"确保它们处于"已删除有效负载已禁用"的状态但是这些功能在Server 2016 Core安装中甚至不会出现
。  因此必须假设它们可能已从GUI安装中删除以运行OiSCT 这是我必须为Server 2012-R2传递该测试所做的事情。  但是看看"在服务器核心测试中操作
"的文档是什么?对于S2016说:

That error code in hex is 0x800f080c which is what "dism /online /Get-FeatureInfo ..." returns for an unknown feature.  I looked at the binary for servercorecheck.dll (the binary for OiSCT) and it looks like it is trying to run DismGetFeatureInfo for three different GUI features - "ServerCore-FullServer", "Server-Gui-Shell", and "Server-Gui-Mgmt" to make sure that they are in the state of "Disabled with payload removed" but those features are not even present in a Server 2016 Core installation.  So it must be assuming that they were possibly removed from a GUI installation in order to run OiSCT Which is what I had to do for Server 2012-R2 to pass that test.   But look what the documentation for "Operate in Server Core Test" for S2016 says:

如果您安装了"完整服务器"或"具有GUI的服务器"或在安装过程中,您应该重新安装Windows并选择
"服务器核心安装"。安装程序中的选项,以确保运行认证的服务器上不会留下带有GUI的服务器的痕迹。驱动程序的所有安装和配置测试必须在服务器核心内完成

以前有一个过滤器5856来解决无法解决的问题从GUI切换到Core但它在2016年11月到期。显然,期望是在Server Core下运行所有​​驱动程序验证测试。  我不知道
如何解决这个问题。  我应用了最新的过滤器,但没有帮助。

Previously there was a Filter 5856 to get around the problem of not being able to switch from GUI to Core but it expired in November of 2016.  And apparently the expectation was to run all driver verification test under Server Core.  I don't know how work around this.  I applied the latest filter and that did not help.

希望有人可以提供帮助。 

Hope someone can help with this. 




Tim

推荐答案

https://social.msdn.microsoft.com/Forums/en -US / 2927825a-dd0c-450d-b943-05a08d882c88 / question-about-filter5856-operating-in-server-core-test-in-windows2016?forum = whck

https://social.msdn.microsoft.com/Forums/en-US/2927825a-dd0c-450d-b943-05a08d882c88/question-about-filter5856-operate-in-server-core-test-in-windows2016?forum=whck

https:/ /social.msdn.microsoft.com/Forums/en-US/997abc57-3ba0-489d-a9da-9f55edfa5429/hlk-testing-under-windows-server-2016all-test-items-passed-but-could -not-get-certificate?forum = whck

https://social.msdn.microsoft.com/Forums/en-US/997abc57-3ba0-489d-a9da-9f55edfa5429/hlk-testing-under-windows-server-2016all-test-items-passed-but-could-not-get-certificate?forum=whck

使用sconfig命令,diskpart命令,devcon命令等,可以以某种方式管理环境。

很难记住,但让我们尽力而为。

https://technet.microsoft.com/en- us / windows-server-docs / get-started / sconfig-on-ws2016?f = 255& MSPPError = -2147217396

https://technet.microsoft.com/en-us/library/ cc770877(v = ws.11).aspx

https://msdn.microsoft.com/en-us/windows/hardware/drivers/devtest/devcon-general-commands

https://technet.microsoft.com/en-us/windows-server-docs/get-started/sconfig-on-ws2016?f=255&MSPPError=-2147217396
https://technet.microsoft.com/en-us/library/cc770877(v=ws.11).aspx
https://msdn.microsoft.com/en-us/windows/hardware/drivers/devtest/devcon-general-commands



通过设置远程管理,您可以在一定程度上使用GUI进行操作。


By setting the remote management, you can operate it to some extent with the GUI.





这篇关于在服务器核心测试中运行失败 - “DismGetFeatureInfo失败,错误代码:-2146498548”的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持!

11-03 11:03