Default user login scripts overriding container login script 6.5

[dgfletcher]

I moved a client from Netware 4 to 6.5.
It is a small client with 10 stations.
The container login script merrily sets up its mappings just as expected, but then the DEFAULT user login script trashes them and sets up it's own mappings.
Before I figured out what was going on I went ahead and ran to each station to have Windows do the mappings. This was a nuisance.
What was Novell thinking when they introduced this behavior?

 

[marvhuffaker]

That's normal behavior, even with NetWare 4. It's also a very common thing with an easy solution.

Put this at the top of the container script: NO_DEFAULT

The deal is this, The container script always runs. Then the user script runs. If the user script is empty, then the default script will run. Putting in NO_DEFAULT in the container script will prevent the user script from running.





Marvin Huffaker MCNE, CNE
Marvin Huffaker Consulting

http://www.redjuju.com

 

[marvhuffaker]

I meant to say that NO_DEFAULT will prevent the DEFAULT script from running if there is no USER script.

Marvin Huffaker MCNE, CNE
Marvin Huffaker Consulting

http://www.redjuju.com

 

[dgfletcher]

Thanks. I misinterpreted the documentation to mean that no_default meant to skip the container login. Which doesn't make sense, but maybe I was tired. I guess the default user login script in versions 3,4,5,6 always coincided with what my clients needed! I never noticed it executing at all.