Slow Autostart / Persistent mapping not working

[k1ee]

Hey Hauke,

I had two projects where I needed to deploy an on-premises DC and file server. They are connected via Entra ID Cloud Sync, and Cloud Kerberos trust is also working for WHfB.

For mounting the network shares, I use Intune Network Drive Mapper and configured it with the GPOs imported to Intune.

I face the issue that the drives are not persistently mapped, despite the fact that I configured it in Intune.

The app autostarts very delayed, and I got complaints from clients that their drives are missing. When they manually start the app, the drives are instantly there.

Do you know:

• How I can get persistent mapping working?
• How I might be able to prioritize the autostart of the app?

Thanks!
Chris

[Truciw]

What the purpose of persistent if the process will check all the time and try to mount ?
For the second point, I have the same behaviour, I guess that it is because app is auto started before the user policy come and will not recheck regularly > app & AutoStart policy > System context

User policy can come after AutoStart (path and interval check). Looks that if no path was configured before started,the process will not check regularly or will use the default delay 10800 seconds

[k1ee]

Persistent drives would solve the problem, that the drive is not there on boot and the user is opening a ticket, because he cannot access the server.

[Truciw]

Exception the first launch. When all policiers are set. You dont really need because a background process (autostart app) will try to mount drives every 10s (custom it in policy) even if user try to dismount it or the vpn is not up. No issue from when I deployed the app. Except the first launch without policy. I'm using for months without persistent. I don't like the red cross on drive when the path are not available with persistent setting