Ektron E-Sync is a good product when it works but it can really make your users nuts!
E-Sync Logging: E-Sync logging is still very rudimentary and there are lot of chances to improve this. There are no simple configurations to change the logging locations and weird log names like “test.log”
E-Sync must tell clearly what content is published. Currently it is just copying the complete database from one machine to another machine where as a user I dont have any clue what is synced to next environment. It just states there are 150 changes to your database but this does not help when you try to debug some rogue content publishing.
Another annoying thing is, it sync your userids as well across environments. This means if you have AD integration in your production environment and you do not have AD integration in your dev/test environments then your system can break or if you added a user as CMS content author then he can not act as membership user.
Regular Full ESync: If you do not perform full ESync on regular basis then it can take hours next time. In my experience, as part of your publishing strategy you must think upon doing regular full ESyncs..to ensure it does not break the system
A granular control on what we are syncing to next stage is critical for an enterprise scale infrastructure…
