Disconnected mapped network drives
A strange situation that has suddenly occurred. From what I can tell we have not changed anything to cause the issue. Server is a Windows Server 2016 standard. The clients are Windows 10 x64. When pcs first boot in the morning, one of the three mapped drives has a red X in the drive mapping when viewed in file explorer. If you double click the drive letter you can still access the contents. However, the red X never goes away. The only way to rectify the situation is to manually disconnect the drive. Which from what I have seen doesn't actually remove it from the file explorer view. However, if you then reboot, then the drive mapping appears normal. In addition, there was once instance where suddenly in the middle of the day, the red X reappeared for one user. This has been going on for about a week and a half. The worst part of it is that the Quickbooks 2017 application does not seem to like the red X situation. If the drive mapping has the red X, then Quickbooks will not let users open any of the datafiles on the server. However, once the drive is disconnected and the pc reboots, Quickbooks works fine. I am looking for any advice as to what could be causing this issue and how to correct it.
ASKER
If I try to delete the drive mapping (ie. net use /d), it disconnects the drive but the drive mapping still appears in file explorer until the system is rebooted. I also setup a group policy to delete the drive mapping but it does not seem to have helped the situation.
You need to turn off persistence as the drives are staying mapped and new ones have different mappings.
Another way is to have a desktop icon that runs the script to map folders. "Connect Folders" and then have logoff script that disconnects the folders that runs on logoff or shutdown.
ASKER
The issue is if I attempt to delete the mapped drive it doesn't disappear from file explorer until the computer is rebooted. There users are having to reboot a second time every morning. That is the issue I need to fix. In addition, I don't understand what is causing the issue in the first place.
It is not an issue with Windows 10 and not with Server 2012. We have not yet implemented Server 2016.
I think the issue might be in your policies or scripting but I am not sure where you should look.
I think the issue might be in your policies or scripting but I am not sure where you should look.
Are you mapping drives by script or GPO? If you're using GPO, then you can try changing the policies that go the drive mapping from "replace" to "update"
BTW - You can try running this on the server as well:
BTW - You can try running this on the server as well:
net config server /autodisconnect:-1ASKER
I am mapping the drives using a login script
Try removing Login, Logoff scripts entirely, and build a batch files (NET USE commands) that you run to map and disconnect folders.
See if that works.
See if that works.
Try the command I've already suggested first. If that doesn't work, then I recommend going with GPO. You could have something going on with when there's a policy update that causes drives to get knocked off during the day. I could understand the red X coming up sometimes at logon because of timing issues, but it certainly shouldn't continue to stay there.
Also make sure you do not have a script in the Server (normal) AND a Windows 10 Logon Script (local to Windows 10) as well. That could easily create the conflict you have.
Please scrap using logon scripts/batch files altogether !! They are too hard to manage over time.
Use Group Policy
https://technet.microsoft.com/en-us/library/cc770902(v=ws.11).aspx
Be sure to read comments at bottom of that link too.
Use Group Policy
https://technet.microsoft.com/en-us/library/cc770902(v=ws.11).aspx
Be sure to read comments at bottom of that link too.
Open Sync Center and check if these drives are set to store content offline
ASKER
I used group policy to map drives but the drives keep disconnecting every during the course of the day. Being that we are an IT company, I have other clients that have reported similar type results recently. Could there be some Microsoft update that is causing this? This seems to be a new issue in the last couple weeks.
How is your policy set up, to replace or update?
ASKER
Policy is setup as replace.
ASKER
Offline files are disabled
Change it to update.
ASKER
Why would they disconnect in the middle of computer operation. Once the the user is able to get the drives remapped, there are reports that the drives disconnect during the course of the day.
Being that we are an IT company ..... Could there be some Microsoft update that is causing this?
I would open a case with Microsoft as this may be a Server 2016 issue. It is definitely not a Server 2012 issue.
I would open a case with Microsoft as this may be a Server 2016 issue. It is definitely not a Server 2012 issue.
ASKER
The problem I have with other clients are running Server 2012 R2. Plus I have other clients running Server 2016 without any issues (as of yet)
I have lots of computers (Windows 10) at several clients all with Server 2012. Zero disconnects.
I do suggest contacting Microsoft to see if they can determine how the policies you have are causing this issue.
I do suggest contacting Microsoft to see if they can determine how the policies you have are causing this issue.
ASKER
The odd thing is until I created this post, we were not using group policies (small 5 user network). Nothing in particular was changed prior to the problem occurring.
Take a new computer, pre-create computer account in OU that has no GPO applying. Join it and link back policies until Edge breaks (assuming it works after domain join)
I had come across particles that gave some ideas tie to things like update vs replace, as well as a refresh time in terms of updating policy changes.
ASKER
Shaun,
Can you explain better?
Can you explain better?
Did you run the command net config server /autodisconnect:-1 on the server yet ??
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Did you run the net config command ??
ASKER
Watchguard bug
I always just delete all mappings: NET USE X: /Delete for all X.
Then by script or however you map, Delete the drive (NET USE T: /Delete) and then Map the drive. (NET USE T: \\server\folder).
Make sure folders are mapped and not just browsed. Browsing for network shares can also kill the QB connection.