/build/static/layout/Breadcrumb_cap_w.png

Why Custom Action

hi,

Why Companies are using Custom Action for giving permissions to file/folder/registry keys, when there is Lock Permission Table?

thanks
skj

0 Comments   [ + ] Show comments

Answers (7)

Posted by: jonasm 19 years ago
Blue Belt
0
Hi!

There is a short answer on your question; The lock permission table is working really bad, and have some bugs.

/Jonas
Posted by: MMA 19 years ago
Senior Yellow Belt
0
And many vendors dont know how to propperbly create a MSI package
Posted by: brenthunter2005 19 years ago
Fifth Degree Brown Belt
0
When using the LockPermission's table, it simply overwrites any ACL's that have already been defined.

I use the XCACLS.VBS tool to 'append' permissions to file/folders, and (most of the time) secedit to apply registry key permissions.

Hope this explains it...
Posted by: VikingLoki 19 years ago
Second Degree Brown Belt
0
The LockPermissions Table can frustrate you tremendously. It doesn't always work as one would think. I use SetACL.exe for both file & registry.
Posted by: rpfenninger 19 years ago
Second Degree Green Belt
0
Additionally I need to say that with the LockPermissions table you can only set permissions on single registry keys instead of full parts of the tree. That's why we use vb scripts and sdb's most of the time.
Posted by: UcMerrill 19 years ago
Senior Yellow Belt
0
I use secedit. It has inherited permission for both files and folder. Works Great!
Posted by: UcMerrill 19 years ago
Senior Yellow Belt
0
and registry as well
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