DeviceManagementExtension Failed State

Boston HCI 0

Recently finished a AzureStack HCI deploment for a customer.

Prior to shutdown, we deleted some test VM's. Since then however, the DeviceManagementExtension is in a failed state on all of the HCI servers (4 in total).

What has happened ? How can it be recovered ?

All other extensions on each server are in healthy state.

User's image

Sai Krishna Katakam 265 Reputation points Microsoft Vendor

2024-09-30T07:15:32.4266667+00:00
Hi Boston HCI,

Welcome to the Microsoft Q&A Platform! Thank you for asking your question here.

Issue: The DeviceManagementExtension is in a failed state on all Azure Stack HCI servers after deleting test VMs and shutting down the servers. All other extensions are in a healthy state.

Cause: The issue likely occurred due to changes made before the shutdown, such as deleting test VMs, which may have disrupted the extension’s configuration or operation.

Here are some steps to troubleshoot and potentially resolve the issue:

Look at the logs for the DeviceManagementExtension to identify any specific errors. You can find these logs at C:\ProgramData\GuestConfig\extension_logs\Microsoft.Edge.DeviceManagementExtension\.

Make sure that the VM Agent is running and reporting a Ready status. The VM Agent is crucial for managing and executing extensions. If it’s not running, the extensions won’t work correctly. You can check the VM Agent status using Azure PowerShell:

Get-AzVM -ResourceGroupName <ResourceGroupName> -Name <VMName> -Status

Sometimes, removing the failed extension and reinstalling it can resolve the issue. You can do this via Azure PowerShell:

Remove-AzVMExtension -ResourceGroupName <ResourceGroupName> -VMName <VMName> -Name "DeviceManagementExtension" Set-AzVMExtension -ResourceGroupName <ResourceGroupName> -VMName <VMName> -Name "DeviceManagementExtension" -Publisher "Microsoft.Compute" -ExtensionType "DeviceManagementExtension" -TypeHandlerVersion "1.0"

Make sure there are no network issues that might be preventing the extension from communicating with Azure.

Since the issue started after deleting test VMs, review any other changes made around that time that might have affected the extensions.

For more detailed troubleshooting steps, you can refer to the documentation on Troubleshooting Azure Windows VM extension failures
Register your servers and assign permissions for Azure Stack HCI, version 23H2 deployment

If you have any further queries, do let us know. If the comment is helpful, please click "Upvote".
Sai Krishna Katakam 265 Reputation points Microsoft Vendor

2024-10-01T01:27:33.5966667+00:00

Hi Boston HCI,

Just checking in to see if you had a chance to review my comment on your question. Please let us know if it was helpful and feel free to reach out if you have any further queries.

If you found the information useful, please click "Upvote" on the post to let us know.

Thank You.
Sai Krishna Katakam 265 Reputation points Microsoft Vendor

2024-10-03T06:45:16.4966667+00:00

Hi Boston HCI,

I wanted to check if you had the opportunity to review the information which was provided in my previous posted comment.

If it was helpful, please click "Upvote" on his post to let us know.

Thank You.

Share via

DeviceManagementExtension Failed State

Your answer