We really need the ability to rely on searches for non persistent terminal servers. I get it, only Outlook email searches can be roamed. I had a 6 month long ticket that in the end, was just told the behavior we are seeing is expected. End users cannot properly search against their Desktop/Document folders, and I would expect that after they login, Windows will start adding that information to the search index. Nope. Users are also unable to search from their Contacts folders in Outlook (but they can oddly enough search from the People bar in the mail screen). I ran through the gambit of rebuilding the indexes, rebooting, checking for specific Windows Updates that cause trouble, sfc /scannow. Once in a blue moon searches will work for a specific user. But as soon as they logout, even if they log right back in to the same server, it fails. Tried multiple builds of FSLogix, and in the end this is 'expected behavior.' It shouldn't be...

As old java versions are often a specific requirement for aged application, they rappresent a huge security issue.
To eliminate security risks, FSLogix could hide java installation to all users and make it visible only for specific application/web sites.

Idea is to use application masking to hide all installed java versions (no default java version) and then allow accessing them using version control rule.

For example, CoreHR, needed by all users, requires java 1.6 installed. Ideally FSlogix can hide it using applciation masking rule preventing security risks, but make it available while requested by CoreHR only. Same for other java versions.

In this way, there is no need for dedicated server and/or application virtualization technology (App-V for example)