Mapped file share issues

Daniel 81 Reputation points
2024-05-15T14:25:17.5833333+00:00

Hello,

I have run up to a strange issue with on-prem file share access on Azure AD joined and Intune managed Windows devices.

The issue is:

When user tries to copy or move a file on a on-prem file share he gets and error:

User's image

I went ahead and created a new Intune policy that adds file share DNS name address and IP address to:

Site to Zone Assignment List

User's image and make sure that Intranet Sites: Include all network paths (UNCs) is Enabled:

User's image

and Intranet Sites: Include all local (intranet) sites not listed in other zones is Enabled:

User's image

The policy was applied to the device successfully and there is a strange thing happening now.

If I access the file share from File Explorer with DNS name of file share: \fileshare.domain.com\SHARE I can move/copy files without any warning what so ever. (Fine it works :)

But if I access the file share with IP address of file share server: \IPADDRESS\SHARE or by the mapped drive shortcut I get the warning message:

User's image

Did I miss something in the policy or there is something else I need to add? A note all user devices are Azure AD joined only (they are not domain joined).

Thanks for the ideas and answers in advance!

Windows Server
Windows Server
A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.
12,303 questions
Windows Autopilot
Windows Autopilot
A collection of Microsoft technologies used to set up and pre-configure new devices and to reset, repurpose, and recover devices.
418 questions
Microsoft Intune
Microsoft Intune
A Microsoft cloud-based management solution that offers mobile device management, mobile application management, and PC management capabilities.
4,489 questions
0 comments No comments
{count} votes

Accepted answer
  1. Crystal-MSFT 44,416 Reputation points Microsoft Vendor
    2024-05-16T01:35:46.1966667+00:00

    @Daniel, Thanks for posting in Q&A. Based on my researching, for the warning, we can add the IP address into "Local Intranet" to fix the issue.

    https://superuser.com/questions/149056/disable-these-files-might-be-harmful-to-your-computer-warning

    Note: non-Microsoft link, just for the reference.

    Please add the file share server DNS name and IP address into the fist policy setting with value 1 to see if it can work.

    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.


0 additional answers

Sort by: Most helpful