Individual file sizes and folder file sizes should match the Finder. What a mess! If I have to use rsync to sort this out, I will skip Dropbox and use or similar providers for my needs in the future.

I have recently discovered that synchronizing a folder, then removing it from synchronization, then later adding it back to synchronization duplicates SOME folders and items into a new 'conflicts' folder, without identifying the conflicts. Can you address that serious problem please? A simple count in a single folder isn't useful for validation. The 'workaround' you propose does not address file size differences between the Dropbox web interface and the Mac Finder. so its making me think we should sure-up our scoping and smart groups.Please raise this issue on your end, this should be considered basic functionality. We have a handful of these types of policies, but they should be occurring that often. The same policy would have the Update inventory option set so it will update jamf to then remove the computer out of scope so the policy doesn't try and push the policy again on next check-in because it still believe the device has no antivirus. This type of policy will be set as ongoing. We have a policy that will reinstall our antivirus if Jamf detects that the end point does not have it installed. But saying that it would also include computers which may be incorrectly scoped and rerunning policies with the recon payload. So that would include computers that are being provisioned which may recon more than normal.

Yes the average of 12 was based on how many recon we are seeing on the server divided by how many computers we have. You all have been incredibly helpful thank you.

Foldersizes view update frequency