Windows 10: How can I use the local group policy in windows 10 to map a network drive persistently

Anoop Kakumanu · Apr 9, 2020

Hi all,

we are testing on few machines on how to map network drives using local group policy.

So the question is: How do I use the local group policy to achieve the below.

A shared network drive has to be mapped once the users logged in using their Windows login credentials. The mapped drive should be persistent.

Please advise.

:)

Morris Subba · Apr 9, 2020

Windows Defender Group Policy Disabeled

Hi,

Thank you for contacting Microsoft community.

As you have stated you want to disable the group policy so that you can run windows defender on the computer.

I would like to suggest few troubleshooting steps:

Method 1: Disable group policy from gpedit.msc

Press Windows key + R.

Type gpedit.msc and click Ok.(it will open Local Group policy editor)

Go to Computer Configuration/Administrative Templates/Windows Components/Windows Defender.

In the right pane of
Windows Defender in Local Group Policy Editor, double click/tap on the
Turn off Windows Defender policy to edit it.

Select (dot) Not Configured or
Disabled, click/tap on OK,

When finished, you can close the Local Group Policy Editor if you like.

If the issue still persist you can follow method 2.

Method 2: Disable group policy from registry.

Important: This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow
these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the
article in the Microsoft Knowledge Base:

How to back up and restore the registry in Windows

http://support.microsoft.com/kb/322756

Press Window Key +R.

Type regedit and click. (it will open registry)

Go to HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows Defender

Right Click on Window Defender to create a new Dword.

Click on New and Select Dword.

Type DisableAntiSpyware.

Right click on DisableAntiSpyware and click on modify.

Set the value to 0 instead of 1.

Hope this information is helpful. If the issue still persists, you can write back to us and we will be glad to assist you further.

Compumind · Apr 9, 2020

Mapped network drives don't work in Windows 10 version 1809

Symptoms

You experience the following issues in Windows 10, version 1809:

In Windows Explorer, a red X appears on the mapped network drives.

Mapped network drives are displayed as Unavailable when you run the net use command at a command prompt.

In the notification area, a notification displays the following message:Could not reconnect all network drives.

Workaround

You can work around this issue by running scripts to automatically reconnect mapped network drive when you log on the device. To do this, create two script files, and then use one of the workarounds, as appropriate.

Scripts

Create a script file named MapDrives.cmd

The script file includes the following scripts. The file should be run at a regular (non-elevated) command prompt:

PowerShell -Command "Set-ExecutionPolicy -Scope CurrentUser Unrestricted" >> "%TEMP%\StartupLog.txt" 2>&1
PowerShell -File "%SystemDrive%\Scripts\MapDrives.ps1" >> "%TEMP%\StartupLog.txt" 2>&1

Create a script file named MapDrives.ps1

The script file includes the following scripts. The file should be run at a regular (non-elevated) command prompt:

$i=3
while($True){
$error.clear()
$MappedDrives = Get-SmbMapping |where -property Status -Value Unavailable -EQ | select LocalPath,RemotePath
foreach( $MappedDrive in $MappedDrives)
{
try {
New-SmbMapping -LocalPath $MappedDrive.LocalPath -RemotePath $MappedDrive.RemotePath -Persistent $True
} catch {
Write-Host "There was an error mapping $MappedDrive.RemotePath to $MappedDrive.LocalPath"
}
}
$i = $i - 1
if($error.Count -eq 0 -Or $i -eq 0) {break}
Start-Sleep -Seconds 30
}

Workarounds

Workaround 1: Create a startup item

Note This workaround works only for the device that has network access at logon. If the device has not established a network connection by the time of logon, the startup script won't automatically reconnect network drives.

Copy the script file (MapDrives.cmd) to the following location:

%ProgramData%\Microsoft\Windows\Start Menu\Programs\StartUp

Copy the script file (MapDrives.ps1) to the following location:

%SystemDrive%\Scripts\

A log file (StartupLog.txt) will be created in the %TEMP%\ folder.

Log off, and then log back on to the device to open the mapped drives.

Workaround 2: Create a scheduled task

Copy the script file MapDrives.ps1 to the following location:

%SystemDrive%\Scripts\

In Task Scheduler, select Action > Create Task.

On the General tab in the Create Task dialog box, type a name (such as Map Network Drives) and description for the task.

Select Change User or Group, select a local user or group (such as LocalComputer\Users), and then select OK.

Select the Run with highest privileges option.

On the Triggers tab, select New, and then select At log on for the Begin the task field.

On the Actions tab, select New, and then select Start a program for the Action field.

Type Powershell.exe for the Program/script field.

In the Add arguments (optional) field, type the following:
-windowsstyle hidden -command .\MapDrives.ps1 >> %TEMP%\StartupLog.txt 2>&1

In the Start in (optional) field, type the location (%SystemDrive%\Scripts\) of the script file.

On the Conditions tab, select the Start only if the following network connection is available option, select Any connection, and then select OK.

