As far as AFS is concern, Windows logon consists of following events: 1. password authenticate 2. establish User execution space 3. map previous mapped network drives.
The client cache manager determines who the current user is by querying the kernel for the owner of the user execution space. Once the owner is known then the client cache manager can then use the appropriate ticket for a SMB message. Which means you have to wait until user execution space is established before you can map network drives. Additionally the client cache manager can't get 'hooked in' via the logon script until after the kernel maps the previous mapped network drives. Mapping drives during windows logon won't work because windows will remap network drives when it establishes User Execution space. Global drive mapping should be done at the same time the cache manager does its drive mapping. Most users just add logon scripts to deal with their drive mapping. NOTE: the environment variable %username% is available at that time. James "Integrity is the Base of Excellence" _______________________________________________ OpenAFS-devel mailing list [EMAIL PROTECTED] https://lists.openafs.org/mailman/listinfo/openafs-devel
