Detailed explanation of Execution status for Patch Deployments

Detailed explanation of Execution status for Patch Deployments

I understand most of the possible status labels, but I'm unclear about a couple of things.

  • Yet to Apply- Sometimes a patch (or patches) are show this status but there is no obvious reason why the patch is not installing.  the computer is found on the network and has responded to a Patch Scan from Desktop Central.
  • Success - This seems obvious, but maybe it's not.  Does Success mean that the patch has been both downloaded to the target AND installed?  And if it was installed AND required a reboot, does it mean that the reboot has taken place?  We don't force a reboot on a subset of our workstations so it's difficult to assess the actual patch status with out knowing the meaning of Success.  Running another Patch Scan is possible (though time-consuming) and may yield unclear results.  I can say more about this after I get  some responses.
  • Failed - I assume this means that there was no download of the patch even after a number of Retries, but it could also mean that the patch was downloaded but not installed or that it was downloaded, installed but no reboot has taken place.
  • Not Applicable - patch Scan showed that a patch in the deployment was required by some of the machines in the group but not all, and this particular machine did not require it?
  • Retry in Progress - based on the number of Retries set in the deployment, DC is attempting to do one of the following:  download the patch, install the patch, reboot the workstation.

I realize that my questions may sound nit-picky or that I may have missed a crucial explanation somewhere in the documentation, so please point me to that resource that answers my questions.

Thanks

                New to ADSelfService Plus?