This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(217.60000000000002, 93%, 31%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EP%3C/text%3E%3C/svg%3E)
I am working with new windows 10 laptop that was provisioned using Autopilot. The user is trying to use "Active Directory Administrative Center" but keeps getting the following error when trying to launch the app:
"Cannot find an available server in the <DOMAINNAME> domain that is running the ADWS service."
ADWS is running normally, as users who have domain-joined laptops can connect with no errors. The autopilot client can see all the domain controllers, (ping, Test-Netconnection to port 9389, etc). ADUC also is able to connect...So it's not a connectivity issue.
We've also tried using "dsac.exe -Server <IPADDRESS>" but still get the same error. Is there another way to force ADAC to use a specific DC?
thanks in advance.
When you connected a device using Autopilot it connects via AAD, not local AD. Are you running in a hybrid scenario where you connect the computer to local AD as well?
No, the laptop is strictly AAD-connected.
if your laptop is AAD-connected only as you mentioned you won't be able to user ADUC to manage if not connected on CORP network with access to DCs
I've seen the following behavior
AAD only device, connected to CORP network (ADDS site) where when you're in the office (CORP network) you're able to reach \DC01.fqdn using the same "AzureAD\user" creds.
or either file server \fileserver\shared-folder\
The user is able to use ADUC but not Active Directory Administrative Center.
User is also able to browse the \<domaincontroller\sysvol folder from the client as well.
The user can browse domain resources from the laptop, it's just the ADAC that thinks it can't connect. It seems to look for the environment variable "LOGONSERVER" which is set to the client name since it's not "joined" to the actual domain. There doesn't seem to be a way to tell ADAC to connect to a different server.
The user can use ADUC to connect to a domain controller once connected to the corporate network via VPN. User can also connect to the SYSVOL share on the domain controllers using domain credentials when prompted.
It seems to be just the ADAC that won't allow manual selection of a DC (seems it will only use what's specified in the LOGONSERVER environment variable).
