Recently Microsoft released a critical update to IE (MS15-093 - 3087985). As such we created an Emergency patch deployment for this patch (not knowing there was a prerequisite). When we looked at the deployment in SCCM it showed compliant on the majority of the machines. However, when we went to the machines we did not see the update. We came to find out that MS15-093 had a prerequisite that was not on the machines (3078071).
This prerequisite update 3078071 is in our SCCM enviroment, downloaded and available to be deployed, but was not a part of the Emergency Patch Deployment
So my question is...
1. Why does SCCM show compliant when the patch was not installed?
2. How does SCCM manage pre-rerequisites during a normal patch process?
Our goal would be that on the night of the update deployment, the workstation checks for updates, installes required updates, reboot if needed, immediatly checks again for updates again, install updates, reboot, and <keep repeating> until all updates are installed. However it appears that the workstation only does 1 cycle and then has to wait for the next month to pick up any updates that had prerequisites.
You insight and assistance would be greatly appreciated.
- Edited by TE2011 13 hours 37 minutes ago Spelling