CQ 5

The Problem: You want to change the cq5.6/AEM admin password on the publish and server instance. The Solution: CQ 5.6 or later: Go to: (Or whatever the address/port of your admin instance is) http://localhost:4502/libs/granite/security/content/useradmin.html Double click on the admin user, scroll down, click on the pencil icon, and change the admin user. NOTE: the first password is the new password, and the second password in the current password. So, for a fresh install, put in the new password first, followed by admin as the second password. Repeat for http://localhost:4503/libs/granite/security/content/useradmin.html or equivalent. CQ 5.4: To change the password for the CQ admin account, you need to make changes in both CRX and the OSGi Console. Changing the CQ admin password in the CRX console. To change the admin account in the CRX console: Open the CRX console at http://<server>:<port_number>/crx Log in as admin to the crx.defa

ISSUE: I have configured two environments of CQ5.5, Author (at 4502) and Publish (at 4503). Initially, when I just created pages based on default templates, the publishing went on just fine. I even activated using workflows.. However, when I created my own components/templates/jsp's, the pages stop getting fdeployed on Publish Environment. Now, even after activation (green light), the pages on publish environment display just a blank page and nothing else. I checked and found that all my new components/templates/jsp's etc. are not present in the 4503 node. Any way to keep them in sync ? RESOLVED: The issue isn't that your pages aren't being activated. They are likely in fact being activated just fine. You can verify this by examining the content tree on your publish instance. The issue is that the components you created and are using on those pages aren't present on the publish instance - as you noted. It's important to keep in my that CQ won't