• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

Mapping Drives on Wireless

M

Maglio

Weaksauce
Joined
Feb 15, 2008
Messages
64
where i work, we have quite a few laptops that connect to the network. we run a script at log on that basically maps all necessary drives for the user. the problem is that when people try to log on wirelessly, the drives don't map because the wireless doesn't start up right away. it just skips the mapping function. is there a way that windows will automatically connect to wireless at log on? it seems like kind of a big pain if microsoft didn't include some sort of functionality like that for businesses.

Maglio
 
You can set up the wireless connection to auto connect when it detects the wireless network however it still may not map the network drives a lot of the time. Where I work we just run a little drive mapping script to map the drives once the user is logged in through Active Directory.
Also I have found that if you have the laptop hardwired to the lan, then start up the wireless connection andunplug the network cable that the drives will usually map fine the next time, if they don't then my users run the map script.
 
so basically they have to click something to map the drives? we have something like that here, but we are trying to figure out/find a way to have the drives map automatically. we authenticate to AD as well, but is there a way we can tell when the machine actually connects to the wireless network?
 
You can have a task that runs like 15/30/whatever seconds after they log on that runs the script to map the drives
 
Jay_oasis said:
you could add Wait to the script
Click to expand...

we thought about this too, but some of our machines take a long time to boot up (30 seconds to a minute...sometimes a lot more depending upon how much crap the person has installed) and it would be hard to come up with a consistent time that it would map for everyone.
 
the other issue is that the batch file is stored on a server. so the batch file doesn't even run when the person logs in. (I just found this out). the batch file is set in AD to run, not locally.
 
this is going to have to be done using a .bat file on the local PC

Code: 
:: -----Map.BAT------
@ECHO OFF
PING www.hexus.net -w 10000 | FIND "TTL" > NUL
IF NOT ERRORLEVEL 1 (
NET USE X: \\your\path /PERSISTENT:NO
ECHO Connection to NetworkDrive complete.
) ELSE (
ECHO You are not connected to the internet, cannot connect to NetworkDrive at this time.
)
:: -----Map.BAT------
 
What's th ereal issue just wirless connection timming ? Does the machine actually conenct to wirless befor authitcation ? If so you can set a GPO to tell the machine to always wait for network.
 
it doesn't connect to wireless before authentication. that's the problem. we are trying to figure out a way to set wireless to activate first after log in and then run a batch file from AD.
 
What I do is setup my clients laptops while plugged into the network. This way the domain users local profile is properly setup while connected to the server. The login script also gets run. Windows does a pretty good job of remembering the mapped drives from the login script, so in future days, you'll see when the user logs in via wireless...it will remember those mapped drives and they'll be there.
 
You must log in or register to reply here.
Back
Top