Software Deployment

Irrespective of the file's attributes, I'd imagine that in most environments the entire Windows folder and sub-folders would be permissioned to read only. Thus, you'd need to add another Custom Action to permission the file accordingly. Use SetACL, XCACLS or any of the command-line tools available to do that. I generally use separate CAs for each action rather than monolithic ones combining several actions, as that makes error diagnosis much easier.

OK so am i correct in saying that i need to creat a custom action for permissioning of the file even though the script that i wrote sets the permissions on the file to start off with to write also?

And if so i'm not too familiar on how to use SetACL or XCACLS

any pointers??

Hi Jose,
this looks to me, as if your script is being called in the wrong place of the MSI.
Could you please paste the script here and tell us, how your custom action looks like?
Regards, Nick

ORIGINAL: mrcheeks
OK so am i correct in saying that i need to creat a custom action for permissioning of the file even though the script that i wrote sets the permissions on the file to start off with to write also? Your OP says that your script sets the file's atributes, not its permissions: the two are completely different.

File attributes can be null, read-only, hidden, system, archive or any combination of those. If you right-click a file and select 'Properties' from the menu, (a limited set of) the attributes can be set from the resulting dialog. If you right-click a file and select 'Sharing and Security' instead, these are the permissions for the file. They are probably inherited from the parent folder and are almost certainly set for 'Read' for the 'Users' group (or 'Everyone', depending on your workstation set-up). It is *these* permissions which you would use a permissioning tool to change.

Use Google to find command-line details for SetACL or XCACLS. My own preference is for the former, merely because I find its arguments reasonably straightforward and because I've used it since the dawn of time.

Hi folks,
the file not being delivered to its location has nothing to do with its own permission, IMHO.
But if the script runs outside of the install script (that means: not in the deferred part), the installer may just not have the permission to copy the file to the system folder.
Another possibility would be, that the script contains "Wscript" statements.
Taking a log file and search for an error would help a lot, i think.
Regards, Nick

One thing at a time, Nick... :)