Package Builder installing files to <ProgramData> folder

[JuliaDawkins]

I've deployed a package from NI Package Builder, with some of the files going to C:\ProgramData\MyProgramFiles.  

My problem is, some of my users do not have admin privileges on their machine, so after my package is installed via NIPM with an admin access, the user does not have permission to change the files inside the C:\ProgramData\MyProgramFiles.

I think this is because C:\ProgramData has restricted security settings.  Standard users can create files there, but the files are secured so that only the user who created the file can modify the file, hence my issue.

Is there any way in NI Package Builder I can set these privileges so it works as I would like it to? Or will I need to move my files to a better location?

Thanks!

Julia

[Scott_Richardson]

Julia, Package Manager based packages do not support controlling permissions on installed files or created directories during installation. However, I have not used the icacls command before but you should be able to execute this in a custom execute directly or in a script that you install and run.

Ref: https://docs.microsoft.com/en-us/windows-server/administration/windows-commands/icacls

Note: If you are using NI Package Builder to call a custom execute from your package, you should be aware of a NI Package Builder 20.6 bug, 1461850 "Custom executes error during installation when arguments contain quote characters" that impacts your ability to pass arguments with spaces. The workaround is to use NI Package Builder 20.5 or call a script or EXE and the script can specify the arguments.