Greetings. Either I am missing something or misunderstanding the DeferRunInterval parameter. For now, I am just testing and not utilizing in ConfigMGR or Intune, just testing locally.
When I run the PSAppDeployToolkit installation (using Adobe Reader DC source) and click on the defer button (just 2 deferrals for now for testing), my expectation is the PSAppdDeployToolkit UI would close and then reappear one minute later with one less deferral left. However, the UI does not come back up at all and the powershell.exe or other processes related to PSAppDeployToolkit are not running.
This is what I am using below for the parameters:
Show Welcome Message, close processes if specified, allow up to 3 deferrals, verify there is enough disk space to complete the install, and persist the prompt.
$saiwParams = @{
AllowDefer = $true
DeferTimes = 2
DeferRunInterval = [TimeSpan]::FromMinutes(1)
CheckDiskSpace = $true
PersistPrompt = $true
}
This isn't how that parameter works. It's to ensure that Intune or whatever's retrying the deployment doesn't retry too soon. Say Intune was retrying every hour, but you wanted 4 hours between retries, you'd set this to 4 hours so nothing showed until at least 4 hours had lapsed. There's not much else we can really do for things like this.
Just to share my experience so far and how I'm using this parameter.
We are deploying an application via Intune in the required context, we give the user's an option to defer until the deadline is reached. When the user's defer, Intune detects as a failure and then will retry but with this parameter it won't show a prompt to the user since the interval has not lapsed.
If Intune then tries to run the app again but the interval is still within the window, it won't prompt the user.
Once window has passed and Intune tries again, the user will see the prompt.
I understand it as Intune being a mindless binary tool that simply see's it as either an 1 or 0, in this context if it's 0 it will retry until it get's a successful install code back from the client but the parameter stop's Intune simply executing the script because it wants to desperately get a successful install.
In testing, I simply set the interval to 1 minute and then re-run the PS as install / Interactive after 1 minute as passed, if you check the logs in PS ISE you will see the log show it set the defer history and the next time the window lapses so you can manually run it again.
Am I right in thinking that after the deadline is reached, the script will simply run the install since deadline has passed? But if I'm still within the grace period until the deadline I can defer as much as I want even if i say the DeferRunInterval to something like 1 minute or more?
Hope this helps.
When you defer, PSADT exits with an error code that tells Intune that the user has cancelled the installation.
Intune will then retry whenever it feels like to try again. usually 8-24 hours later.
The PSADT Defer functionality does not magically coordinate with Intune to retry the installation.
I don't use the feature so I can't comment more on this.
PS: Next Time, please start your own threads as it confuses future readers.
Thanks, makes sense — I was mainly describing how DeferRunInterval helps suppress repeated prompts when Intune retries.”