This is a newbie question.

I am creating a package in Wise Package Studio and need to give the group Everyone or the USERS group full permission to the C:\Program files which I guess translates to C:\Program.nfo.

I can give permissions to individual files in program files folder, but when I click on the C:\Program Files Folder in my Filestructure in Wise Package studio, I do not see the ability to go to details button [it becomes grayed out] and so I cannot add permission. Is there a way I can do it in wise package studio?

Thank you in advance
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
I am creating a package in Wise Package Studio and need to give the group Everyone or the USERS group full permission to the C:\Program files which I guess translates to C:\Program.nfo. One, that's a REALLY bad idea and two, I have no clue what you mean by 'translates to C:\Program.nfo'.

You should ideally only permission the folder to which the application you're packaging writes. At the very worst you can permission INSTALLDIR and its sub-folders but NEVER assign Full Control to 'Everyone' or 'Users' to [ProgramFilesFolder]. Users are universally stupid and someone WILL delete the entire contents of that folder if permissions allow them.

Coming to the "how to", you *could* use the LockPermissions table (in WPS, select the 'Installation expert' view, select the folder and click 'Details'. You can then click 'Add' to add the relevant user(s), group(s), whatever. However, LockPermissions will REPLACE and current permissions so you have to go through the pain of knowing which users and groups normally has access and what their permissions are. Most packagers use a command line tool via a Custom Action. Examples are SetACL, SubInACL, XCACLS and so on, because these tools can ADD permissions (although they can also replace!) Note that it saves time to set permissions after the CreateFolders action and before the InstallFiles action, as files will inherit folder permissions as theyre copied in.
Answered 10/03/2008 by: VBScab
Red Belt

Please log in to comment
0
Thank you so much!

Well, I got an email back from one of the application owner/ tester, that the package was not working and I need to give the USERS group write permissions to the C:\Program.nfo folder.

Since, I do not have such a folder in the package, I thought that the program.nfo folder is the program files folder...my bad!

I am not sure what the program.nfo even means.
Answered 10/03/2008 by: aek
Purple Belt

Please log in to comment
0
hidden folder perhaps ?

Are you sure that this is a folder ?
Answered 10/03/2008 by: JeanLedot
Orange Belt

Please log in to comment
0
yeah it looks a little more like a file than a folder. perhaps your universally stupid user gave you the incorrect term leading you down the incorrect path.
Answered 10/05/2008 by: jmcfadyen
Fifth Degree Black Belt

Please log in to comment
Answer this question or Comment on this question for clarity