Software Deployment

In what amounts to a direct contradiction of my normal advice, i.e. to fix problems and not work around them, I'd suggest that you abandon the use of the LockPermissions table. No-one in their right mind uses it. Instead, use one of the many, much more flexible third-party tools to do that via a Custom Action.

My own preference is for SetACL (because the one tool can do file and registry permissioning) but there's XCACLS, SubInACL and, of course, the built-in SecEdit.

Instead of using lock permission i will suggest to use custom action to give permission.

packengg,

Wasn't that what Ian (VBScab) just suggested?

However, there shouldn't be a problem using the LockPermissions table if you are certain that it's only your single package that is going to use that file, registry or folder. Just have in mind that it will replace the ACL on the object.