[lizard]

I'm a dev and had created an uber nt logon script. This script performed flawlessly. On Win 2K clients. Performed sort of spotty on XP clients. I pulled much hair out over this problem. The IT Manager and I went back and forth on this for several days.

He finally found something about "lazy authentication" on the web. Just did a brief search and didn't hit anything real quick, BUT, he changed a registry setting for AD and the problems went away. Might be the above solution. Like I say, I wasn't the one that found it.

In the big scheme, apparently XP sometimes just checks local settings and such and lets things proceed - without doing things like running new or changed scripts OR creating new profiles.