Is it possible to tighten a deployment to defer not by days but by hours? We’re using PSADT v4, but given the options available by Show-ADTInstallWelcome, there’s only an option to defer by days. We’d like to make a tight deployment where users can only defer by an hour at time (for a max of 3 times), is this possible? Could we do something by writing a deadline date to the registry upon deployment and having it read that time +1 hour? Be interested if anyone has done something like this before
Hi Mitch, we don’t user defer at work but will shortly.
I was under the impression that after you click [Defer]:
Invoke-AppDeployToolkit.ps1 sends exitcode 1602 to Intune or SCCM
Intune or SCCM sees this as a Fail and retries later. (E.g. ~8 hours later for Intune)
Now you are saying the “retry” can be scheduled?!?!
How is this done? Scheduled task?
Don’t get me wrong. Being able to have the USER “Schedule” the retry of the installation would be awesome.
For Intune at least, it depends on what you do with the exit code. We now use 1602 as it gives a prettier error within Intune, however if you were to set it up as an explicit retry value, Intune will retry again every 5 minutes for a total of 3 times before giving up, then I believe retrying in 24 hours.
While I’ve made the above parameter a double so floating point values can be expressed, it shouldn’t be assumed that an install will magically pop back up on the screen in 6 hours time just because -DeferDays 0.25 was specified.
The Intune retry time is one of my biggest frustrations as it isnt very “user friendly”.
We set the old exit 60012 (until I have time with the new v4.1 PSADT) to “retry”, are we saying there is an exit code to delay the five minute retry rule?
Apologies for any confusion here. I’m not suggesting this change can change the frequency in which Intune retries a deployment, it simply gives you more granularity for how many days a user can defer for.
In 4.1.0, there’s -DeferRunInterval to set a timespan between the last deferral and the next attempted run. If it’s set for 4 hours but Intune tries again in 3 hours, it’ll silently defer again without impacting the user’s remaining deferrals.
Ah ok. Thanks for explaining. Microsoft has designed Intune to be self served “available” and not really thought about if deployments should be required. its a pain when you have a mass upgrade but still want the interaction deployments.