Users need to login to different containers than home container.

[zooluu70]

Work at a bank, and we have tellers that go from branch to branch. Rather than use a generic login for those users, I would like them to be able to sign in with their own username from their home branch. Now I understand that this can be done by having the users type in their full name .jdoe.branch1.bank.company, but this gives them the drive mappings to their home server. I want to know how to set the client to use the local server drive mappings. I only want the users home directory to be mapped back to the home server.

Thanks
Zooluu70

 

[marvhuffaker]

That's a difficult task because when they login, it will run the container script from where their userID is located, not the container script for the branch that they might be physically sitting in.

There is a utility that you can install on the client to do a contextless login (LGNCL.ZIP - look for it on Novell's site). This would solve the problem of having to use the full nds name.

As far as mapping to the local server, you might be able to setup an if/then in the login script that checks the network segment and maps to the servers accordingly. Not necessarily a quick or easy solution but if you work with it you should be able to get it to do what you want.

Marvin Huffaker MCNE, CNE
Marvin Huffaker Consulting

http://www.redjuju.com

 

[lgarner]

That's how I worked it out when we had that issue. In the "O" script I put if-then statements based on the network numbers, then included those scripts in the "OU" ones. That way you only need to tweak the script in one place. I don't know how it would perform if you have a lot of networks, though.

Also you can check the workstation's context. %REQUESTER_CONTEXT is the variable, I think. There was a little weirdness with that, though. I seem to recall that it got changed to the current user's context after a successful login so subsequent logins were messed up. Rebooting the PC after each logout solved it and wasn't too bad.

This worked fine, and also gave me a good way to avoid things like NAL when a user was dialing in.