Applying folder secutiry permissions via a transform
Hi,
I'm pretty sure I'm missing an obvious trick here but I need to change the \\<LOCALPC>\USERS security permissions to a folder within a transform being applied to a 3rd Party MSI.
I've tried searching the forums to see if there are any similar posts to this one and couldn't find any.
I've done this many times within native MSIs via the Lock Permissions Table, using the GUIs in either Wise or Installshield or via a Custom Action using ACL command line utilities.
I've tried to two methods of applying the permissions in a transform using both Wise and Installshield:
I suppose my question is can Permissions/Custom Actions be applied via a transform?
I'm pretty sure I'm missing an obvious trick here but I need to change the \\<LOCALPC>\USERS security permissions to a folder within a transform being applied to a 3rd Party MSI.
I've tried searching the forums to see if there are any similar posts to this one and couldn't find any.
I've done this many times within native MSIs via the Lock Permissions Table, using the GUIs in either Wise or Installshield or via a Custom Action using ACL command line utilities.
I've tried to two methods of applying the permissions in a transform using both Wise and Installshield:
- Making this change via a transform attempting to do it via the Lock Permissions table, the altered permissions don't get applied to the designated folder, during the installation.
- Setting up a Custom Action to run a command line, the Custom Action never gets invoked when the transform is run.
I suppose my question is can Permissions/Custom Actions be applied via a transform?
0 Comments
[ + ] Show comments
Answers (14)
Please log in to answer
Posted by:
cygan
14 years ago
try this in your mst
In Wise Package Studio
Drag the custom action --- Execute Program from Installation
Name enter a name for your CA
Executable file browse to your setACL.exe
Command Line Arguments -on "C:\Program Files\FolderName" -ot
file -actn ace -ace "n:Users;p:change"
Condition Not Installed
Location Normal Execute Immediate/deferred.
After . InstallFinalise
In Wise Package Studio
Drag the custom action --- Execute Program from Installation
Name enter a name for your CA
Executable file browse to your setACL.exe
Command Line Arguments -on "C:\Program Files\FolderName" -ot
file -actn ace -ace "n:Users;p:change"
Condition Not Installed
Location Normal Execute Immediate/deferred.
After . InstallFinalise
Posted by:
anonymous_9363
14 years ago
Posted by:
joban2000
14 years ago
Posted by:
cygan
14 years ago
Posted by:
joban2000
14 years ago
I've got it working, well the Custom Action method, it looks like it was to do with where in the execution sequence I was trying to run it. I was attempting to run it after the PublishProduct but before the InstallFinalize Actions.
From reading your instructions I noticed you mentioned putting it after the InstallFinalize action, I did that and now the setACL command is running.
Thanks for your help.
From reading your instructions I noticed you mentioned putting it after the InstallFinalize action, I did that and now the setACL command is running.
Thanks for your help.
Posted by:
McRip
14 years ago
ORIGINAL: cygan
try this in your mst
In Wise Package Studio
Drag the custom action --- Execute Program from Installation
Name enter a name for your CA
Executable file browse to your setACL.exe
Command Line Arguments -on "C:\Program Files\FolderName" -ot
file -actn ace -ace "n:Users;p:change"
Condition Not Installed
Location Normal Execute Immediate/deferred.
After . InstallFinalise
How deos it look like for a specific registry key???
Because I have problems with setting permissions for registry key... And setACL.exe is too complicated...
Thanks in advance
Posted by:
cygan
14 years ago
Posted by:
McRip
14 years ago
Posted by:
cygan
14 years ago
Posted by:
cygan
14 years ago
Posted by:
turbokitty
14 years ago
Posted by:
McRip
14 years ago
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.