You have to ensure all is lowercase in AEM then add mod_rewrite rule to apache or to those of us using varnish it could be even implemented there. We did avoid using AEM for this job as this might affect licence costs on a long term.

After upgrade, once you have logged in to CRX or Content Explorer, you should be able to login to other modules including system console.

Hi there,Thanks for reaching out to Adobe Community.You can automate the process of uploading multiple assets to DAM. Please see the below community article to know more:https://helpx.adobe.com/experience-manager/using/multiple-digital-assets.htmlThanks!

Hi, could you re-attach the image here? I'd like to try this, but unsure exactly where to disable. Thanks!

We can control the ACLs using cURL (Refer [1]) or we can write a custom servlet aswell using 'AccessControlUtil' API[1] http://stackoverflow.com/questions/24919675/cq5-aem-change-permissions-on-groups-with-curl

I figured it out myself. Anyhow, attached my working config. 

You are working with the multi window view which none of our over 300 authors uses because it's useless from their point of view and I totally agree.I guess it's quite a different behaviour whether you have to manipulate 5 pages a day or like some of our authors 300, not using the back button (or backspace how they do it) this simply saves you 300 x 1 Second per Day or half an hour per week. And as a matter of fact it works perfect in 5.5

Thank you.Anyhow not what I expect from a system with AEM's price tag.Actually I expect to have a health check console for all my authors and publishers and for sure no custom coding.