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, using Passthrough Authentication (PTA) for Authentication and we have 3 PTA agents (Including AAD Connect) on-premises. Now, we want to grant users access to an on-premises file share (File server) while they are physically connected to the local network at the office. Each user has an individual Home Drive (H:) defined in their On-premises "Home-Directory attribute" (HomeDirectory), and we want to make this H drive accessible for any users who sign-in to a locally connected shared AADJ devices at the office (We don't want these H drives to be available for remote users). Our shared AADJ devices currently have access to on-premises share files when they’re locally connected at the office, but they don’t have access to user's home drive now. In summary, we want to map Home-Directory attribute UNC path for locally connected azure-ad joined shared devices for any individual users who sign in to these devices.

Just wondering... but how are you mapping those drive letters? And in which context ...are you using PowerShell scripts or the admx solution?WIth powershell script you need to make sure you are deploying that script in the user context... otherwise the %username% cant be resolved..I know that with the admx option, you need to change a couple of things but the username variable works with this option... we use it everywhere 🙂 https://call4cloud.nl/2021/03/willy-wonka-and-the-drive-letter-factory/#part6

I just need to understand it correctly.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

Map Home-Directory attribute UNC path for locally connected azure-ad joined shared devices.

Rudy_Ooms_MVP
MVP
May 11, 2024
Just wondering... but how are you mapping those drive letters? And in which context ...are you using PowerShell scripts or the admx solution?
WIth powershell script you need to make sure you are deploying that script in the user context... otherwise the %username% cant be resolved..
I know that with the admx option, you need to change a couple of things but the username variable works with this option... we use it everywhere 🙂
https://call4cloud.nl/2021/03/willy-wonka-and-the-drive-letter-factory/#part6
NicklasOlsen
Iron Contributor
Apr 23, 2024
I just need to understand it correctly.
Are you looking for a solution, that can map your drives on Azure AD joined devices?
- Rasul_RA1
  Copper Contributor
  Apr 23, 2024
  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.
  - NicklasOlsen
    Iron Contributor
    Apr 24, 2024
    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/

Forum Discussion

Map Home-Directory attribute UNC path for locally connected azure-ad joined shared devices.

Share

Resources