Login through Multiple Trees

[k3n85]

The situation I'm looking is to have students login through our tree, but use shared drives in which are accessed through a second tree. We would like to have information about who logs into our hall public comptuers without using the generic login account(s). We also need to be able to have the user have access to our ZEN application launcher. I am looking for any kind of solution to this problem, any insight would be great.

Hurdles:
We don't have student accounts on our tree. They exist on the school tree.
If a students authenticates to a school tree account how do we access that information w/o admin rights to that tree?

Suggestions:
Look at possible ways to "piggy back" tree logins in a new "lab login script."
Check into possible ZEN type options

T.I.A

 

[marvhuffaker]

Novell introduced a concept a while back where you have a ZEN tree that is separate from regular file / printing..

I never really bought into the idea but it's completely possible. I think it makes it more difficult to manage.





Marvin Huffaker, MCNE

http://www.redjuju.com

 

[andriod998]

T.I.A,

I've never really looked into if it's possible to have people login across tree's. I guess you would have to have seperate user accounts on each. I guess my question would be how come you have multiple trees to being with? I work in a medium sized school district and we have one large tree and OU's for our different buildings. Inside our OU's we have our printers, staff account, zenworks policy packages, etc.. We also have another OU inside each of our site OU's called "Student" and this is where all the student accounts are kept. When a student logs into a machine they have to use a username of "username.student" and this lets them login. Students login to the same file servers that our building staff does but they only have rights to the "student shared" and their home directory but this alows them to use our NAL and everything that we want them to use in their classes. We then use Zenworks and windows group policy to lock students out of whatever we dont want them to change. We have been doing this since our migration off NetWare 3.12 to 4.11 and it's worked for us very well with minimal service calls related to malicious re-configuration to machines that students login to. We also use zenworks quite a bit for imaging and stuff so if / when we do need to re-image a machine it can be done very easly and once the image is done printers are automatically re-installed and all this doesn't really require much intervention from me or any of my fellow "techies" here at the district..

Andy

http://www.tumwater.k12.wa.us/

asmith1@tumwater.k12.wa.us

 

[k3n85]

This is the hard part, where both Trees are for our University, there is one tree for all of campus (students, staff, etc) and then another account for Residence Life which is a different tree, with another set of shared drives not stored at the campus level, but hosted in our office (a different site). While we're still able to map drives for each user, this is only because the users exist on both trees. The problem being that the other Tree uses the registration process to the university which has every single person registered here, while we need just the students living in the residence halls. And at the moment the only way we could do this for each student would be to manually add/remove users.

 

[marvhuffaker]

Even the most complex environments can be facilitated with one tree. Yours, even a university, is no exception. If you configure your OU's correctly and strategically, you can provide users access to whatever resources they need.

Marvin Huffaker, MCNE

http://www.redjuju.com

 

[k3n85]

Yea, since our department hasn't been around as long they had everything implemented already, and when this dept. was created I guess the idea never came up and there wasn't a problem. We have just started talking w/ the campus wide IT about what options we have, and was just seeing if there was a way without having to migrate or share the load w/ our 3 novell servers & SAN.