![]() If you have a Hybrid scenario, see Troubleshooting hybrid Azure Active Directory joined Windows 10 and Windows Server 2016 devices for troubleshooting steps. If the infrastructure is in a non-Hybrid join environment, these event IDs are expected during Windows 10 deployment. When the device tries to do Hybrid join, the registration fails, and the events are logged. These event IDs occur when the infrastructure isn't prepared for Hybrid join. As such, this question will be closed as off-topic. Exit code: Unknown HResult Error code: 0x801c001d. This is likely to be a problem with the eve-ng environment, please contact the appropriate support channels for that product. Source: Microsoft-Windows-User Device RegistrationĪutomatic registration failed at join phase. Log Name: Microsoft-Windows-User Device Registration/Admin Exit code: Unknown HResult Error code: 0x801c001d. Failed to lookup the registration service information from Active Directory. 2nd VM for Windows Server 2016: 100GB HDD + 16 GB RAM. Vmware ESXI 6.5 Based setup: 1 VM for EVE-NG: 500GB SSD + 32 GB allocated RAM. Setup:Dell PowerEdge R620 128GB Ram 12 Core server. ![]() When you deploy Windows on a device, these events are logged: Log Name: Microsoft-Windows-User Device Registration/AdminĪutomatic registration failed. EVE-NG QEMU based nodes are not starting. This article provides a resolution for the event ID 307 and 304 that are logged when you deploy Windows on a device.Īpplies to: Windows 10 - all editions, Windows Server 2019 Original KB number: 4480781 Symptom
0 Comments
Leave a Reply. |