IntuneDriveMapping VS Sieve

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/

Biarity/Sieve: ⚗️ Clean & extensible Sorting, Filtering, and Pagination for ASP.NET Core (github.com)

I´m trying out Sieve and the rip my app to pieces and use that instead.

Similar to Sieve

https://github.com/Biarity/Sieve Sieve is a simple, clean, and extensible framework for .NET Core that adds sorting, filtering, and pagination functionality out of the box. Most common use case would be for serving ASP.NET Core GET queries.

If you're looking for a library for a REST API, there really aren't very many good ones. I used Sieve as a starting point to write my own because it didn't support the filtering syntax I was required to use. I would definitely not recommend a new person write their own, however.

I also looked at Sieve: https://github.com/Biarity/Sieve but I'm not sure it is 100% hitting what I am wanting. Unless I am just a bork at the end of my day unable to read properly. Any direction in the right area would greatly be appreciated!

For complex queries like this, you don't have a ton of choices. You could use Sieve (https://github.com/Biarity/Sieve) in lieu of your current implementation. I use it specifically in situations to handle filtering/paging/sorting, not as a general way to access data. Most of the time I write an underlying DB view and hook that up to a keyless entity and allow Sieve to do the actual filtering.

If you're using EF, you can use https://github.com/Biarity/Sieve