Intended Use of the AEM 6.5 LTS Analyzer Content Transformer The LTS Analyzer identified a handful of references to obsolete components in our custom code, which we remediated and were removed from the report on a subsequent run.What remains are many paths to out-of-the-box components that we have never used or referenced. In our dev system, I used the Content Transformer to remove ALL paths (/content, /etc, /libs, /var) on both author AND PUBLISH instances, PRIOR to upgrade (6.5 SP21).After upgrade, everything is working fine. Zero issues. But now I am seeing conflicting information that the tool should not be used that way, specifically:Only /content and /etc paths should be removed by the Content Transformer. The Analyzer should only be run on author instances. On publish instances you should remove the obsolete paths manually or some other method (not sure what that would be). And just to confirm, the Content Transformer must be run on a 6.5 classic instance, prior to upgrade. It errors out on a upgraded LTS instance. The error logs in