Scheduling caching of OS installer?

If I understand what you're wanting, you would need to specify a trigger (otherwise nothing will ever cause the policy to run, even after it's activated), enable the policy, and set the activation date/time.

That's the odd part bvrooman, even with "recurring check-in" specified there is no green or grey dot to the left of the policy. I don't know what I am doing wrong.

Until you reach the activation window, the policy should not turn green. I'm not sure what time zone you're in, but it's not yet 7pm here on the east coast.

so I just looked at my active policy. It has a green dot. It needs a trigger (recurring check-in for ex). Do you have it scoped to any particular machines? Also take note, are you wanting a server time limitation or a client. We have computers through every US Timezone, so we set it to client side times, since 7pm est is still 4pm (and working hours - aka massive network impact) for our California folks.

If you base a policy on Server Side time frames, it won't appear to be enabled until the time you specified. You'll also need a trigger.

I always build this part of policy building up too much in my head. I will forever think that an ongoing policy will happen all the time regardless of what triggers I enable.

Policy runs when you tell it to, based on the triggers and frequency. If I want it to run more than once a day, but only when someone logs on, then
Trigger = at logon
Frequency = ongoing