hostsbion.blogg.se - Mapped network drive not showing

Mapped network drive not showing windows 10#

It is possible to configure network drive mappings by simply creating the required registry keys/values. This is so that the drive mappings can be rebuilt at each user sign-in. When a network drive mapping is marked as persistent the configuration is stored in the registry.

Ensure mapped drives switch from “offline” to “online” when connectivity to the remote path is available.

Create mapped network drives without requiring network connectivity to the remote path.

Easily change/remove mappings without having to edit/re-deploy scripts.

Control assignment of drive mappings via Azure AD groups.

Configure the drive mappings directly in Intune.

The main requirements I had when I developed this solution were: Yes… network drive mappings without PowerShell😊.

Mapped network drive not showing windows 10#

In this post, I am going to share another way of mapping drives on Intune-managed Windows 10 devices without using anything other than MDM policy. These solutions typically use a combination of PowerShell, Scheduled Tasks, etc. There isn’t any native support for doing this within Intune today although there are some great alternative solutions already documented by some MVPs and members of the MEM community. Apart from the ability to configure preferences that the user can override/customize it also has some other useful features such as network drive mappings.

One of the current challenges when moving from a group policy to MDM with Intune is the lack of support for group policy preferences (GPP).