My login script provides a ton of diagnostic info. If you're willing to download and add it to your Netlogon share, it should provide enough info about the environment to possibly identify the problem without modifying your current script. See the link in my sig and browse to Products / Administrators Toolchest.
PM me with the following info and I'll create a basic config file for you to eliminate the learning curve and provide you with a 30-day demo license key (if needed):
# of domain controllers in your environment (4 or less requires no license).
List of resources to map - drive, UNC Path, Group(s) to control mapping (if any)
Do you want to unmap drives prior to mapping?
Any drives to exclude from the unmapping process?
If you can reproduce this with a specific user, update that user's profile to run the new script. Create a debug file in their user profile folder and debugging will be enabled automatically.
The debug file will identify the system environment, all groups the user is a member of, the OU that the user and computer are in, and much more. Then, for each resource being mapped the status of the authorization logic (group, site, OU, etc. memberships) and result of the mapping command will be logged. If it fails to map, this should point to the cause.
Welcome to KORG, BTW!
Regards,
Glenn
BTW - a client in Australia had an issue with no mapping on 3 of 200+ machines - by running this we were able to determine that the environment was corrupt during logon due to a system fault.
_________________________
Actually I
am a Rocket Scientist!
