Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 531
  • Last Modified:

Windows 7 could not reconnect all networks drives

Been searching all over the net on Windows 7 could not reconnect all networks drives issue. I can find a real solution and wondering if anyone else has some suggestions.

I have found a number of sources but so far nothing works. Including this
http://community.spiceworks.com/topic/388905-windows-7-could-not-reconnect-all-network-drives-at-boot-up 

It is a Windows server 2012 R2 with 10 Windows 7 workstations. Brand new server and hardware and wiring in the building.

The mappings are done via a GP
0
Gerhardpet
Asked:
Gerhardpet
  • 4
  • 3
1 Solution
 
RizzleCommented:
So when the user logs in can they not access the mapped drives?

This happens in our environment but we check the users mapped drives they are ok! so it's just a false report more than anything.

Sometimes it can be due to duplicate drive mappings, for example you could be mapping the users home drive in AD via their home drive path and then via the login script/GP Preferences this also maps the users home drive.

Maybe this may help?

https://social.technet.microsoft.com/Forums/windows/en-US/48f5ca04-6561-404d-b3ab-897320593aa6/could-not-reconnect-all-network-drives
0
 
GerhardpetAuthor Commented:
My problem is that we have an older application that requires the mapping. If not the application fails to start. Users don't know what to do then.
0
 
Rob GMicrosoft Systems EngineerCommented:
There are two changes in windows 7 that cause this..
1. The original Group policy (Default) setting in XP was to wait for the network before login when on a domain. In windows 7 it is not the default, so that causes the network drives to not be available till you are logged in and group policy is applied.
2. The login scripts for XP do not work on windows 7 the same as in windows XP the drive was removed on shutdown, but in 7 it is removed on boot if the drives are not persistent... (In xp if the drive was set to reconnect, it was removed on shutdown, in 7 it is removed on boot up, before being connected again, causing that stupid "drive not available issue" till group policy is applied.

The work around i found that works,
Use a script, but script that all mapped drives are removed before being added, and set the script to have a 15 second wait. (along with changing the Group policy to wait for the network, before logging in.
(Caution, can cause issues with laptops)
0
Fill in the form and get your FREE NFR key NOW!

Veeam is happy to provide a FREE NFR server license to certified engineers, trainers, and bloggers.  It allows for the non‑production use of Veeam Agent for Microsoft Windows. This license is valid for five workstations and two servers.

 
GerhardpetAuthor Commented:
I found an easy solution for this. In the GPO I just set it to delete the mapped drives first and then remap them

I did this under User Configuration > Preferences > Windows Settings > Drive Maps

My order is delete and then create

Hope this will help someone else

@Rob G: your solution would be similar except using a script. You gave me the idea to try my solution so i will award you the points
0
 
GerhardpetAuthor Commented:
Also see my own solution
0
 
Rob GMicrosoft Systems EngineerCommented:
Gerhardpet,
Assuming you did this..

net use * /D /Y
net use x: \\Servername\drive$\folderName /P:Y

or

net use * /D /Y
net use x: \\servername\Sharename /P:Y
0
 
GerhardpetAuthor Commented:
I don't use a script

I went here in the GPO User Configuration > Preferences > Windows Settings > Drive Maps
0
 
Rob GMicrosoft Systems EngineerCommented:
You're going to want to make sure you have the policy set to wait for the network to come live if you do this through group policy, or you will still have this issue once everyone's policies get updated.. So if you made the change Monday, you'll probably start to see the original problem again sometime next week.. i believe it is 15 days till you start to cache again(WindowsXP or better).. Keep in mind, that on laptops, this is something that will likely require you to have two different policies.. As if you make that change, laptops who are not in the office will not be able to log into there machines once that policy is applied..
0

Featured Post

Visualize your virtual and backup environments

Create well-organized and polished visualizations of your virtual and backup environments when planning VMware vSphere, Microsoft Hyper-V or Veeam deployments. It helps you to gain better visibility and valuable business insights.

  • 4
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now