As a (late) followup to my previous thread (viewtopic.php?p=55010#p55010) Would it be possible to have an option to allow this? In my case the script needs to run elevated (as it changes AD user accounts) and AV is centrally controlled so it would be easy to put an exception for the .exe. Furthermore, we don't want end users to have (easy) access to the attached files. So I can't use an .MSI or .ZIP
Thanks
Adding files to packages
Forum rules
DO NOT POST LICENSE NUMBERS, ACTIVATION KEYS OR ANY OTHER LICENSING INFORMATION IN THIS FORUM.
Only the original author and our tech personnel can reply to a topic that is created in this forum. If you find a topic that relates to an issue you are having, please create a new topic and reference the other in your post.
Any code longer than three lines should be added as code using the 'Select Code' dropdown menu or attached as a file.
DO NOT POST LICENSE NUMBERS, ACTIVATION KEYS OR ANY OTHER LICENSING INFORMATION IN THIS FORUM.
Only the original author and our tech personnel can reply to a topic that is created in this forum. If you find a topic that relates to an issue you are having, please create a new topic and reference the other in your post.
Any code longer than three lines should be added as code using the 'Select Code' dropdown menu or attached as a file.
-
Alexander Riedel
- Posts: 8488
- Last visit: Tue Apr 16, 2024 8:42 am
- Been upvoted: 37 times
Re: Adding files to packages
There really is no mechanism for this anymore. If you install your application with an MSI into the Program Files folder, normal users do not have permission to change or remove any files you install, if that is what you intend to prevent.
If you use an unpacking scheme the file is available for easy access while the application is running, since it has to be extracted to a location that is available to ALL users. Remember that you said you want to run elevated, which prevents a user specific folder.
If you do not want the files to be easily readable by end users, just use something like base64 encoding for your files and decode them when loading, that will discourage most regular users.
Example: http://powershellscripts.blogspot.com/2 ... -file.html
If you use an unpacking scheme the file is available for easy access while the application is running, since it has to be extracted to a location that is available to ALL users. Remember that you said you want to run elevated, which prevents a user specific folder.
If you do not want the files to be easily readable by end users, just use something like base64 encoding for your files and decode them when loading, that will discourage most regular users.
Example: http://powershellscripts.blogspot.com/2 ... -file.html
Alexander Riedel
SAPIEN Technologies, Inc.
SAPIEN Technologies, Inc.