Windows 10: Microsoft Policy change to "Update" for mapping network drives, when previously it was...

Daybreak0 · Oct 1, 2019

All - I was experiencing problems with blank pages in my PDF's when viewing them in my software Nuance Power PDF and also Nitro Pro PDF, and when searching I found that the same problem was occurring in Acrobat PDF software.

Someone on Acrobats forums who were having problems with other tax software which had started crashing had spent hours and hours trying to fix the problem reported this -

"Group Policy was previously using "Replace" to map network drives. Apparently Microsoft changed the way that Replace behaves via Group Policy on Win 8, Win 10, and Server 2012 machines and now says to use "Update" to map the drives."

When they changed group policy to make it "Replace" instead of "Update" they no longer had problems with their Tax software crashing.

Subsequently they no longer had problems with blank pages in their PDF either.

However I believe this problem goes way further than just the above.

I use a NAS for all my files, with mapped drives to different folders on my NAS. Quite often -

* I lose the mappings with an image of a cross coming up over the drives. however all I have to do is click on them to restore them.

* I am the only one that ever uses my files, but I can open one up, make changes and when I go to save it tells me someone else is using the file (normally when in compatibility mode).

* my PC slows down when using my NAS especially with PDF files, where they like freeze for a minute or longer.

Now possibly it is something else, but I don't believe so.

So my question is, as the Acrobats forum solution did not include any instructions on how to change group policy, how do I change group policy to Replace when mapping network drives. I really need a step by step.

I am running Windows 10 (not pro or anything) on a 64 bit machine

Thank you.

:)

DMyr · Oct 1, 2019

Trouble Mapping Network Drive

I have a WD NAS drive connected to my router and have mapped it on three of my computers. I just setup another laptop with Windows 10 and have updated it to 1809 and when I tired Mapping a network drive nothing is displayed in the browse window except the
computer I am currently using. The drive is shown under network locations in File Explorer but not when you select map network drive and browse. I right clicked on the drive and selected properties and noted the IP address and went back into Map network drive
but instead of selecting browse I entered the IP address but it still does not map the drive. The strange part is if I go to any of the computers that already has the network drive mapped and select Map network drive and select browse none of those computers
show the drive either but you can select the mapped drive in the drive list in file explorer and it works just fine.

I have read several articles both here and elsewhere and tried the suggestions but nothing works. Network discovery is turned on as is file sharing and also checked if all three boxes under SMB file sharing support in Windows features were also checked and
they are. I have mapped several computers to several different drives over the years and anytime the drive was not listed it was always easy to go into Network Sharing Centre and find the problem but everything seems to be as it should so would appreciate
if someone can suggest something I may have overlooked.

Thank you

Isha Soni · Oct 1, 2019

Cannot add/change drive letter in disk management or map network drive.

Hi,

Thanks for the update on the issue. try these methods and check.

Method 1: I would suggest you to change to the following options for
both the systems (Main PC and Set-top PC) on the network in the
advanced sharing settings (OpenNetwork & Sharing Center
> Change Advanced Sharing settings):

- Turn on Network Discovery

- Turn on file and printer sharing

- Turn on sharing so anyone with network access can read and write files in the public folders

- Turn off password protected sharing

Now, try to map the drive following these steps:

Press Windows key+E key on the keyboard.

Click Computer (above) and click on
Map network drive from the options given under the address bar.

In the Drive box, click the drive letter you want to use.

In the Folder box, type
\\server\share, where you can type the IP address of the drive to be mapped. For example, if the IP address is 192.168.6.xxx, you can type
\\192.168.6.xxx.

Click Finish.

Method 2:

Try to ping the IP address from the Run command. Refer to the following steps:

Press Windows button and
R key

Type in the IP address of the drive to be mapped, e.g., if the IP address is 192.168.6.xxx, you can type
\\192.168.6.xxx.

Click OK.

Check if you are able to open the network drive.

Method 3:

If the methods do not help, try to rename the
hosts file in the drivers and check if you are able to connect to the network drive.

Click Windows key and File explorer.

Go to the location C:\Windows\System32\drivers\etc.

Rename the file hosts to
hosts.old and close the window.

Restart your computer.

Hope this information is helpful. If the issue still persists, please post back for further assistance, we'll be glad to assist you.

_______________

Thanks & Regards,

Compumind · Oct 1, 2019

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: Microsoft Policy change to "Update" for mapping network drives, when previously it was...

Microsoft Policy change to "Update" for mapping network drives, when previously it was...

Microsoft Policy change to "Update" for mapping network drives, when previously it was...

Microsoft Policy change to "Update" for mapping network drives, when previously it was...

Microsoft Policy change to "Update" for mapping network drives, when previously it was... - Similar Threads - Microsoft Policy change

Map network drive

Network drive mappings

Mapping Network Drives

Mapping Network Drives

Mapping a network drive

Is there a way for Windows to not search for previously mapped but offline network drives...

Mapping a network drive

Map Network drive

Map Network Drive