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 drive...
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.
