Well, it only took 15 minutes on the front burner. The script now supports path rewriting by AD Site, User, OU, and network address.

Basically, if you have a computer with address 172.16.3.43 and a netmask of 255.255.254.0, the network address is 172.16.2.0. This calculated network address can be used as a lookup reference:
 Code:
[SubnetLookup]
172.16.0.0=\\server1\share\path
172.16.2.0=\\server2\share\path
in a format similar to my prior post. In this way, a Teacher would map server1 to the S: drive in one location, but map Server2 to the S: drive in a different location.

Another cool thing about path rewriting - the lookup doesn't need to include the share path - only the server, so if the resource record was
PATH=&SUBNET:SubnetLookup&\share
- and you had consistent share names at each location, only the server name would be replaced during the PathRewrite operation. This means that the same rewrite table could be used for multiple drive maps, reducing overall complexity.

I'll currently make Version 2.4.3 with SubnetRewrite capability available only by request until I've had sufficient time to test it - PM here or email from my web site if you want to try it out.

Glenn
_________________________
Actually I am a Rocket Scientist! \:D