New-SmbMapping -LocalPath $MappedDrive.LocalPath -RemotePath $MappedDrive.RemotePath -Persistent $True $MappedDrives = Get-SmbMapping |where -property Status -Value Unavailable -EQ | select LocalPath,RemotePath The file should be run at a regular but not at an elevated command prompt because it should be run at the same privilege as Windows Explorer: $i=3 PowerShell -File "%SystemDrive%\Scripts\MapDrives.ps1" > "%TEMP%\StartupLog.txt" 2>&1 The file should be run at a regular but not at an elevated command prompt because it should be run at the same privilege as Windows Explorer: PowerShell -Command "Set-ExecutionPolicy -Scope CurrentUser Unrestricted" > "%TEMP%\StartupLog.txt" 2>&1 To do this, create two script files, and then use one of the workarounds, as appropriate. Currently, you can work around this issue by running scripts to automatically reconnect mapped network drive when you log on the device. Monitor the mapped drive topic in the WindUpdate History KB 4464619. Microsoft is working on a resolution and estimates a solution will be available by the end of November 2018.
In the notification area, a notification displays the following message:.Mapped network drives are displayed as Unavailable when you run the net use command at a command prompt.In Windows Explorer, a red X appears on the mapped network drives.You experience the following issues in Windows 10, version 1809: This article provides a workaround for the issue that mapped network drive may fail to reconnect in Windows 10, version 1809.Īpplies to: Windows 10, version 1809 Original KB number: 4471218 Symptoms
0 kommentar(er)
