Forum Discussion
Onboarding Defender on Hyper V Server 2019, failing with error [Error Id: 15, Error Level: 1]
Hi, I have a Windows Server 2019 Hyper-V server that is failing the Defender for Endpoint onboarding with the following error [Error Id: 15, Error Level: 1] Unable to start Microsoft Defender fo...
Installing the Unified Installer package downloaded from the MDE portal also includes the sensor install. Even if the install is successful and the server is onboarded into MDE, Azure Arc won't recognise that the "MDE.Windows" extension is installed.
There is a specific method that Microsoft provided to me to effectively do a manual install of the MDE.Windows extension, but it's quite convoluted and in fact when we attempted it yesterday on a call with Microsoft engineers, it failed.
Discussed in a different ongoing thread - https://techcommunity.microsoft.com/t5/microsoft-defender-for-endpoint/re-install-mde-windows-extension/m-p/3781123/emcs_t/S2h8ZW1haWx8dG9waWNfc3Vic2NyaXB0aW9ufExGU0RPREhVTU1HUUFDfDM3ODExMjN8U1VCU0NSSVBUSU9OU3xoSw#M3420
There is a specific method that Microsoft provided to me to effectively do a manual install of the MDE.Windows extension, but it's quite convoluted and in fact when we attempted it yesterday on a call with Microsoft engineers, it failed.
Discussed in a different ongoing thread - https://techcommunity.microsoft.com/t5/microsoft-defender-for-endpoint/re-install-mde-windows-extension/m-p/3781123/emcs_t/S2h8ZW1haWx8dG9waWNfc3Vic2NyaXB0aW9ufExGU0RPREhVTU1HUUFDfDM3ODExMjN8U1VCU0NSSVBUSU9OU3xoSw#M3420
- In a surprising turn of events, all servers which had the error installing the MDE.Windows extension, now have the extension installed. So I think either...
1. Azure just kept trying until it succeeded
2. Microsoft found the root cause and fixed the back-end
3. Microsoft engineers used a manual method and fixed directly on our tenant.
Am following up with Microsoft- Thanks for the updates.
had quite a few cases in the Defender onboarding where the exact cause was not clear, that said we had to push through a large number of machines so we didn't spend anymore time than was required to get it working. Ironically the Linux machines were easier than the Windows.Hi,
I've just got same issue here. Trying to onboard a Microsoft Hyper-V Server, but always got this error. I've tried some of the described options, without any luck. This server is on our onpremise DC.
Did you had any extra information from Microsoft or find any other way to troubleshoot or solve this issue?
Thanks
