R
R A Peterson
<<
>If a user needs access to an executable, why not simply assign access in the policy to his id or group?
A user can develop/install software that is available to him, or just his group, without requiring the intervention of somebody with
Administrator level priviledges. The advantage of this is only really appreciated on large systems however, not your typical NT setup, I
certinaly think it is a non issue for control apps. >>
This is not generally so. most software requires registry changes which a typical user cannot do. i got so tired of having installs die on me that I
changed my normal login to be an admin as well. its too much hassle to have to keep logging off to install a piece of software.
>If a user needs access to an executable, why not simply assign access in the policy to his id or group?
A user can develop/install software that is available to him, or just his group, without requiring the intervention of somebody with
Administrator level priviledges. The advantage of this is only really appreciated on large systems however, not your typical NT setup, I
certinaly think it is a non issue for control apps. >>
This is not generally so. most software requires registry changes which a typical user cannot do. i got so tired of having installs die on me that I
changed my normal login to be an admin as well. its too much hassle to have to keep logging off to install a piece of software.