Software Deployment

is the component you assigned the permissions to associated with a feature?

Any permissions you apply via IS's native support will populate the LockPermissions table. The problem with that table is that it assigns replacement permissions, rather than additive ones. As you have things (almost) set up now, you'll assign 'Full Control' to 'Domain Users' ONLY. That sounds great right now but what happens if you need to access that folder when you're not logged in to the domain? Even the local 'Administrator' account now has no access whatsoever.

You would be best advised to create a Custom Action which calls a command-line tool like SetACL, XCACLS or whatever your favoured tool is. Much more flexible!

On a related note...one thing that people trip over when they create such a CA is to have it run at the end of the install. That undoubtedly works but of course it wastes time writing to already-installed files. It's a lot more efficient to run the CA right after the CreateFolders action (in the Execute Deferred sequence, obviously). Then, all files copied in will simply inherit the folder's permissions.

Thank you so much for the response. I have decided to create a custom action which calls the ICACLS in Vista to set the permission. It worked beautifully. In fact, I will have to create another CA to use XCACLS in XP.

Your note about running such CA right after the install folder makes a lot of sense. Thanks.