Using NAL Application Objects to Map/Assign file rights....

[Vidanon]

Hello

Not sure if this is the right group or not, but....

We are using NAL Application objects to map drives (via script), and
assign file rights for users. Normally we would use groups, but since
we have to map the drive anyway, we decided to use the App object,
instead of standard group assignments.

Does anyone see a problem in the foreseeable future, or even now by
doing it this way ? I heard talk at one point of Novell using file
rights on App Objects just until the app is launched, then the rights
would disappear. Does an App object use anymore resources, or take
longer to replicate than a standard group....??

Thanks...

Vid

[Duane Fish]

How many users/groups do you have?

[Vidanon]

Thousands of users... Normally the shared drive would
be mapped in the login script. This is for users that need
additional shared drives, so we're not exactly sure how
much as of yet. Right now on the normal shared area,
we do the rights by group, but we'd rather have just one
way of assigning rights. Mixing groups, and Application
object rights will get confusing down the road.... We
could still use the Application object to map the drive,
and then the group to assign the file rights, but that is now
assigning 2 objects per user....

[Duane Fish]

What I've done in the past that's helped me:

- Use the Login Script to map / give rights to the vast majority of
users that are common. For example, if everyone needs an X: drive
mapped to a common database, then the Login Script would be the best
place for it.

- NAL would be used for everything else that NAL needs in order to
run.
Of course, you need to document this so that if UserA needs WordPerfect
and you map it to Drive M:, and then create a NAL that was created for
Drive M: and UserA happens to be added to that group, then that would
cause problems.

As long as it's done with proper planning, I don't see a problem doing
it that way.

[Vidanon]

I guess its also more a conceptual thing, because its
not App related. Its just shared drive information...
Every one gets a drive M: for shared.... But Drive M:
could be unique for specific groups of people. Its when
those people need access to another group of peoples
shared data. We would use the NAL object to map the
X: drive to this area, then have that NAL object also
assign the rights... Realistically, though, there may already
be groups available that have rights to those directories....

On Sun, 25 Jan 2004 15:17:09 GMT, Duane Fish

[Chris Denby]

I have seen rights as assigned by Apps be unreliable, especially in revoking
rights after the fact.

Not a recommendation against app rights, but watch for it.

"Vidanon" <vid...@hotmail.com> wrote in message
news:5is7101tg7rohr4aj...@4ax.com...

[Vidanon]

Thanks...

I saw a TID on that (2953015)...
Wasn't sure if it was 'fixed' or not....