Add Delay Counts to Deployment Status
Under Deployment Status, you have the basic tabs Success, In Progress, Error, Requirements Not Met, and Unknown. When an application delays installing due to selections in the deployment settings (i.e. "Delay enforcement of this deployment according to user preferences, up to the grace period defined in client settings") these return codes are shown as "Errors" in the deployment. This can throw off numbers in regards to how successful a deployment is. In the cases of a delayed deployment, SCCM hasn’t even tried to install the application, so why is that counted as an error? The proposal here is to create a category under Deployment Status to show delayed efforts. This would look for specific return codes (such as 0x800404E7) and categorize them as delayed instead of as an error. This can help the administrator then quickly identify those machines that have been delaying installs which ones have errors preventing an install that need to be addressed.
It would also be good for us to define custom Delay Codes. In some wrappers (such as PowerShell App Deployment Toolkit), there is an exit code that is used whenever a user delays an install. Within the properties of the deployment, you should be able to add a custom return code that indicates that the install was delayed and needs to be re-attempted.