Share via

Error initializing default drive: 'Unable to find a default server with Active Directory Web Services running

Rasitha Mudugama Hewage 220 Reputation points
2025-11-03T18:17:13.19+00:00

Hi ,

please advice on following error and i am running validation before start azure local.User's image

Azure Local
0 comments No comments

Answer accepted by question author

  1. Jilakara Hemalatha 13,340 Reputation points Microsoft External Staff Moderator
    2025-11-03T20:14:00.28+00:00

    Hi Rasitha Mudugama Hewage

    Thank you for reaching out.

    The warning “Unable to find a default server with Active Directory Web Services running” usually indicates that the Active Directory Web Services (ADWS) component is either not running or is not reachable from the node where the validation is being executed.

    ADWS is required for Azure Stack HCI / Azure Local deployments to communicate with Active Directory.

    Please review and perform the following steps to resolve the issue:

    1. Verify ADWS Service on Domain Controllers:
    • On each Domain Controller, open services.msc and confirm that the Active Directory Web Services service is running and set to Automatic.
    • If it’s not running, try starting it manually. If the service fails to start, review the Event Viewer logs for specific errors

    2.From the HCI node, run the following command to verify connectivity to the Domain Controller on port 9389:

    Test-NetConnection <DomainControllerName> -Port 9389
    

    If the connection fails (TcpTestSucceeded: False), review firewall rules, network security groups, and routing configurations that might block port 9389.

    3.Ensure the user account executing the validation has the necessary permissions, particularly GenericAll on the relevant Organizational Units (OUs). Insufficient permissions can prevent the validation from recognizing ADWS services.

    4.Disable IPv6 on all network interfaces and assign static IP addresses if applicable, as misconfigured IPv6 settings can impact communication.

    5.Run the following command to ensure the domain name resolves correctly to your Domain Controllers:

    nslookup <your-domain>
    

    6.Run the below command to verify that at least one Domain Controller is ADWS-enabled:

    Get-ADDomainController -Discover -Service ADWS
    

    Once these steps are completed, re-run the validation. This should resolve the issue and allow you to proceed with Azure Local deployment.

    Please find below documentations for reference:

    Related threads discussed on this issue:

    Hope this helps! please let me know if you have any queries.

    Was this answer helpful?


0 additional answers

Sort by: Most helpful

Your answer

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