- #MAPPED DRIVE KEEPS DISCONNECTING UPDATE#
- #MAPPED DRIVE KEEPS DISCONNECTING MANUAL#
- #MAPPED DRIVE KEEPS DISCONNECTING WINDOWS 10#
- #MAPPED DRIVE KEEPS DISCONNECTING WINDOWS 8.1#
- #MAPPED DRIVE KEEPS DISCONNECTING WINDOWS 7#
You said the drive mappings disconnect after 3 or 4 days? Was the server hosting the shares rebooted in this time? Or is this just happening in the middle of the work day? Are the workstations going to sleep? I've seen these things affect drive mappings and cause them to disappear and stop working. Switching to direct mapping may fix the issue. If you are mapping to DFS namespace, I've seen the same issues occur.
You didn't say if the mapped drives are using DFS or just regular network shares. Delete them out and let the logon script handle it. You might also review Windows Credential Manager and see if there are any saved credentials for any of the drive mappings.
You will have issues with the login scripts until these drives have been removed from the computer. If they still show mapped drives, they were manually mapped. You can test this by disabling their logon scripts, then logging into the computer. These saved settings then end up conflicting with the logon script. I've seen issues where the drive was mapped manually via Windows and set to reconnect at logon. It works, but it’s not ideal.In your login scripts, do you remove any previous mappings with a "net use * /d /y" command first before mapping the needed drives?Īlso, do you have the GPO set to run the login script syncronously?
#MAPPED DRIVE KEEPS DISCONNECTING MANUAL#
Disabling the background refresh seems to be the same as enabling the manual call-the-IT-guy refresh. Maybe they would have eventually been replaced, but users can’t wait to access their files once the old server is gone. What I discovered was that in this scenario, drive mappings were not replaced until I logged on with each user to each workstation and did a “gpupdate /force”. Under User Configuration > Preferences > Windows Settings > Drive Maps, I set the Action to Replace, also recommended in the comments.
#MAPPED DRIVE KEEPS DISCONNECTING UPDATE#
Update November 21, 2018įollowing the advice in some of the comments, while I migrated shares from one server to another, I set up the group policy Computer Configuration > Administrative Templates > System > Group Policy > Configure Drive Maps preference extension policy processing > Do not apply during periodic background processing: So far that seems like a one-time occurrence so I’m going to ignore it. Please click on the “More information” link. Group Policy Drive Maps settings might have its own log file. I did see one error on my client machine after changing the drive map policy:ĭescription: Windows failed to apply the Group Policy Drive Maps settings. It looks like the group policy refresh happens about every two hours. Lost connection 8/3 8:33am, group policy update finished 8:34am Lost connection 8/2 4:41pm, group policy update finished 4:42pm. Lost connection 8/2 2:42pm, group policy update finished 2:43pm. Source = GroupPolicy (Microsoft-Windows-GroupPolicy)Įvent IDs = 1501, 1503 (user policy completed, with or without change) Now that I know what to look for, I can see that a group policy refresh completed shortly after each disconnect. Confirming in the Event Logįor a while, I was keeping track of when the machine got disconnected from the server.
#MAPPED DRIVE KEEPS DISCONNECTING WINDOWS 8.1#
WARNING: As of the Windows 8.1 Preview if you set a drive mapping to “Remove” or “Replace” it will forcefully disconnect the drive and close any open files you have to that location. That one explains the background update principle and concludes with this: New Background Drive Mappings in Windows 8.1 There are several posts about the same issue under Windows 8.1, for example: In the Group Policy Object (GPO) where drive maps are defined, edit User Configuration > Preferences > Windows Settings > Drive Maps. The solution? Change the group policy to Update rather than Replace the drive mapping. As of Windows 8.1, the group policy refresh happens not only at logon but periodically in the background while users are working. It turns out that if drives are mapped in group policy and the policy specifies Replace, the drive will disconnect and then reconnect every time group policy is refreshed.
#MAPPED DRIVE KEEPS DISCONNECTING WINDOWS 10#
Finally I found this article:įollowing Windows 10 upgrade, mapped drives disconnect briefly One 2010 article talked about disabling SMB2 to solve app crashes, but you’d think SMB2 would be working by now. So something is wrong with the 2012 R2 Essentials server? Then I realized that other Windows 10 machines on the network were having the same problem. I was wondering if I needed to go back to Windows 7. The outages were very brief: I could immediately connect to the location again. If I had File Explorer open, it loses its location: One of my database programs relies on a mapped drive and keeps crashing. The most frustrating problem has been that mapped drives on my server frequently disconnect.
#MAPPED DRIVE KEEPS DISCONNECTING WINDOWS 7#
A few weeks ago, I upgraded from Windows 7 Ultimate to Windows 10 Pro.
0 kommentar(er)
