Probably the best way to go, rather than having many different scripts on a per user basis is to have one script that performs different tasks depending on the user running the script at logon.

For example, have one central logon script, called logon.kix. In User Manager, set all the users who will run a logon script to use "kix32.exe logon.kix".

The main script would have sections for all users, for seperate groups, and for individual users, using conditions and the INGROUP() function - something like this:

code:
? Welcome to test Kix script.
If InGroup("Domain Admins")
   ? "You are an administrator in this domain."
   Use x: "\\server\adminshare"
Endif
If InGroup("Application Users")
   ? "You are a user of the xxx application."
   Use y: "\\server\applicationshare"
Endif
If @USERID = "joebloggs"
   ? "You are user Joe Bloggs."
   Use z: \\server\usershare"
Endif

? "Logon script complete."
Exit
If you set up a test script like this and try logging on as different test users with different group memberships, you can see that you can handle different users and groups seperately from within a single script.

As far as possible I try to avoid having too many scripts, to make editing them easier - although I relax this for my admin scripts and functional scripts that are called by the central logon script itself. All in, however, I probably have less than twenty seperate scripts, in my Netlogon folder, which caters for over two and a half thousand users.

Hope this helps a little...
_________________________
================================================
Breaker