question

Steve-3491 avatar image
0 Votes"
Steve-3491 asked Steve-3491 edited

Custom Fast Retry return code behavior for applications

When setting a custom Fast Retry return code for an application that is deployed as available or required, specifically when using PSADT, does that mean the failed install (because of a deferral) that matches the custom Fast Retry return code should attempt to launch the deployment until success every two hours (up to 10 times), logged in or not?

I'm trying to determine if a Fast Rety return code is similar to running the Application Deployment Evaluation Cycle (when running a required deployment) which launches the install and if there's any difference between required and available application deployments, logged in or not, for Fast Retry return code behavior.

mem-cm-application
· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

At least for the available deployment test, there was no attempt to automatically re-run the install two hours after a custom Fast Retry code failure referenced in the application which matched the client failure code. I need to perform some additional testing to confirm, but for a required deployment, the install did run again approximately 2 hours after the first Fast Retry failure.

0 Votes 0 ·
Steve-3491 avatar image
0 Votes"
Steve-3491 answered Steve-3491 edited

My testing showed that the Fast Retry return codes are only applicable to required application deployments at least when using PSADT. Software Center will show the next retry date and time under status for only for required deployments. Additionally, the first fast retry was not exactly two hours and ranged from 1 hour and 47 minutes to two hours and 28 minutes after a install deferral (60012 return code) on two different hosts,

Subsequent fast retries were every two hours (sometimes adding an additional second) . Fast Retry is essentially the same as launching the Application Deployment Evaluation Cycle (only for the app being deployed) in that it will kick off the install again every two hours.

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

AllenLiu-MSFT avatar image
0 Votes"
AllenLiu-MSFT answered

Hi, @Steve-3491
Thank you for posting in Microsoft Q&A forum.

Here is the definition of Fast Retry:
Fast Retry: Another installation is already in progress on the device. The client retries every two hours, for a total of 10 times.

I think this behavior have no difference between required and available application deployments.
You may check User Experience of the deployment type when you test for the available deployment, whether you have selected the "Determine behavior based on return codes"?
128945-1.jpg

And this behavior is not similar to running the Application Deployment Evaluation Cycle, the cycle reevaluates the requirement rules for all deployments.
For the details:
https://docs.microsoft.com/en-us/mem/configmgr/core/clients/deploy/about-client-settings#schedule-re-evaluation-for-deployments


If the response is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.



1.jpg (71.3 KiB)
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.