I created a bug report in the BETA forum - see this post.
It almost seems that Kix32 is checking for:- @SCRIPTDIR\@USERID.kix (works)
- @CURDIR\kixtart.kix (works when both script and exe are in the CURRENT folder, but since the NetLogon share isn't the current folder during logon, it fails at logon.)
This broke in 4.60 but was partially fixed a few releases back. Since most of us updated the login profile to read "Kix32.exe kixtart.kix" and simply tested the way Mart and I did, we assumed that it worked. My AD still has the full spec.
Clearly, this is still broken from the perspective of a logon process using Kix32.exe alone. Our script handles the user-specific script internally via a {UserID}.ini, but others who depend on this user-specific script feature are impacted by this bug.
Glenn
_________________________
Actually I
am a Rocket Scientist!
