I was not able to get this working via a GPO.. Still have the same problem with everyone on Windows 10, even the fresh install of WIndows 10 did nothing.
To continue this discussion, please ask a new question. Get answers from your peers along with millions of IT pros who visit Spiceworks.
Best Answer. Change the drive to "Update" in group policy and the issue will disappear! View this "Best Answer" in the replies below ». Popular Topics in Windows Spiceworks Help Desk. The help desk software for IT. Track users' IT needs, easily, and with only the features you need. Learn More ». Determinist This person is a verified professional.
Verify your account to enable IT peers to see that you are a professional. Adam Gadoury This person is a verified professional. Caur Aug 21, at UTC.
Hmm, I'll have to look into those suggestions on Monday! Thank you all! Adam Gadoury wrote: Did you remap the drives and not check off "Reconnect at Sign in"?
Hi Pass, I'm going to try turning off the Turn off this device to save power option and see if that helps! Thank you! Sorry about the mess of 2 logins, mistake on my part. We investigated network issues, restarted switches, ran ping tests, etc, but nothing obvious showed up. The culprit was in fact caused by Group Policy settings whereby drive mappings were set to " Replace ". Since Windows 8, the system automatically runs GP updates in the background and will disconnect and reconnect the drive to replace it.
The fix is to find the responsible Group Policy object the easiest way to check is by running RSOP from the command line. Then edit the offending GPO and change the drive mapping action to " Update " and the issue will disappear! Credit to 'Shane' for posting the fix on Spiceworks community. Yes, thank you : No, sadly not :. For us, the issue began after moving from win7-pro to winpro. Our issue was a tad more severe than merely losing a mapped drive. We have client-side apps that have db-s on share drives.
The disconnect even for a moment screwed the app's access to that data. Our disconnects consistently occurred after about 20 mins of client idle time. File history is disabled. Winserver R2. No probs at all in win7. If you use this method, you may turn off the auto-tuning feature for the Server service.
To change the default time-out period for the autodisconnect feature of the Server service, open a command prompt, type the following line, and then press ENTER. The maximum value for this command is 65, However, these programs function normally before the drive is disconnected. For more information about how to increase the default time-out period, Server service configuration and tuning. Feedback will be sent to Microsoft: By pressing the submit button, your feedback will be used to improve Microsoft products and services.
Privacy policy. Skip to main content. This browser is no longer supported. Download Microsoft Edge More info. Contents Exit focus mode. Applies to: Windows 7 Service Pack 1, Windows Server R2 Original KB number: Symptoms On a computer that runs Windows 7 Service Pack 1, if you map a drive to a network share, the mapped drive may be disconnected after a regular interval of inactivity, and Windows Explorer may display a red X on the icon of the mapped drive.
Cause This behavior occurs because the systems can drop idle connections after a specified time-out period by default, 15 minutes to prevent wasting server resources on unused sessions. Resolution To resolve this behavior, change the default time-out period on the shared network computer. Method 1: Using Registry Editor Warning If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system.
0コメント