Giters

Weatherlights / Intune-Network-Drive-Mapping-Tool

Map on-premises network shares with Intune and the Microsoft Store for Business

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Drives not mapping but logs seem ok

bpmarine opened this issue · comments

commented

Thanks for your handy tool, I'm hoping I can make it work!

My logs look ok, but the drives are not mapping for me:

<![LOG[Will now connect O to \\10.11.12.7\MAL]LOG]!><time="16:54:46.980-000" date="03-04-2022" component="DriveSettings" context="" type="1" thread="1" file=""> <![LOG[Will now connect P to \\10.11.12.7\Projects]LOG]!><time="16:54:46.981-000" date="03-04-2022" component="DriveSettings" context="" type="1" thread="1" file=""> <![LOG[Will now go to sleep.]LOG]!><time="16:54:56.997-000" date="03-04-2022" component="NetworkDriveMapping" context="" type="1" thread="1" file="">

I have checked the network paths directly in File Explorer and I can browse them without issues.

My ADMX template ingestion and the drive configs are on different policies. I'm using Enabled, Refresh Interval and Map Persistent with the /"enabled/"/ string, and only have these two drives in the Network Share Mappings settings. The logs suggest that everything is being read correctly, but it's not showing drives after many reboots and syncs via Company Portal.

Any suggestions would be appreciated! BTW, Windows 21H2

commented
commented

Hello

I created a new release that mainly improves logging. Please update and check the logs again and see if there are some additional informations. Please keep me updated :).

Best
Hauke

commented
commented
commented

Hey

did you use MapPersistent?

Best
Hauke

commented
commented

Hey

you can check the the following registry key to see if your configuration is applied successfully: HKEY_CURRENT_USER\Software\Policies\weatherlights.com

Intune sometimes falsely reports that a setting is not applied (this has something to do with the "LineBreak" Formatting in the ADMX Template).

However: The error 1202 translates to ERROR_DEVICE_ALREADY_REMEMBERED (The local device name has a remembered connection to another network resource). For the start I would recommend you to disable MapPersistent (as a matter of fact you do not need it at all it is in there for legacy reasons). Afterwards I would recommend you to remove all existing network connections on your machine (or use a blank machine).

Also: Is there something else that maps drives on your machine (A script or anything) that could be in conflict?

Best
Hauke

commented

Also check this guide here that has something nice ideas how to troubleshoot:
https://appuals.com/how-to-fix-the-local-device-name-is-already-in-use-error-on-windows/

commented
commented
commented

Ahhh nice that we got this one resolved :).

Well thank you very much for the feedback. If you like I really appreciate a nice comment in the Microsoft Store ;).

Thank you again and have a great day
Hauke

commented