The columns display on the Remote Users tab and you can quickly see information for each Remote. It's that easy.
Actually.. you cannot really tell when a user last synchronized.. you never could (w/SalesLogix OOTB).
A - Last Send (Date/File) only tells you the last time the main sync server "posted" changes for a remote (user) to pick up. It does not tell you that they actually did
B - Last Apply (Date/File) only tells you the last time a change came FROM a remote (user). If there were no changes from a remote(user) when that remote "synch'd", the Last Apply (Date/File) is NOT updated. Therefore if you have a remote (user) that does not change (or add) data on the remote very often but DOES synch often, one does not know that is what is going on.
Mike Spragg (www.emapth-e.com) and I (www.rjlSystems.net) have both developed "Synch Tracking" applications/tools that DO cause data (on the remote) to change each and every time a user logs in (and/or does a ctrl-F5) and out.. this results in a 99.999% probability there will be changed data on each and every synch cycle.
Note that you cannot (easily) tell what is going on w/a remote office since the system treats it as a special case (and not a "user"). Also, because of how the web works (stateless vrs Windows/LAN which is not), it is difficult to track "disconnected web" and/or remote offices that host a web. Also, when there is more than one synch server it is very difficult to tell which synch server was involved in a particular cycle (the unique synch server site code is NOT recorded ;-)
There are ways to solve this problem but they do require some schema and application changes. Some of which is possible by smart partners (or customers).. but not all of it since it requires access to the "hard-code" (Windows/LAN) which nobody outside of (Slx) dev has access to.
Thank you for the clarification. The steps described will not indicate if synchronization failed or there was not any data to send or receive. We have modified the posting.