I'm trying to deploy the HCI 23H2 cluster from the Azure Portal and hit the following error while validating the cluster. Any suggestions to troubleshoot?

Yall 0 Reputation points
2024-05-10T06:54:38.49+00:00

I have registered the system PatrasA with AzureARC using the below link.
https://learn.microsoft.com/en-us/azure-stack/hci/deploy/deployment-arc-register-server-permissions?tabs=powershell

while validating the nodes from the AzurePortal hit the below error. Any help for the troubleshooting?

Image

Azure Stack HCI
Azure Stack HCI
A hyperconverged infrastructure operating system delivered as an Azure service that provides security, performance, and feature updates.
356 questions
Azure Arc
Azure Arc
A Microsoft cloud service that enables deployment of Azure services across hybrid and multicloud environments.
435 questions
0 comments No comments
{count} votes

2 answers

Sort by: Most helpful
  1. geevee.sajan 10 Reputation points
    2024-05-16T14:27:18.7033333+00:00

    On the node-->go to C:\ProgramData\GuestConfig\extension_logs\Microsoft.Edge.DeviceManagementExtension\

    see if there is edgedevice.txt file.

    Delete this file and it will be auto created in 10 mins.

    Rerun the validation and you should be good

    2 people found this answer helpful.
    0 comments No comments

  2. Prrudram-MSFT 25,081 Reputation points
    2024-05-14T06:12:35.5433333+00:00

    Hi @Yall

    Thank you for reaching out to the Microsoft Q&A platform.

    Please check this blog https://techcommunity.microsoft.com/t5/fasttrack-for-azure/common-deployment-challenges-and-workarounds-for-hci-23h2/bc-p/4065366/highlight/true

    Cause #1

    • Get-NetAdapter -InterfaceDescription NDIS | Disable-NetAdapter
    • Validation selected error failed
    • Error: The resource 'Microsoft.hybridCompute/machines/<ServerName>/providers/microsoft.azurestackhci/edgeDevices/default' could not be found
    • Resolution: In most of the cases that I have seen, the issue was with the NDIS network adapter. I suggest disabling the NDIS adapter as well as any other unused adapters during the deployment process you can enable it back once the deployment is complete.

    Cause #2

    This could also be due to the windows update released on October 11 2022 

    Resolution: in each node create the following registry key  #Add reg key for legacy doman join Write-Host "Add legacy domain join registry key" -ForegroundColor Green # Create a new registry key (if it doesn't exist) try{ $RegPath = "HKLM:\System\CurrentControlSet\Control\LSA" $RegValue = "NetJoinLegacyAccountReuse" $RegistryKey = Get-Item -Path $RegPath -ErrorAction SilentlyContinue if ($RegistryKey.GetValueNames() -contains $RegValue) { # Value exists Write-host "Registry Key already exists, skipping" -ForegroundColor Green } else { # Value does not exist New-ItemProperty -Path $regPath -Name $RegValue -Value 1 -PropertyType DWord } } catch{Write-Host "An error occurred: $($_.Exception.Message)"}

    Troubleshooting guide for any other resource not found errors https://learn.microsoft.com/en-us/azure/azure-resource-manager/troubleshooting/error-not-found?tabs=bicep

    Please Accept Answer and hit Yes for "was this answer helpful" if this helps


Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.