Forum Discussion
Map Home-Directory attribute UNC path for locally connected azure-ad joined shared devices.
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).
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.
- Hi Gordon,
You're welcome, let me know, if you have any questions.
I think it will be hard for you, to map a specific file server based on a location. Is it on group basis, or is it automatically, when the user switch location? I tried using %username%, and it seems to be working for the ADMX method. Thank you for mentioning that! However, we have several file servers based in different locations, and we need to map specific file servers and folders based on the location of each user. Unfortunately, none of the available solutions address our scenario. I attempted to expand the script provided by intunedrivemapping.azurewebsites.net, but I haven’t been successful yet. I’ll keep this post updated if I find a solution. Thanks, Nick!
- I have it working with the %username%.
How do you configure your configuration profile? 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.
