Just an FYI - this is where our Universal Login Script is very strong..

You can specify a list of groups with modifiers to control access to a resource, in this case, the Z: drive. Here are a couple of example group configurations for Group Authorizations
 Code:
GROUPS=group1,Group2           ; Map if member of any group
GROUPS=+,group1,Group2         ; Map if a member of ALL groups
GROUPS=+,group1,!Group2        ; Map if a member of of Group1 and Not Group2
GROUPS=+,Group2!               ; Map for all, but DO NOT Map if a member of Group2
These options are supplemented by User OU, Computer OU, Subnet, Site, and User-specific authorization logic. Many of these can be combined with Value Rewrite, so you can replace a subnet, OU, ComputerOU, or UserID with all or part of a UNC path. For example, you might have 50 departments in Division 1, each in a unique OU. Rather than creating 50 IF or CASE statements, you create one resource, with the resource path like this:
PATH=&OU:DeptLookup&

This tells the script to obtain the User's OU, use it to lookup the path to be mapped from the table called "DeptLookup".
In the DeptLookup section, you simply write
 Code:
Dept1=\\server1\share1
Dept2=\\server1\share2
:
Dept50=\\server3\share18
where "Dept##" is the OU name of each department. The huge advantage of this is that as departements are added or removed, you simply update the lookup table - no more coding, eliminating potential login script problems that can affect the entire company.

This Kix-based script can be downloaded for free with a full user manual and configuration examples from our web site.

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