FSLogix Exclusions Wildcards – Q&A Microsoft

[ad_1]

Does FSL recognize wildcards? Attempting to detect when a new Chrome profile is created (we’ve seen some users have “Profile 1”, some have “Profile 4”, etc.) What we currently need to detect profile names if they’re not at Default:

AppData\Local\Google\Chrome\User Data\Profile 1\Cache
AppData\Local\Google\Chrome\User Data\Profile 1\Code Cache\js
AppData\Local\Google\Chrome\User Data\Profile 1\DawnCache\js
AppData\Local\Google\Chrome\User Data\Profile 1\GPUCache
AppData\Local\Google\Chrome\User Data\Profile 1\JumpListIcons
AppData\Local\Google\Chrome\User Data\Profile 1\JumpListIconsRecentClosed
AppData\Local\Google\Chrome\User Data\Profile 1\JumpListIconsOld
AppData\Local\Google\Chrome\User Data\Profile 1\Service Worker\CacheStorage
AppData\Local\Google\Chrome\User Data\Profile 1\Service Worker\ScriptCache

Would this be possible and supported by FSL?

AppData\Local\Google\Chrome\User Data\Profile*\Cache
AppData\Local\Google\Chrome\User Data\Profile*\Code Cache\js
AppData\Local\Google\Chrome\User Data\Profile*\DawnCache\js
AppData\Local\Google\Chrome\User Data\Profile*\GPUCache
AppData\Local\Google\Chrome\User Data\Profile*\JumpListIcons
AppData\Local\Google\Chrome\User Data\Profile*\JumpListIconsRecentClosed
AppData\Local\Google\Chrome\User Data\Profile*\JumpListIconsOld
AppData\Local\Google\Chrome\User Data\Profile*\Service Worker\CacheStorage
AppData\Local\Google\Chrome\User Data\Profile*\Service Worker\ScriptCache

[ad_2]