We're seeing errors in our App Deployment policies when they run on hosts when errors are overcome, such as PSremoting not being enabled initially, but then Nerdio enables the service and carries on fine, and with app installers exiting with a soft reboot code.
Could the error handling be improved to account for these so we don't end up with large numbers of failed tasks to cleanup?
Hi Rob Kayll , thanks for this suggestion - I will capture in our backlog and ask the development team to review options.
Could you possibly provide some specific examples of the issues encountered? This would help alot.
e.g. :
- App installed successfully
- installer returned reboot required (3010) exit code
- policy status is marked as failed
For the above, you have the option to include custom success codes to mitigate. Other examples would be great to see. Thanks!
The most common error we see is due to PSRemoting not being enabled. Other than that we occasionally get 3010 when an app requires a reboot.
How do we add a custom success codes to an app deployment policy & app groups?
Hi Rob Kayll - regarding the PSremoting issue, please could you raise a case with the support team?
Regarding custom success codes - This requires a private Winget repository to have been created, and the application imported into it. The change is made at the application level, not at the policy level.
The process is:
1. Select an application from the private repository. From the dropdown, select ‘Manage’
2. For the application version you want to define custom detection codes for, select the dropdown, then click on the installer you wish to edit.
3. You can now specify any additional success codes, as well as other useful options such as modifying the install switches.
I hope this helps with your issue!
Please sign in to leave a comment.
Comments (3 comments)