Autopilot Laptops Unable to Map Azure File Shares Due to Domain Controller Authentication Issues

Question

Autopilot Laptops Unable to Map Azure File Shares Due to Domain Controller Authentication Issues

Sal Delvisco 0

In a hybrid environment with On-Prem AD and Entra ID/M365, there is an issue mapping Azure File Shares to Intune Autopilot laptops. MDM imaged laptops can successfully map the network drives using the PowerShell script (New-PSDrive).

However, the Autopilot laptops are encountering an error when attempting to map the drives, specifically: "New-PSDrive : The system cannot contact a domain controller to service the authentication request. Please try again later." Notably, there are no related events in the Domain Controller's Event Logs.

The laptop is connected to the network, and it is possible to ping the Domain Controllers from the laptop.

1 answer

Your answer

Answer 1

Crystal-MSFT 54,201 Microsoft External Staff

@Sal Delvisco, Thanks for posting in Q&A. From your description, I know we get the error on the Autopilot device, for New-PSDrive.

To clarify our issue, could you collect the following information to us.

Could you confirm if we run the command "New-PSDrive." manually on one Autopilot enrolled device or we deploy it via Intune script?
If we deploy via Intune script, please capture a configuration of it.
I notice the DC is able to ping. If we manually access the Azure file share on this Autopilot device, can it be accessible?

Please collect the above information and if there's any update, feel free to let us know.

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Sal Delvisco 0 Reputation points

2024-11-27T15:29:37.2966667+00:00

Good morning. Thanks for the response. Answers to your questions:

I am running the New-PSDrive command manually at this time.

Yes, I can ping the Domain Controllers. They are accessible to my device. I am logging into the device with domain credentials, and the login works fine.

I cannot manually access the drive on the device either. In fact, we have other drives mapped through GP to File Shares on a VM and I cannot manually access those mapped drives either. Those mapped drives do not successfully connect in Windows either. I get the same error on those on-prem mapped drives as I do for the Azure File Share mapped drive.
Crystal-MSFT 54,201 Reputation points Microsoft External Staff

2024-11-28T06:23:07.59+00:00

@Sal Delvisco, Thanks for the reply. Could you let us know what is the command we use to map? Did we use one like the example 4 to map the drive?

https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.management/new-psdrive?view=powershell-7.4#example-4-create-a-persistent-mapped-network-drive-using-credentials
Crystal-MSFT 54,201 Reputation points Microsoft External Staff

2024-12-02T01:54:19.5666667+00:00

@Sal Delvisco, Hope things are going well. Please help to confirm the above information to go further. Thanks!
Sal Delvisco 0 Reputation points

2024-12-02T15:39:57.2033333+00:00
This is the script I am using to try to map the drives. It is just a New-PSDrive command:

$connectTestResults = Test-NetConnection -ComputerName smrtfilesharestorage.file.core.windows.net -Port 445

if ($connectTestResults.TcpTestSucceeded) {

#Mount the drive New-PSDrive -Name Z -PSProvider FileSystem -Root "\\xxxxxxxxxxsharestorage.file.core.windows.net\testfileshare" -Persist

}

else {

Write-Error -Message "Unable to reach the Azure Stroage Account via port 445" ```}
Crystal-MSFT 54,201 Reputation points Microsoft External Staff

2024-12-03T02:03:04.5566667+00:00

@Sal Delvisco, From the script, I find the credential is not included. To confirm if the issue is with the credential, please add credential parameter in the command to see if it can work.
Sal Delvisco 0 Reputation points

2024-12-03T15:53:06.0266667+00:00

I added a credential to the command using my administrator account. The script runs without errors, and prompts me for my password, but it does not map the drive in Windows at all on our Intune Autopilot devices (this script maps drives fine on our older Domain-joined MDM imaged devices, so this is just an issue with the Autopilot laptops).
Crystal-MSFT 54,201 Reputation points Microsoft External Staff

2024-12-04T01:31:01.7066667+00:00

@Sal Delvisco, Thanks for the reply. If you use administrator account to map, the map drive will show under administrator account. You can use current user to map to let it show under the profile.
Sal Delvisco 0 Reputation points

2024-12-04T15:34:50.7433333+00:00

I believe I have the Intune policy working now, at least for some of our devices.
Crystal-MSFT 54,201 Reputation points Microsoft External Staff

2024-12-05T01:44:28.02+00:00

@Sal Delvisco, Thanks for the reply. For the working devices, please let us know how did we deploy the policy? Please get detailed configuration to let us know it better.

Meanwhile, for the working device, is it Microsoft Entra Joined or Microsoft Entra hybrid joined?

Share via

Autopilot Laptops Unable to Map Azure File Shares Due to Domain Controller Authentication Issues

1 answer

Your answer