Log off, and then log back on to the device to run the scheduled task.

Workaround 3: Group Policy settings

If the mapped drives are defined through the Group Policy settings, update the action of the drive maps to Replace. This will delete the existing mapped drive and create the mapping again on each logon. Any settings on the mapped drive that are changed from the Group Policy settings will be lost on each logon. You may also have to run the gpupdate command (together with the /force parameter) to update the Group Policy settings.
Click to expand...

Source: https://support.microsoft.com/en-us/...0-version-1809

Brink · Apr 9, 2020

Mapped network drives don't work in Windows 10 version 1809

Symptoms

You experience the following issues in Windows 10, version 1809:

In Windows Explorer, a red X appears on the mapped network drives.

Mapped network drives are displayed as Unavailable when you run the net use command at a command prompt.

In the notification area, a notification displays the following message:Could not reconnect all network drives.

Workaround

You can work around this issue by running scripts to automatically reconnect mapped network drive when you log on the device. To do this, create two script files, and then use one of the workarounds, as appropriate.

Scripts

Create a script file named MapDrives.cmd

The script file includes the following scripts. The file should be run at a regular (non-elevated) command prompt:

PowerShell -Command "Set-ExecutionPolicy -Scope CurrentUser Unrestricted" >> "%TEMP%\StartupLog.txt" 2>&1
PowerShell -File "%SystemDrive%\Scripts\MapDrives.ps1" >> "%TEMP%\StartupLog.txt" 2>&1

Create a script file named MapDrives.ps1

The script file includes the following scripts. The file should be run at a regular (non-elevated) command prompt:

$i=3
while($True){
$error.clear()
$MappedDrives = Get-SmbMapping |where -property Status -Value Unavailable -EQ | select LocalPath,RemotePath
foreach( $MappedDrive in $MappedDrives)
{
try {
New-SmbMapping -LocalPath $MappedDrive.LocalPath -RemotePath $MappedDrive.RemotePath -Persistent $True
} catch {
Write-Host "There was an error mapping $MappedDrive.RemotePath to $MappedDrive.LocalPath"
}
}
$i = $i - 1
if($error.Count -eq 0 -Or $i -eq 0) {break}
Start-Sleep -Seconds 30
}

Workarounds

Workaround 1: Create a startup item

Note This workaround works only for the device that has network access at logon. If the device has not established a network connection by the time of logon, the startup script won't automatically reconnect network drives.

Copy the script file (MapDrives.cmd) to the following location:

%ProgramData%\Microsoft\Windows\Start Menu\Programs\StartUp

Copy the script file (MapDrives.ps1) to the following location:

%SystemDrive%\Scripts\

A log file (StartupLog.txt) will be created in the %TEMP%\ folder.

Log off, and then log back on to the device to open the mapped drives.

Workaround 2: Create a scheduled task

Copy the script file MapDrives.ps1 to the following location:

%SystemDrive%\Scripts\

In Task Scheduler, select Action > Create Task.

On the General tab in the Create Task dialog box, type a name (such as Map Network Drives) and description for the task.

Select Change User or Group, select a local user or group (such as LocalComputer\Users), and then select OK.

Select the Run with highest privileges option.

On the Triggers tab, select New, and then select At log on for the Begin the task field.

On the Actions tab, select New, and then select Start a program for the Action field.

Type Powershell.exe for the Program/script field.

In the Add arguments (optional) field, type the following:
-windowsstyle hidden -command .\MapDrives.ps1 >> %TEMP%\StartupLog.txt 2>&1

In the Start in (optional) field, type the location (%SystemDrive%\Scripts\) of the script file.

On the Conditions tab, select the Start only if the following network connection is available option, select Any connection, and then select OK.

Log off, and then log back on to the device to run the scheduled task.

Workaround 3: Group Policy settings

If the mapped drives are defined through the Group Policy settings, update the action of the drive maps to Replace. This will delete the existing mapped drive and create the mapping again on each logon. Any settings on the mapped drive that are changed from the Group Policy settings will be lost on each logon. You may also have to run the gpupdate command (together with the /force parameter) to update the Group Policy settings.
Click to expand...

Source: https://support.microsoft.com/en-us/...0-version-1809

Windows 10: How can I use the local group policy in windows 10 to map a network drive persistently

How can I use the local group policy in windows 10 to map a network drive persistently

How can I use the local group policy in windows 10 to map a network drive persistently

How can I use the local group policy in windows 10 to map a network drive persistently

How can I use the local group policy in windows 10 to map a network drive persistently - Similar Threads - local group policy

How can I make a created local user group appear in the Local Group Policy?

How can I make a created local user group appear in the Local Group Policy?

Mapping a network drive using a local network

Local group policies

How to map a Drive using Group Policy Preferences on Windows 10

Windows 10 - Local Group Policy (PowerShell)

local group policy

Deploy Printer on network using local group policy (Windows 10 Pro Laptop)

Wireless Network (IEEE 802.11) Policies in local group policy ?