Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Extension fails to install on Windows VM #6

Open
ruslangalasun opened this issue Feb 3, 2022 · 2 comments
Open

Extension fails to install on Windows VM #6

ruslangalasun opened this issue Feb 3, 2022 · 2 comments

Comments

@ruslangalasun
Copy link

ruslangalasun commented Feb 3, 2022

MDE extension deployment is returning the error below. I tried the deployment using Azure DevOps first and then did the manual ARM deployment through Azure Portal.

Status Message: VM has reported a failure when processing extension 'MDE.Windows'. Error message: "Failed to configure Microsoft Defender for Endpoint: Protected Setting defenderForEndpointOnboardingScript does not exist, please use mdeOnboardings API to retreive it (https://docs.microsoft.com/en-us/rest/api/securitycenter)"

@ruslangalasun
Copy link
Author

ruslangalasun commented Feb 3, 2022

To add some context, this is the code I'm using in my ARM template:

{
"type": "Microsoft.Compute/virtualMachines/extensions",
"apiVersion": "2021-03-01",
"location": "[parameters('location')]",
"name": "[concat(parameters('vmName'),'/MDE.Windows')]",
"properties": {
"autoUpgradeMinorVersion": true,
"publisher": "Microsoft.Azure.AzureDefenderForServers",
"type": "MDE.Windows",
"typeHandlerVersion": "1.0",
"settings": {
"azureResourceId": "[resourceId('Microsoft.Compute/virtualMachines',parameters('vmName'))]",
"defenderForServersWorkspaceId": "[parameters('WorkspaceId')]",
"forceReOnboarding": false
},
"protectedSettings": {}
}
}

@ruslangalasun
Copy link
Author

ruslangalasun commented Feb 18, 2022

Hopefully, someone can look into this issue soon. Here are some additional troubleshooting details that I did.
When I looked at one of the older VMs that we have I saw the following files for the Extension:

image

In this case, the extension was provisioned successfully and we didn’t see any issues.

Here is a screenshot from a new VM where the extension is failing:
image

You can see that WindowsDefenderATPOnboardingScript file is missing, which is exactly what the error message is complaining about:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant