This is a strange issue that in  ALLUSERS profiles user's don't have write access.Either moving the component to USERSPROFILE  (if possible) or applying permission using CACLS can resolve the issue.But I doubt whether its a best practice.

A custom action is required to call CACLS to execute. CACLS will help to set a permission for a file.
To get more information type in CACLS  /? in command prompt.

I suggest you to run ' processmon' to find which folders inheritance is deneying the access.

If you must set permissions - and I agree that you have a permissions issue if that is necessary in this case - use SetACL instead. The reason is that it can permission the registry as well as the file system, meaning you only need to use one tool for permissioning.

File permissions forum doesnt sound good there are many options to give permissions. as VBScab says, think about using http://www.google.com before posting.  Anyways get a proper process to set permissions using any tool you are suitable with then add a custom action to perform that process.

Thanks for the replies.  I will try some of your suggestions if I cannot find another way.  My hope was that this function was available in the Wise app and I was just not finding it.  I want to minimize the amount of CAs in my installs as much as possible.

Nac, my first step is to always search google.  I guess I was more looking for a way to do it within the Wise App and that is why nothing turned up.  Thanks for the suggestion though.

>Yes permissions can be given with wise also, with the help of LockPermissions table

The reason why I almost never mention the LockPermissions table, particularly for newcomers, is that it's such a bear to use (in that you need to use SIDs instead of user/group names) and that it isn't additive, i.e. you need to explicitly add all users and/or groups which require permissions, whereas the tools suggested can be used to add those users and/or groups.

Since the intention is to apply full permissions for everyone, the lockpermissions table may be adequate.

You need to add a create folder action for the folder you wish to set permissions for - it doesn't matter if the folder exists or not.

Then using the permissions menu, you need to appreciate that Lockpermissions removes all existing permissions when it applies your permissions, so you need to set the following:

Administrators - select all the permission options to give full permissions - leave the domain field blank.
Users - select all the permission options to give full permissions - leave the domain field blank.

(There is no support for the group "Everyone", so don't bother trying to set that in the Lockpermissions table)

I cannot recall whether the permissions set this way are inherited all the way down the ALL Users profile, but worst case you can set the permissions individually for all the standard subfolders too.

Overall, it's a damn site easier using CACLS or SetACL for permissioning but if you want to avoid the extra custom action, then Lockpermissions is there for you to struggle with.....
 

Use Secedit with well known SIDs

Secedit is OK where the SIDS are not prone to change, but for any domain resources, the SID values will change if a group is deleted and recreated, for example.
The controlling INF file can be generated using the security snap-in in the mmc

I'd like to set global read/write permissions for a folder that is being created in a "shared" or "all users" folder.

Using the groups "administrators" and "USERS" seems to work fine in the US and UK, but the install fails on foreign language versions of Windows.  From what I can tell so far, it is the group "USERS" that is not available and thus the install fails.  Is there a term that implies all users of all groups in any language version of the OS?

Google for "common SIDs" and use the SID for USERS.

EDIT:
Actually, you could save some time by going directly to installsite.org which, if memory serves, is where the SIDs are listed

The URL you need is:
http://support.microsoft.com/kb/q243330/

I suspect your best choice will be S-1-5-11
Secedit.exe, which is part of windows default fileset, will apply permissions based on security sids. You can generate the necessary INF file using the security snap in that is in the mmc.