1) If this package was sent "in error", then either the machines are in the wrong collection, or the packages distribution criteria is wrong. Either way, something needs to be changed, I assume the package applicable criteria needs to be changed.
2) When you get a re-imaged machine back onto the network, manually force the collection probes and updates to get them back into the collections. I would disable this problem package completely (temporarily) as if you are still having critera issues, then this will be pushed out as soon as possible after the new images are detected. You will now see 2 instances of the same machine, with different GUIDs, depending on whether you imaged the machines with the SMS adv client on, or without and SMS has distributed the adv client upon detecting the new machines. The OLD instance will become ACTIVE:No, and will become OBSOLETE, after a period of time (acording to the flag set in the site maintenance options)
3) When you re-image the machines, the new images will appear in the same collection as last time, if that package is still set to run on that collection, then they will get it again, so you need to address the package, or the collection rules that apply to those machines.
Neil J Cotton
Technical Consultant