Welcome to KORG!

Our login script can do what you're looking for with a single INI file. We use something called Value Rewrite to change some or all of the UNC path that the resource maps to. There are 9 ways to handle the rewrites - User, User:Lookup, OU, OU Lookup, ComputerOU, ComputerOU Lookup, AD Site, AD Site Lookup, and Subnet lookup. Four of these simply replace a macro in the UNC path with the UserID, OU, Computer OU, or AD Site values, while the others actually look up a replacement value in a table. This allows us to, for example, have one definition to map the S: drive with 430 unique paths, for department-specific share paths, one per departmental OU.

Since we started offering commercial support, we no longer distribute source code to the login script, but you might get some ideas from the user guide on our web site. Of course, you could try the script itself, too.

Based on my experience, a central database or config file might work well in a LAN environment, but would likely suffer considerable performance degradation over a WAN connection. At one client with many remote retail locations, the login script they used took as much as 80 seconds to complete using an Access back-end on the WAN. Implementing our script brought the LAN time down to 3-4 seconds, and the WAN times to around 12 seconds (256K F/R connections). This is based on 30 disk resource checks, 7-9 being mapped, 2 printer connections, 1-2 message files displayed, and 2 external commands run (set the background w/ BGInfo, and verify/update a desktop icon which links to the intranet.

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