This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- Ini File Permission
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
![](/skins/images/A5EADE085F77DE82FB3B14D6B307AE6A/responsive_peak/images/icon_anonymous_message.png)
Not applicable
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Nov 15, 2012
02:58 PM
Ini File Permission
In the Custom Actions Section, I have a VBScript that creates a new INI file. I want the permissions on the new INI file to be: Everyone - Full Permission, Authenticated Users - Full Permission, and Users - Full Permissions.
None of these users/groups show up in the INI file permission page. After the installation, I have to log in as administrator to add the permissions.
Is there a way to create an INI file in the Custom Actions Sections with Full permissions for everyone?
Thanks,
Eric
None of these users/groups show up in the INI file permission page. After the installation, I have to log in as administrator to add the permissions.
Is there a way to create an INI file in the Custom Actions Sections with Full permissions for everyone?
Thanks,
Eric
(1) Reply
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Dec 04, 2012
04:34 AM
I use a small tool called "setacl.exe" to set permissions. Add it to the Setup Files, and call it from the Property("SUPPORTDIR") from the VBScript.
I use if for fixing permissions for some legacy OEM component which installs incorrectly in the Windows Registry. But I believe that is also works for files and folders.
Note, it also uses the correct "naming" of the user groups, like "Everyone" is not the name for everyone in other languages than English.
-cpede
I use if for fixing permissions for some legacy OEM component which installs incorrectly in the Windows Registry. But I believe that is also works for files and folders.
Note, it also uses the correct "naming" of the user groups, like "Everyone" is not the name for everyone in other languages than English.
-cpede
![](/skins/images/A5EADE085F77DE82FB3B14D6B307AE6A/responsive_peak/images/icon_anonymous_message.png)