@mireneS1 yes you should be able to do it please refer to very detailed article on the same   https://blog.developer.adobe.com/how-to-integrate-a-single-adobe-workfront-instance-with-multiple-aem-environments-3ab09c7a08e2

Got it, please not condition for model.json in your regular rules and create a new rule only for model.json

@ashish_kamalaksha as said by @konstantyn_diachenko we might need more details..   But few things to look for More than one rewrite rule matching , for this use L apache flag which marks the rule as last rewrite and doesn't execute subsequent rules   Check if your publish farms are multiple and all ...

@Prithwiraj_Deb I think there is an open bug in the ACS commons reporting feature for the replication status column.   Please check link below: https://github.com/Adobe-Consulting-Services/acs-aem-commons/issues/2812

@georhe6 can you please elaborate your ask? Is you AEM on-prem? AMS? Cloud?   Process might differ based on type of deployment.  

@RajeevBo it's all about hitting an AEM page from AeM publisher and storing it as redirects in webserver, be it apache or IIS, while I am not expertise in IIS, I am sure you should be able to write a bat file kind thingy to do similar job.

@gallaghan6 check Dynamic Media Reprocess under workflows tab in tools section

@punithshetty123 no

@ChristianJu as AEM is built on top JCR repository, move operation is nothing but deleting a node from one folder and creating in new folder. So it needs delete permission to allow move operations to work..   One thing we can do is to write some custom JS on top of aem UI to hide delete button on pa...

@SeanMc5 Can you be more specific in the ask? what kind of images you have in folder A, What's the size of each asset and overall folder? Are they getting synced successfully if you are manually re-processing the asset again using DM::Reprocess asset workflow?   Based on that we can guide you better...