Patch Policy actions issued to a group are using dynamic targeting, which means the action is issued to all devices that an operator administers, and not individually to computers.
Any devices that meets both the following criteria:
- is part of the targeted group(s)
- is relevant to any patch fixlet in the action
will gather the operator site (opsite), look at the dynamically targeted action from Patch Policy, and the device itself will check the criteria and run the action if it meets the criteria. Of course, the device would need to be turned on at some point during the active time of the action. Both Device A and Device B will be included in the patch action in your scenario.
Caveat: there is an optimization in Patch Policy where the action only includes fixlets that are at least relevant for one device for that operator, at action issue time.
Assuming that Device A and B are the only devices that the operator administers, Device A has never evaluated any of the new content, since it has never been powered on Wednesday and before the action issue time. Device B was turned on Wednesday and has reported back its applicability to the new content, even if it is technically offline during the action issue time. The Patch Policy action will only contain fixlets that are applicable to Device B,
but both Device A and Device B will run the action (assuming there is at least one fixlet applicable to Device A).
EDIT: Device B will not run the action at all, since it is not on during the entire patch window. I got the times mixed up in my head. But Device A will run the action since it is on for at least some part of the patch window.