Roaming Profiles - map drives depending on subnet

[Guest]

We have 2 servers in 2 different locations and 2 different subnets. All are
part of the same domain.

Users on serverA map an F drive to \\serverA\apps

Users on serverB map an F drive to \\serverB\apps

If a user who normally logs onto ServerA logs onto ServerB, we want the
correct F drive to be mapped.

Can a profile or logon script be setup so thet a drive letter will be mapped
based on the subnet the user logged on to ?

 

[Herb Martin]

We have 2 servers in 2 different locations and 2 different subnets. All
are
part of the same domain.

Users on serverA map an F drive to \\serverA\apps
Users on serverB map an F drive to \\serverB\apps

If a user who normally logs onto ServerA logs onto ServerB, we want the
correct F drive to be mapped.

Which is "correct"? The same as the logon server (my guess)
or the original one the user normally used?

Can a profile or logon script be setup so thet a drive letter will be
mapped
based on the subnet the user logged on to ?

Sure. You can do this a couple of ways

If the content is precisely the same (AND you will keep it
synchronize either manually or using the provided automation)
-- you can perhaps benefit from a DFS share here place the two
subnets into different sites. (The only weirdness might be if
the two subnets are in the same LAN you would be using Sites
not for their obvious role across a WAN, but rather to control
preferred logon and preferred DFS to the same subnet.)

But for doing precisely what you asked (with same server as
logon server used) you could just map the drive from a batch
file in a GPO using either a Site specific GPO for each OR
merely using the environment variable %LogonServer% in the
UNC path.

 

[rvalstar]

DFS can be a pain.

If you look in the env variables, (Start\Run\cmd then type Set), is the
LOGONSERVER correct for each workstation on the differing subnets? If
so, map to \\%LOGONSERVER%\apps

Otherwise, we'll have to try something a bit more tricky

Rick Valstar
Star Consulting
r + last name + at + gmail + dot + com

 

[Herb Martin]

DFS can be a pain.

Not if you understand it and use it as intended.

If you look in the env variables, (Start\Run\cmd then type Set), is the
LOGONSERVER correct for each workstation on the differing subnets? If
so, map to \\%LOGONSERVER%\apps

You replied to my message but seem to be repeating
one of the several recommendation I already gave.

 

[rvalstar]

Sorry about the repeat. My mind wandered off somewhere in your
explanation.

Cheers,

Rick

 

[Jerry G]

Desktop Authority by ScriptLogic makes this a snap. You can get very
granular with applying settings such as drive mappings, and apply them
by subnet. It eliminates the need to use roaming profiles, and it will
eliminate the need for this to be scripted. Check it out at:
http://www.scriptlogic.com/products/DesktopAuthority/

Desktop Authority is the perfect answer for roaming profile issues,
since it eliminates the need to store user configurations in a user
profile. It eases the task of redirecting all of the folders containing
the user's environment which are traditionally stored in the profile.
For example, Desktop Authority makes it easy to redirect the user's
desktop folder, My Documents, web cookies, favorites, etc. to a central
location such as the user's home directory. With this arrangement,
the user's environment always "follows" them, without the need
for a roaming profile.

Hope this helps!



Ray Brown wrote: