This might appear to be a relatively unnecessary rule, but the idea is to demonstrate the kinds of configurations that you can achieve with FsLogix.
Notepad.exe holds its settings in the HKCU hive: [HKEY_CURRENT_USER\Software\Microsoft\Notepad] where you will see a set of DWORD values. Your key may be empty, it appears that notepad only populates values as it needs to. These are obviously stored in the correct place for user specific application settings, however assume for the purposes of thus example that we wanted to set the Notepad values for all users that use the machine and that these settings should not bee something that a Standard user should be able to change by default for the application.
I have configured Notepad as I want it to be for all users (Font, FontSize, Bold etc.) each time they start the application. I have then exported the Notepad registry key as a .reg file. This is then edited to change the Path to [HKEY_LOCAL_MACHINE\Software\_FSLRules\Notepad].
With the .reg file edited we can then import those keys into the HKLM Hive without affecting anything else. I also want to make sure that when a user opens a certain file in notepad they are redirected to another file, in this case it is just a txt file that I have redirecting to another but it might be a need to make a configuration file writeable when it is normally stored in a System path. Another example might be an application that created configuration files on first run, rather than on install, that you want to set values for.
Finally the rule association in this case has been assigned to the Process "Notepad.exe" so will apply to all users that use notepad. This could have been assigned to a user group if there was a need to alter the standard configurations of an application for a particular set of users.
No Rule Applied:
Notepad Look and Feel:
File Open [No Redirection]
Notepad Look and Feel:
File Open [Redirected]:
The Rule Association:
If you want to download the Demo Rule and associated Registry settings and files you can get it from HERE. Extract the ZIP file to C:\_FSLRuleTest if you want to run it without editing the Rules file for the File Redirection.
This is just a quick look at how you can combine the rules to deliver application configurations as well as Application Masking. The ability to tweak application settings and configurations at runtime has been a capability of application virtualisation solutions since forever and has been a really powerful piece of functionality when you need to get applications to work in environments that they were not designed to run within (i.e. RDS, Non-persistence etc.). It has also been possible to achieve similar capabilities within traditional UEM solutions in the past, but it is great to see this level of control in the new breed of application management / layering technologies as well.