Skip to main content

Alright, there is a high probability that I've missed something very basic here. I've set my new update policy (script by UESCDurandal as described in https://jamfnation.jamfsoftware.com/discussion.html?id=5890). Absolutely awesome script BTW. In any event, I've scoped this to the groups I need it to, however I've tried to set the policy to run on Monday - Thursday 2:30pm to 6pm. This means that I've set my date and time limitations as follows:



Do Not execute On: Sunday, Friday, Saturday
Do Not Execute Between 6:00pm and 2:30pm (proper logic form what I remember).



While the policy DID NOT run on Saturday or Sunday, it did run on Friday, and it IS running at any time fo the day (so say to logs).



In any event, I hope that I'm missing something very basic. It's the start of the new year and my brain has probably run as far away as possible.

... you know. I just had a bit of a realization. It may be that the process is beginning at the proper times, but recon isn't running until well after (especially if a user lets it run in the background) the process is scheduled to start. I am still waiting to verify this, but it may account for at least some major variances. I am stil seeing, that at least one or two of the computers seem to be accessing the SUS outside of these bounds initially. Will report back for anyone in the future who has a similar beginning of the year brain freeze.

Alright... this is confirmed. Now that my mind is working again I'm going to close this posting. Sorry folks!~

Terms & ConditionsCookie settings