Once you set up your LDAP or LDAP-AD synchronization properties, you may execute an LDAP sync in several ways:
1) The basic way, via configuration properties: By default, a differential sync is done on synchronization subsystem startup (on Alfresco startup) and also via the corresponding cronjob:
synchronization.syncOnStartup=true synchronization.import.cron=0 0 0 * * ?
http://docs.alfresco.com/5.0/concepts/sync-props.html
2) Via OOTB Support Tools: Go to OOTB Support Tools > Scheduled Jobs and execute ldapPeopleJobDetail job
https://github.com/OrderOfTheBee/ootbee-support-tools/wiki/Scheduled-Jobs
3) Via Javascript Console: This is a nice tip for Javascript Console. You can run code for triggering a quartz job (ldapPeopleJobDetail job) for example, or executing the user syncronizer.
https://gist.github.com/AFaust/beaa309837397abf961f#file-triggerusersynchintxn-js
4) In Alfresco Administration Console > User Management: Simply, run sync.
http://localhost:8080/alfresco/service/enterprise/admin/admin-directorymanagement
5) Via JMX Console: You can restart the synchronization subsystem using JConsole or jmxterm
MBeans -> Alfresco -> Configuration -> Synchronization -> default -> Operations -> start()
or trigger the LDAP quartz:
MBeans -> Alfresco -> Schedule -> *CronTrigger (e.g. MonitoredCronTrigger)-> syncTrigger -> executeNow()
Finally, remember that you can debug this process setting the following logger:
log4j.logger.org.alfresco.repo.security.sync=debug
This can be done using OOTB Support Tools (without restarting) in Alfresco Community Edition or setting it in $TOMCAT/shared/classes/alfresco/extension/custom-log4j.properties (needs restarting Alfresco). In Enterprise Edition, you may also use Support Tools (for EE) or a JMX console to set this logger to debug, without restarting Alfresco.