Jump to content

Recommended Posts

Posted
We have a bunch of 8-year-old macs running OSX 10.6.8 (they are being run until they die) which are bound to AD. When any staff member logs in, their AD home folder gets mapped fine, their desktop shows fine too. However, when a student logs in, it fails to map their home folder. Moaning about it having been removed or can't be found etc. When the user logs in to a Windows machine there are no issues whatsoever so to me it can not be a permissions issue. Can anyone nudge me in any form of direction as to how this can happen?
Posted (edited)

im pretty sure this is a permissions issue on the shares

look at staff share settings on your server

see whats the difference

 

when I did ours I had to give read permission somewhere but cant remember for the life in me

Edited by round2it
Posted
im pretty sure this is a permissions issue on the shares

look at staff share settings on your server

see whats the difference

 

when I did ours I had to give read permission somewhere but cant remember for the life in me

Surely if the home folders map fine like they do on Windows machines, then it can't be a permissions issue? Unless Mac interprets NTFS permissions differently?

(There are 2 shares - staffdata for staff home folders & curricdata for student home folders. Share permissions are identical).

Posted

Home folders on OS X can be a tricky swine. We've had to do a few odd things, especially with versions after Snow Leopard.

 

We've had to enable the machines to create a local home directory (otherwise logons take forever or didn't work at all)

We've had to allow the students to read the root of the home area share (e.g. the whole home storage folder). This doesn't allow them to enter sub-folders other than their own due to our NTFS permissions.

 

Cross check your settings in the Directory Utility. Are your staff on a separate domain or child domain?

Posted
Home folders on OS X can be a tricky swine. We've had to do a few odd things, especially with versions after Snow Leopard.

We've had to enable the machines to create a local home directory (otherwise logons take forever or didn't work at all)

We've had to allow the students to read the root of the home area share (e.g. the whole home storage folder). This doesn't allow them to enter sub-folders other than their own due to our NTFS permissions.

Cross check your settings in the Directory Utility. Are your staff on a separate domain or child domain?

 

One of the requests from the resident teacher in the room is that students could still access work done on the macs on Windows machines (where software compatibility allows) so we're trying to avoid forcing them down the local home directory route.

I currently have "Traverse folder / execute file" & "List folder / read data" for "This folder, subfolders & files" on the route of the curricdata share. There are then separate folders in there for each intake year. Each intake year's folder then has the home folders for each user in that year group.

When checking one of those subsequent intake year folders, it looks like inheritance has been disabled so it is not getting the same Traverse & list permissions set at the level above.

 

 

FYI - I inherited this setup 2 months ago when I started the position.

Posted
If you make it so a local home directory is created it won't stop them saving files to the network, but it does add an extra step. We found it an acceptable compromise. They are told not to save locally!

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...