novell Roaming Profile Folder security question

We are implimenting Novell here on Windows XP workstations, and I am going to utilize the roaming profiles component for backup purposes, and instructors that like to log in in classrooms and have all their files accessible (even desktop shortcuts)

Now, my initial thought was to create a profiles directory that is separate from the user's Home Drive, as to alieviate any potential wandering by users exploring their Home Drive.

So I have the folder created and designated for Roaming profile storage, but my question is what kind of permissions is needed?  On the /PROFILES folder should I make all users have File Scan?  Then under that you will have all the USERNAME folders, and each user should have trustee to that folder, correct?  Is there some automated way that those will be created, or each time a user's profile directory is created and populated am I going to have to apply trustee rights to it manually?

Or am I looking at too much babysitting of the security on these folders, and its just way easier to dump the profile to the Users's Home Drive?

Thanks
tfallertAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

PsiCopCommented:
<pet peeve>

"Novell" is a company. It makes a number of products, such as "SUSE Linux Enterprise Server", "Open Enterprise Server", "ZENworks", "GroupWise" and "Identity Manager".

You didn't write "Micro$oft XP", did you?

</pet peeve>
0
PsiCopCommented:
Given that Novell makes a number of products, what ones are you using to imlement your environment? Are you using the Dynamic Local User functionality of ZENworks to do the "roaming profiles"?
0
tfallertAuthor Commented:
Well I mean to say we are using the novell client and ZENworks (along with patchlink) on the desktop systems, and the servers, I dont actually administer, but they are I believe running SUSE Linux Enterprise.

Im setting permissions from within ConsoleOne, if that makes a difference.

I am using Dynamic Local Users, but not to do the Roaming Profiles.  the Roaming profiles is configured in the Windows Desktop Preferecnes in the User package
0
Cloud Class® Course: Python 3 Fundamentals

This course will teach participants about installing and configuring Python, syntax, importing, statements, types, strings, booleans, files, lists, tuples, comprehensions, functions, and classes.

ShineOnCommented:
Actually, as to your question, assuming these files are on an NSS volume, granting of filesystem trustee rights (not permissions - permissions are a Windows-ism) are only necessary on each user's directory, not the parent.  If you grant filescan to the parent directory to all users, unless you block inheritance of filescan at the parent they'll all be able to see each others' child folders and, by inheritance, all the files therein.  They wouldn't be able to open/read/change/delete or modify the attibutes thereof, but they'd be able to see they exist.

Any necessary rights to the parent directory would dynamically flow up the directory structure.  It is not necessary to grant any rights to the parent directory at all.

I think it'd be easier to dump the profile to the User home directory.  They should already be secure from other users; you'd just have to make sure they don't mess with their profile directories, which they'd be able to do in your planned scenario as well, if not as conveniently.
0
tfallertAuthor Commented:
Okay that makes sense.  so the users would only need Trustee on their Profile folder.  but the system doesnt automatically grant trustee access to those folders when it is created to drop the profile in, does it?

I havent ruled out using the Home Drive, I just am exploring this option before I do that
0
ShineOnCommented:
Actually, if you don't use the user's home directory, ZEN assumes that the directory you specify will be a shared directory for multiple users to share the profile stored therein.  That's what the documentation suggests, anyway.  It will not fill in the name of the user automatically as it would with the home directory.

So:  

If you do what you're suggesting rather than use the user's home dir, then for >each user,< you will have to 1) create the user's profile-storage subdirectory and 2) specify the full path to the subdirectory in the Desktop Preferences, Roaming Profiles.

I don't know whether ZEN or the C1 snapin would automatically grant rights to access the Roaming Profile directory or not, but I would assume not, which would add step 3) grant trustee rights to the user's profile subdirectory.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Novell Netware

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.