Please log a Daycare support case and report the issue.Enterprise Support

Did you have a chance to test the solution package at https://helpx.adobe.com/content/dam/help/en/experience-manager/using/twofactor64/jcr_content/main-pars/download_section/… Also, make sure that the main pom.xml includes a 6.4 uber.jar file dependencies.

MIgrating an existing page three into a LiveCopy is not feasible

Try to employ http://<host>:<port>/libs/granite/distribution/content/distribution.html and check agent queue health and the status.

Experience and Content Fragment components are not designed for Classic UI. It's expected to be used in Touch UI.

Please check if pages in question have under jcr:content node a property "hidenInNav" that set to true.It means that they are Hide in Navigation.

ESAPI.properties is not an issue. Check if data*.tar file has RW permissions for an account that you are using to start AEM.Are you able to access /system/console?Also, tail stderr.log file. If there is an error on startup it will be thrown into stderr.log.

AEM 6.5 supports smart tags only for images

You need to deploy a war file to each WL managed servers separately, as such AEM author will have it'own crx-quickstart folder.What is the use case of having two authors? Keep in mind, that despite the fact that AEM is packaged as a war file, it does not support J2EE clustering. TarMK is not horizon...

Did you apply a custom metadata schema or did you edit DAM update workflow?What error if any do you see in an error.log?