Forum Discussion
Map Home-Directory attribute UNC path for locally connected azure-ad joined shared devices.
We have an on-premises Active Directory (AD) environment connected to Azure AD via AD Connect. We’ve successfully joined our devices to Azure AD using Azure AD Join (MEJ) through Autopilot. We also, ...
I just need to understand it correctly.
Are you looking for a solution, that can map your drives on Azure AD joined devices?
Are you looking for a solution, that can map your drives on Azure AD joined devices?
NicklasOlsen Correct, but we have different paths for each individual user accounts which are their personal drive (We call it Home Drive). These paths are available on "Home Directory" Attributes on Active Directory. When I connect Azure joined devices to a local network, all shared drives and home Drives are accessible, but they are not Mapped for users as a Drive. they should get the path for Shared Drive and Home Drive and open it via the explorer.
- Hi Gordon,
It's fairly simple to map your drive mappings through Intune. In regards to the home directory, this is also possible to map. How have you named the home folders for your users? Do you use %USERNAME%?
This blog post might help you along the way:
https://www.learnintune.net/the-future-of-drivemapping/- Thank you, Nick, for your response.
We have several servers for Home Drives, and we’ve named them based on the username and the group they are assigned to. For instance, group members of X need access to \\Server01\%USERNAME%, while members of Y require a mapped drive to \\Server02\%USERNAME%, and so on.
I’ve used a method to map two other drives that need to be available for all users. While it worked with some customizations, unfortunately, it didn’t work with %USERNAME%. I even tried mapping the Home Drive for a test user using this method, and it worked for that specific user, but it doesn’t seem to work consistently for various users, and various shared servers.
https://github.com/nicolonsky/IntuneDriveMapping
