Win10的AAD连接导致启动后崩溃 [英] AAD join of Win10 leads to crash after boot

问题描述

将Windows 10设备加入Azure AD后，后续重新启动会显示旋转轮，并且加载永远不会结束。这些设备无法使用。

After joining Windows 10 devices to Azure AD, the subsequent reboot shows spinning wheel and the loading never ends. The devices are unusable then.

如果我们在启动菜单中关闭ELAM（早期启动反恶意软件）驱动程序，设备将在每次等待3个小时后完成启动。

If we turn off ELAM (Early Launch Antimalware) driver in boot menu, the devices will utimately finish booting after some cca 3 hours of waiting, every time.

试图在AAD加入中生存的步骤：

- 最新的一切即可。所有更新的最新Windows（1709）（2018年2月28日）已安装

- latest everything. latest Windows (1709) with all updates (as for 28th Feb 2018) installed

- 在EMS或Intune中的差异。通过帐户加入Intune许可证（EMS E3，但没有设置政策）或通过帐户加入只有AAD Premium P2（所以只是EMS政策，没有Intune）没有区别

- difference in EMS or Intune. Joined via account with Intune licence (EMS E3, but with no policies set) or joined via account with just AAD Premium P2 (so just EMS policies, no Intune) made no difference

- 完整性扫描。加入前后的sfc / scannow（当它与禁用的ELAM一起启动时）没有区别

- integrity scan. sfc /scannow before and after join (when it booted with disabled ELAM) made no difference

- 设备   name uniquiness 。将设备重命名为绝对唯一的计算机名并重新启动，然后再加入

- device name uniquiness. renaming the device to definitely unique computername and restart, before join

但是没有运气。 

But no luck. 

这是发生在我们的hyperv来宾，但也我们已经尝试过联想和戴尔的实体笔记本电脑。

This is happening to us with hyperv guests but also with physical laptops we have tried, both Lenovo and Dell.

我们接下来可以尝试：

1）我们使用Win10版本1709的自定义映像，安装了各种软件并设置了策略。那里没有杀毒软件。我们将逐步尝试新的图像创建过程以查看哪些可能会产生影响

2）安装我们的图像到UEFI而不是BIOS分区。这个尝试来自于ELAM的转向部分有助于启动的想法

任何想法？

关键字：纺车，aad join，stucked，bricked，problem

推荐答案

在这种情况下需要深入技术故障排除需要从绩效角度来理解延迟的原因。因此，建议您创建

技术支持服务单，因为我们的工程师需要就此问题与您合作，并需要有关该问题的更多详细信息才能找到问题的根本原因。但是，您也可以尝试从iso重新安装并检查。看看是否有帮助。

------------------------------------- -------------------------------------------------- ----------------------
$
点击"标记为答案"在帮助您投票并将其投票为有用的帖子上，这对其他社区成员有益。 

In this scenario requires a deep dive technical troubleshooting need to be done from the performance stand point to understand the cause of the delay. So, suggest you to Create a Technical Support Ticket as our engineers would need to work with you on the issue and would require more details on the issue to find the root cause of the issue. However you can also try to reinstall from iso and check. see if that helps.
-------------------------------------------------------------------------------------------------------------
Do click on "Mark as Answer" on the post that helps you and vote it as helpful, this can be beneficial to other community members. 

这篇关于Win10的AAD连接导致启动后崩溃的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！