For flashplayer, I usually just keep current and -1 around; and I expire the older ones.
For anything else, unfortunately you'll have to do trial and error. For some updates (like adobe reader) there have been times when you could go straight from version x.1 straight to x.latest; and other times it's had to be x.1, then x.5, then x.latest--it all depends how the patches were written/coded by the vendor, and it's really unpredictable. If, for you, you can go straight from x.0.3 or less to x.0.8, then sure, expire anything that you don't want to actively deploy--keep your rules tidy. On Monday, January 26, 2015 9:37 AM, Jimmy Martin <[email protected]> wrote: scup 2011, adobe, expiring updates I probably just missed it in the documentation somewhere... or maybe it wasn't spelled out so explicitly... Using SCUP for adobe related updates, when a new version of flash or reader or full comes out, do you go ahead and expire the old updates or must they all stay active stairstepping through update levels? When I am creating my own custom updates, I have an idea about what to do based upon my installed and installable rules and the msi or exe I setup for the update... Also, Reader 11.0.4 seems to error out a large amount of the time. It doesn't seem to prevent 11.08 from installing so that got me to wondering if my process needed to include expiring old adobe updates. Just doing a sanity check. Thank You, Jimmy Jimmy Martin| Engineer | Information Technology | BMHCC - CORPORATE Phone: (901) 227-8209 | [email protected] Opinions expressed above are not necessarily those of Baptist. This message and any files transmitted with it may contain legally privileged, confidential, or proprietary information. If you are not the intended recipient of this message, you are not permitted to use, copy, or forward it, in whole or in part without the express consent of the sender. Please notify the sender of the error by reply email, disregard the foregoing messages, and delete it immediately. PPlease consider the environment before printing this email...
