Always remember, C:\ProgramData is the eqivalent of /etc in Linux. If they don’t know where to put/hide shit, but needs admin priviliges to edit and users can only read, you put it in C:\ProgramData.
Config files that are meant to be used as sane defaults for new user accounts, yes. Config files that are meant to be manually edited, no.
Besides, there are a lot of examples of configs that are saved in ProgramData, like, let’s say, registration info for proprietery programs (of course, this info needs to be shared amongst users, so your safest bet is ProgramData). Hidden by default, makes it perfect for storing everything the program is trying to hide from the user.
Always remember,
C:\ProgramDatais the eqivalent of/etcin Linux. If they don’t know where to put/hide shit, but needs admin priviliges to edit and users can only read, you put it inC:\ProgramData.I think programdata is closer to /usr/lib or maybe /var/lib.
You almost never see config files in programdata.
Config files that are meant to be used as sane defaults for new user accounts, yes. Config files that are meant to be manually edited, no.
Besides, there are a lot of examples of configs that are saved in ProgramData, like, let’s say, registration info for proprietery programs (of course, this info needs to be shared amongst users, so your safest bet is ProgramData). Hidden by default, makes it perfect for storing everything the program is trying to hide from the user.