Forum Discussion
ADMX drive mapping issue
We have a customer with 12 drive mappings pushed via Intune Import ADMX. We uploaded the admx for windows and the admx for the drivemappings. In the configuration created one policy with al the driveletters configured and pushed this to every device in the environment. Al worked great, untill we changed one drive letter from X to Z i remembered correctly and changed the path to a folder deeper in the folder three.
Then it was pushed to everyone and people got issues with the drivermappings. Only 2 or 3 driveletters were showing in file explorer. When you want to add the drive letter via the wizard you can see all the paths to the different drive letters are there. Adding them via that way is not possible.
We checked all the settings, like persistent drive mappings, enable linkedeconnections, setting all the drives to not configured, Create separate policy for every driveletter, removed the admx in intune and uploaded again, but nothing is working. currently using a custom script via our minitoring system to get it working again.
I have used the ADMX by many customers and never have had these issues. Also opened a microsoft case but they couldn't get it fixed. Only way is a fresh install of the device. But 150 devices is a bit to much time consuming for us and the customer.
Love to hear how i can solve this issue.
2 Replies
Hi, I read this in a separate thread. Apparently, this is a bug with ADMX. If you change the drive even add/delete can left leave some previous registry entries behind. And if that the case it will not map any other drives after the conflicting registry. For example: removing L: could hide M:, N:, O:, etc. This seems same with your scenario.
The fix is clean up the orphaned key with a script, remediation task can be used to perform this action. Remove-Item -Path "HKCU:\Network\L" -Recurse -Force After the cleanup reboot the drives should return.
Thank you for the answer. Do you maybe have a link to this thread?
