Understanding Prefetch behavior for Offers and Deployed via AD Group

We have had some bandwidth issues if we create an offer deployed to our entire environment. It seems that the prefetch is downloading even though the “Start client downloads before constraints are satisfied” remains unchecked. It seems all clients download it regardless of whether or not the offer will be used.

We have seen similar behavior when using the Users tab to specify an AD group and then targeting all workstations. The prefetch payload is downloaded even though the “Start client downloads before constraints are satisfied” remains unchecked." and the client is in a Waiting status, waiting for the AD user to logon.

We have also seen this cause ‘Disk Limited’ conditions on clients who we never really intended to download the prefetch to because it is waiting on 1. a user logon or 2. Pending Offer Acceptance.

The point in writing is I am looking for a detailed description on how this behavior works. Do these packages roll off after that initial download? Why do they download prior to action start in these scenarios? Is this expected behavior? We are wanting to be more reliant on AD groups but this behavior may prevent us from moving forward with that.