MMF internal Installer question - Installing into AllUsersAppData

I am using the MMF internal install maker. I want to install my settings files, a ini and a txt file, into the AllUsersAppData folder so that every user at the pc is able to use the software. And not just the current user. That`s the Program Data folder from what i know then. Unfortunately the installshield just provides the Application Data Folder. Which is the AppData folder for a single user.

So i tried to use a manual path for my settings, have chosen a custom path, and have tried it with a #All Users\Application Data# , 'Program Data# and #ProgramData# into the corresponding edit box so far. No luck. The files are not created in Program Data. Windows search finds nothing. I have of course also tried #AllUsersAppData#. And also Program FilesNo luck.

What path do i need to choose to install my ini in the AllUsersAppData so that the files gets created in the ProgramData path?

I use Inno Setup, in which this is very easy to accomplish. In case Install Maker accepts environmental variables, maybe this website can help. Keep in mind that if one user writes a file to the "All Users" application data folder, another user will not have write privileges to this file unless the installer changed the ACL permissions to "modify". In other words, if Install Maker doesn't support changing this, you're out of luck even if you figure out a way to retrieve the path - unless of course you never intend to modify these files at all after installation - in that case they just go into the application's own folder (Apppath$)

However, I suggest consider alternatives. What data is this, are you sure it doesn't fit better in the user account's roaming application data folder? Even a program's settings should in 95% of all cases be linked to the user account. Maybe you don't need to create these files during installation, but let your application check if the files exist when you launch it, and if not, extract them into AppData? I do that in Knytt Underground's default settings (which can then be modified by the game's settings menu).

Thanks Nifflas. That`s what i have done now. When file doesn`t exist, then create it.

I nevertheless still need a place to store my settings where all users have access too. I have a case here where it is important that ALL users have the same settings to prevent confusion. And that`s the Program Data folder. App data folder leaded to just the one who has installed the software was able to run it. Because without the settings the software didn`t work. That`s why i started to invest into the problem at all.

In my opinion an installer should be able to install in a way so that all users can access the settings of a software. Simply switching to Inno Setup may solve my problem, but not the problem of the MMF installer. And that`s part of MMF.

The funny part is, the file object knows the AllUsersAppData path. The installer not :)

I take it you have found a way to change the ACL permissions then? Without it, your solution still won't work for other accounts if UAC is enabled.

What settings are these, and why must they be the same for all users? I'm just curious, it's just not very common to want to store your settings like this, but if you're right I can learn from it too :)

The Program Data is under UAC, but accessible from all users from what i know. And it is very common. There are lots of folders in the Program Data folder. From Avast across Mozilla and Microsoft up to Unity :)

I haven`t had the time to test things by creating another account yet. That`s something i wil do tomorrow.

Quote:

---

What settings are these, and why must they be the same for all users?

---

It`s not so important in this case that they all have the same settings. It`s simple settings like window position, values to use for computation and stuff. But i have somebody with a horde of other userrs here. And he told me that for him the software works, and for others not. Which is most likely a rights problem because the values were stored in the appdata folder. And so they are only accessible by the user who installed it. Other users can start the software, but misses the settings. And then the stuff doesn`t work.

But think about a game where different users wants to use same highscore. And in this case it`s of interest so that all other users starts with the same setup.

Tested now. I can access the settings from a guest account without a problem. The software itself doesn`t show in the start menu though. Which doubles my questions.

Old question: How can i install my settings into the AllUsersAppData using the MMF Installer? New question: How can i install the software to be global accessible?

Any help is appreciated :)

Ah, yeah, you're right, it does make sense with highscores and such data. Anyway, I tested Install Maker, and I unfortunately don't think it supports the features you need. Maybe you'll need to look into Inno Setup.

Of course you'll be able to read the files as a different user than the creator. The point is, without changing the ACL permissions, another user won't be able to write to these files. By default, the standard user permission for a created file or folder will only be read and execute. The fact that you wish to put them in ProgramData instead of the application's own folder implies that you want your software to write to the files, right?

While your approach with ProgramData is valid, you will need to figure out how to change the ACL permissions too. In Inno Setup this page explains how.

Have i mentioned that i have tested it? ;)

As told, this works here, without changing the ACL permissions. The Program Data folder is not connected with the user accounts. Stuff that is connected with user accounts has a username in the path. Means i can also as a guest or another user change the values of the ini that is in the Program Data folder. Which works just fine.

But it seems that i have my answer. Clickteam installer is not able to do such a simple operation like installing a file into the Program Data folder. Sad one. Seems that i really have to migrate :(

Thanks for help Nifflas :)

This MSDN article recommends putting the data into the shared documents folder. Feels ridiculous, but I'm not aware of a better location, either. :-/

I don't think that's a good idea though, since that folder is specifically for files the user would want to view in Explorer. This particular case falls under Scenario 1 on that page (but for shared data which the article doesn't cover). The shared documents folder is a recommendation for Scenario 2. ProgramData is probably most appropriate for settings shared between all users, but modifying the ACL will be necessary. This seems to be quite common practice, a lot of software I have installed modifies the ACL to allow normal users to modify content in their folder within ProgramData.