nealr82603403​, we always recommend you use the newest Dispatcher versions for the latest security patches and bug fixes.Also see the Dispatcher release notes for the changelog and a list of past versions.

Lazy content migration is relevant starting with versions 5.x, so the answer is yes - you need to run it for 6.0 as well.

Unfortunately, it's not possible to run the lazy migration tasks selectively at this time.

Hi VAr,Yes, those bundles should've been disabled when running in nosamplecontent mode. Not sure why that didn't happen, but you can stop them manually as described in the security checklist here: [1]. [1]: https://docs.adobe.com/docs/en/aem/6-1/administer/security/security-checklist.html#Disable%20...

Hi Vinyak,Your first screenshot indicates that the JVM is running from Program Files\IBM\Java60, while the second is running from Program Files\Java.In the case of running quickstart from the batch script, the second JVM instance is there because it was forked due to insufficient heap (the default l...

Hi Vinayak, Looking at the paths, I can see that the first JVM is launched from what appears to be an IBM JRE while the second from a standard Oracle one. You can set your file associations and JAVA_HOME environment variable to point to the same Java installation and the behavior will be consistent....

Hi, You can follow the instructions here to deploy AEM with JBoss: https://docs.adobe.com/docs/en/aem/6-0/deploy/application-server-install.html#JBoss%207.1Hope that helps.

You can also check [0] and [1] for more info on on how to calculate the sizing of your setup depending on the purpose of the deployment.BR,Alex[0]: https://docs.adobe.com/docs/en/cq/current/managing/hardware_sizing_guidelines.html[1]: http://docs.adobe.com/docs/en/cq/current/managing/capacity-guide....