Forum Discussion
Common Application Configuration File in WVD
knowlite the original ini file will be in the place where the app expects it to be. It's just that based on which user is accessing the file, FSLogix will redirect the file open to the user's copy in their profile. It's like a fancy symlink, except that it will redirect to a different place based on which user is accessing the file. And if the target file doesn't exist, it can copy the original file to the target location before opening it.
The ini file *has* to be in a certain directory of the installed application (did I mention worse app ever?). I floated the idea of doing a hand-recompile of the app to allow for a registry-based ini file location, and was told that would violate all sorts of legal stuff.
Can FSLogix be used to take the contents of the configuration directory of the application and cache it for each individual user?
FSLogix is a method to resolve the issues that come with roaming profiles (big Outlook OST files, OneDrive synced files, teams content etc) causing extensive login times. FSLogix also offers "application masking" which hides applications for certain security groups but this would only solve your issue if you want to hide other user's INI files from other users (maybe this is what you are looking for?) More information can be found on: https://docs.microsoft.com/en-us/fslogix/implement-application-masking-tutorial
The explanation for the recompile sounds like "let's use the magical LEGAL term to get rid of irritating requests", just like "GDPR" but those are just my two cents 😉
- racook
Microsoft
While application masking is generally intended to handle full applications, you can generate a rule file by hand that will do what you want.
Create a redirect for the ini file that redirects into the users profile somewhere. There is even a checkbox that will copy the original file if one does not exist at the target.
Start by creating a new, empty ruleset. Add a file redirection rule. Something like:
C:\badapp\badapp.ini -> __USER_PROFILE_PATH__\AppData\Roaming\badapp\badapp.ini
(Variables that can be used are described here: https://docs.microsoft.com/en-us/fslogix/application-masking-rules-ht#create-a-new-rule)
Next you will need to describe which users should get it. Maybe Everyone? See this for directions: https://docs.microsoft.com/en-us/fslogix/implement-application-masking-tutorial#make-assignments-for-your-rule-set
Then deploy.
- Hi Racook,
As far as I understood the initial poster, the ini should stay in the program folder so redirection cannot be done? Am I correct 40MB?- racook
knowlite the original ini file will be in the place where the app expects it to be. It's just that based on which user is accessing the file, FSLogix will redirect the file open to the user's copy in their profile. It's like a fancy symlink, except that it will redirect to a different place based on which user is accessing the file. And if the target file doesn't exist, it can copy the original file to the target location before opening it.