Intune-Network-Drive-Mapping-Tool VS IntuneDriveMapping

We used this tool from the Microsoft store: https://github.com/Weatherlights/Intune-Network-Drive-Mapping-Tool/blob/main/Documentation/Manual.md

Currently, each user has a (local) Synology account. For the pilot, we've been using the Intune Drive Mapping Generator tool to create a PowerShell script to deploy the mapped drives. As an initial test, we've been manually adding each user's Synology credentials to Windows Credential Manager on their machine. This would probably be "fine" for us if not for the shared PCs; we'd like for users to sign into any shared PC and auto-magically have all their shares mapped and authenticated, ready for use.

Intune Drive Mapping Generator

I am currently hybrid environment with AADJ only devices. For my users on AADJ devices I used Intune Drive Mapping Generator by Nicola Suter. I don't have any user folders mapped but maybe you could use a system variable like %USERNAME% to map their folders. Otherwise this worked great for our common file shares.

I think this is exactly what you are searching for: https://intunedrivemapping.azurewebsites.net/

This script performs network drive mappings with PowerShell and is auto generated by the intune-drive-mapping-generator ([https://intunedrivemapping.azurewebsites.net](https://intunedrivemapping.azurewebsites.net)). When executed under SYSTEM authority a scheduled task is created to ensure recurring script execution on each user logon.

Just wondering what's this Intune mapping generator here do differently to creating a regular powershell script for mapping drives?

Did you use this script? https://intunedrivemapping.azurewebsites.net/