Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Pushing Proprietory Apps
0 views
Skip to first unread message
Trahsub
May 16, 2008, 10:25:02 AM5/16/08
to
In our environment, we try to limit administrative rights as much as
possible. What we're finding is that applications in some cases require
modify permissions to the associated registry and file system folders in
order to update, or run certain pieces of the program. The software vendor
assumes that all users of their app will have power users or administrative
rights. When we push the software with sms, the user still needs elevated
rights to the folders and registry keys in some instances when we take their
admin rights away. How do others handle these issues. We take the users
rights away to install software and use SMS to push it, then the users can't
run the app unless we change the acls are changed on the folders and files.
Can the acl changes be included in the package?
possible. What we're finding is that applications in some cases require
modify permissions to the associated registry and file system folders in
order to update, or run certain pieces of the program. The software vendor
assumes that all users of their app will have power users or administrative
rights. When we push the software with sms, the user still needs elevated
rights to the folders and registry keys in some instances when we take their
admin rights away. How do others handle these issues. We take the users
rights away to install software and use SMS to push it, then the users can't
run the app unless we change the acls are changed on the folders and files.
Can the acl changes be included in the package?
What are some other ways to automate this piece.
Thanks
Garth
May 16, 2008, 7:32:37 PM5/16/08
to
This can be done using Resource Kits and any software packaging software.
The biggest issue is finding the problems and then solving the issue. Once
you can do that creating pacakge is fairly simple.
The biggest issue is finding the problems and then solving the issue. Once
you can do that creating pacakge is fairly simple.
"Trahsub" <Tra...@discussions.microsoft.com> wrote in message
news:03FB8B3E-277A-4D2F...@microsoft.com...
Bruno
May 21, 2008, 2:49:01 PM5/21/08
to
Hi
As said in the previous post, you can use Setacl, Regdacl, etc to do this.
One option is to have a script run just before the install to make the
changes. (note that since the folders won't exist yet, this might be a bit
tricky). Another option is to have a script run after the install that
changes the requested permissions.
I've been using a One-for-all script that checks if any 'problematic' app is
installed and based on files or folders found, updates the permissions.
As said in the previous post, you can use Setacl, Regdacl, etc to do this.
One option is to have a script run just before the install to make the
changes. (note that since the folders won't exist yet, this might be a bit
tricky). Another option is to have a script run after the install that
changes the requested permissions.
I've been using a One-for-all script that checks if any 'problematic' app is
installed and based on files or folders found, updates the permissions.
0 new messages