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, ...
Hi Gordon,
Hm, I think I understand the question; otherwise, please correct me 😊.
You can create a configuration profile for each drive and assign it to specific users.
Otherwise, you have the option to utilize this tool and use the security filtering. However, this creates a scheduled task on the device.
https://intunedrivemapping.azurewebsites.net/
Hm, I think I understand the question; otherwise, please correct me 😊.
You can create a configuration profile for each drive and assign it to specific users.
Otherwise, you have the option to utilize this tool and use the security filtering. However, this creates a scheduled task on the device.
https://intunedrivemapping.azurewebsites.net/
Nick,
We're using this method and it's working good for non-variable address (for example "\\sharedserver\publicfolder", or "\\server02\JohnDoe"), but when I tried to address any user who logs in, it doesn't create the home drive (Personal Share Drive) for that specific user. I try to address multiple file server following %USERNAME% and it didn't work (For example I used "\\server02\%USERNAME%", and it didn't work).
We're using this method and it's working good for non-variable address (for example "\\sharedserver\publicfolder", or "\\server02\JohnDoe"), but when I tried to address any user who logs in, it doesn't create the home drive (Personal Share Drive) for that specific user. I try to address multiple file server following %USERNAME% and it didn't work (For example I used "\\server02\%USERNAME%", and it didn't work).
- Ah, now I understand.
The home folder would have to exist, before the drive mapping can map it. If it doesn't exist, it can't map the homefolder unfortunately.The paths already exist on our file servers and are accessible to each user based on their username. We need to devise a method to link the existing folders to the respective usernames (%username%) so that it becomes their Home Drive. This Home Drive will serve as their profile on any device they log into. I think, I’ll likely need to write a script that get the HomeDirectory attribute on-premises and map that path folders for each user.
- I have it working with the %username%.
How do you configure your configuration profile?
