Because Avast creates new processes for each terminal connection (session), running additional Avast components besides the File Shield can bring a terminal server to a crawl, especially if you have hundreds or thousands of terminals. We’ve also seen many instances of where additional Avast’s components can conflict with (and perhaps even detect) processes ran on a terminal server remotely from terminals. However, I encourage to thoroughly test within your environment (preferably a test/non-production environment) and use what settings work best. These are just settings we recommend to avoid possible conflicts and false positives without lengthy testing.