Script is used to create system- and locationspecific profile-directory(and some additional directories) on the fly. When used in conjunction with interdomain-trusts the %m in logon-path ist resolved to the trusted domain controller (unwanted behaviour) and the %m in root preexec ist resolved to the name of the windows-client (wanted behaviour). logon path = \\%L\profiles\%U\%m root preexec = <script> '%m' '%U' '%a' '%L'
This is by design from what I can tell. The logon path is executed as part of the net_sam_logon() reply which is sent to the trusted domain controller. The preexec script is done when the client connects to an actual share. Not a bug per say.
(In reply to comment #1) > This is by design from what I can tell. The logon path is executed > as part of the net_sam_logon() reply which is sent to the trusted > domain controller. The preexec script is done when the client > connects to an actual share. Not a bug per say. Perhaps not a bug, but this renders %m useless for logon path, as all logon paths would be contain the domain controller instead of the client in case of an interdomain trust