I hate to necro a post with no answer, but this is still not answered anywhere on the forums nor addressed in the documentation, for that matter.
There should proper documentation of the things that Composer and subsequent jamf installs may already handle intelligently; things like de-personalizing files from home folders, generalizing ByHost prefs, smart updating rather than overwriting of assorted files in-place, receipt creation, etc.
Is everyone just using Composer without grooming what's added, and just hoping for the best? Or winging it and learning the hard way what does or does not need culling? Why does everybody have to go through that? I'd settle for a FAQ somewhere on how to treat those myriad unexpected things that pop up in Composer... InstallHistory.plist, saved application states, CoreTypes.bundle, App Store/adoption.plist, /Library/Updates/, [later-dysfunctional] symlinks, logs, ~/Library/IdentityServices/, time machine prefs and files, Cookies.binarycookies, .DocumentRevisions-V100, unrelated-looking LaunchDaemons like fpsaud or cingen, /Users/Shared/adi, .spin files, unrelated-looking .localized files, and so forth.
With a sigh, jreid
