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

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
Hi!

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

/Jonas
Answered 08/30/2005 by: jonasm
Blue Belt

Please log in to comment
0
And many vendors dont know how to propperbly create a MSI package
Answered 08/31/2005 by: MMA
Senior Yellow Belt

Please log in to comment
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...
Answered 08/31/2005 by: brenthunter2005
Fifth Degree Brown Belt

Please log in to comment
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.
Answered 08/31/2005 by: VikingLoki
Second Degree Brown Belt

Please log in to comment
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.
Answered 09/01/2005 by: rpfenninger
Second Degree Green Belt

Please log in to comment
0
I use secedit. It has inherited permission for both files and folder. Works Great!
Answered 09/01/2005 by: UcMerrill
Senior Yellow Belt

Please log in to comment
0
and registry as well
Answered 09/01/2005 by: UcMerrill
Senior Yellow Belt

Please log in to comment
Answer this question or Comment on this question for clarity