N
Nick
How do I map a network drive based on current location.
Here's the setup.
Master AD servers around the area.
Then each location has it's own win 2000 sever that houses
users home directories and applications.
Each location has applications that only are stored
locally. Some of the people travel between locations.
So the mappings for one location, lets say f: = \\server1
\apps
Now that will work for the one location. But when that
person needs to go to location 2 then need that f: drive
mapped to f:= \\sever2\apps
My question is, how do you determine what your local
server is when you log into AD? Would you have to do this
by the IP range? And how would I map this based on that.
My orginal though would be for example in teh script. I
don't know what the script would be but here's the logic
behind it.
IF %IPADDRESS IS IN 192.5.6.* then map \\server1\apps
IF %IPADDRESS IS IN 192.5.7.* then map \\SERVER2\apps
Or something like that. So it would know what the local
server name is to map to.
Any thoughts?
Here's the setup.
Master AD servers around the area.
Then each location has it's own win 2000 sever that houses
users home directories and applications.
Each location has applications that only are stored
locally. Some of the people travel between locations.
So the mappings for one location, lets say f: = \\server1
\apps
Now that will work for the one location. But when that
person needs to go to location 2 then need that f: drive
mapped to f:= \\sever2\apps
My question is, how do you determine what your local
server is when you log into AD? Would you have to do this
by the IP range? And how would I map this based on that.
My orginal though would be for example in teh script. I
don't know what the script would be but here's the logic
behind it.
IF %IPADDRESS IS IN 192.5.6.* then map \\server1\apps
IF %IPADDRESS IS IN 192.5.7.* then map \\SERVER2\apps
Or something like that. So it would know what the local
server name is to map to.
Any thoughts?