![]() Schedule 5 is to run the install for the locally staged High Priority packages at remote sites. Schedule 3 is for High Priority P2P downloads at remote sites for the high priority packages. Schedule 1 is for High Priority downloads to distribution points. So 2:00:00, 2:00:30, 2:01:00, 2:01:30, 2:02:00, 2:02:30 - All set to abort at 3:59:00.Īs to my particular reasoning for these schedules? Getting security updates out and installed sooner than other 3rd party updates. All are set to abort 1 minute prior to the next even hour. Then each subsequent schedule is set to start 30 seconds after the previous. Starting on each even hour is schedule one. (Of course you can have as many as you want) Those schedule tiers allow for six levels of priority. +1 for set priority's on deploy packages.Īnd perhaps not helpful, but in case it is for anyone, I've semi-resolved this priority issue with scheduling.Īll of my In-Policy PDQ Deploy Packages fall into one of six schedule tiers.
0 Comments
Leave a Reply. |