mapping network drives upon startup

[dbinphilly]

I have a number of computers using Windows 7 which share network drives. Some have application shortcuts that are using mapped drives.

When the computers are booted, some do not remap the drives - an 'x' is next to the drive letter if you click on 'Computer'. This is a problem for those who are using shortcuts to start their mapped programs, since the mapping is not active.

Is there a way to insure that the mapping is activated upon start up?

 

[MilesAhead]

Instead of using the setting in Explorer to remap the drives on startup you can use a .cmd batch file with a delay. Here's an example of one with a 20 second delay. The number is in milliseconds. For a 10 second delay change 20000 to 10000 etc.. This gives the network time to connect before trying to map the drives.

( In a command prompt type: net use /help for switches )

ping 192.0.2.2 -n 1 -w 20000 > nul
net use x: \\host\shaer
net use y: \\host\share

Edit: put a shortcut to the cmd batch file (MapDrives.cmd or whatever) in the startup folder for each machine.

Edit: the address 192.0.2.2 is guaranteed not to exist. This forces the ping to wait until the set time-out(the -w switch)

 

[chev65]

I have a number of computers using Windows 7 which share network drives. Some have application shortcuts that are using mapped drives.

When the computers are booted, some do not remap the drives - an 'x' is next to the drive letter if you click on 'Computer'. This is a problem for those who are using shortcuts to start their mapped programs, since the mapping is not active.

Is there a way to insure that the mapping is activated upon start up?

I've worked on this problem quite a few times in the past. There are two different methods to ensure that mapped drives connect on boot up.

There is a group policy setting that may help, this assumes you are using the Pro, Ultimate or Enterprise versions. If you are using the Premium version then use the second method as there is no group policy.

Start > Run > type "gpedit.msc" (without quotes) click ok.

Local Computer Policy > Computer Configuration > Administrative Templates > System > Logon > Always wait for the network at computer startup and logon

set this to Enable then reboot.


Or you could try adding the credentials from the server.

1. Go to Control Panel -> All control Panel Items -> Credentials Manager

2. Next to the heading "Windows Credentials" click on the link "Add a Windows credential".

3. Enter the name of your server and the appropriate credentials, reboot and check for mapping.

You might also want to set up a DHCP reservation for the local IP's or use static IP's so they don't change.