Howto? Setting Access Permission on Folders - InstallShield
Hi All,
Hoping someone can point me to the right directions. I am still learning.
I am customising a MST to create 2 folders under the install directory.
C:\Program Files\App1
Folder to be created:
C:\Program Files\App1\SubFolder1
C:\Program Files\App1\SubFolder1\SubSubFolder1
I am using InstallShield2009 and look pretty easy to me.
I go to "Files and Folders" and go to "Properties" and Permission.
I have the following settings:
[%USERDOMAIN] Domain Users
Permisision: FULL.
After the installation with MST on a client. I check the App1 folder and the permission has not been applied. I wonder why. Can someone tell me I've done the right thing or anything else I need to do before I can see the results?
Hoping someone can point me to the right directions. I am still learning.
I am customising a MST to create 2 folders under the install directory.
C:\Program Files\App1
Folder to be created:
C:\Program Files\App1\SubFolder1
C:\Program Files\App1\SubFolder1\SubSubFolder1
I am using InstallShield2009 and look pretty easy to me.
I go to "Files and Folders" and go to "Properties" and Permission.
I have the following settings:
[%USERDOMAIN] Domain Users
Permisision: FULL.
After the installation with MST on a client. I check the App1 folder and the permission has not been applied. I wonder why. Can someone tell me I've done the right thing or anything else I need to do before I can see the results?
0 Comments
[ + ] Show comments
Answers (3)
Please log in to answer
Posted by:
Tone
15 years ago
Posted by:
anonymous_9363
15 years ago
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.
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.
Posted by:
ahcash
15 years ago
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.
Your note about running such CA right after the install folder makes a lot of sense. Thanks.
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
so that the conversation will remain readable.