I've got a application deployment running in my environment being pushed to roughly 10k clients. It's a simple script and initially deployed quite well, hitting 81% success in the first 24 hours. Then something seems to have changed and clients that were previously designated as "success" started jumping ship and being reclassified as "in progress", dropping my success percentage from 81% to 65% and now down to 42% over the past 3 days. The good news is that the "error" state has stayed roughly stable at <1%, but I have no idea what might be causing the deployment to change states from "success" to "in progress" again on such a massive scale.
Additional odd behavior: There is a large discrepancy between what I see on the Monitoring Deployment overview and the drill-down of the application monitoring. In the deployment monitoring overview I'm seeing about 5.3k systems with the "in progress" status. However, when I drill down into the deployment, and look at the specific "in progress" line items, adding them up comes to less than 1k. Conversely the total systems in the "success" category showing in the monitoring overview (4.6k) match exactly to those in the drill-down under success. The difference between the two "in progress" figures simply don't appear in the drill-down at all (not under Error, Requirements not met or Unknown), they just seem to be gone.
To cover a couple of obvious things. No changes have been made to the deployment since its inception. Content was successfully pushed to all DP's and has not been updated. The script running is a simple in-house script and is detected with a registry value looking at a specific version number. It is configured to be hidden/silent and is invisible from an end user perspective.
Any ideas on what might be happening? I haven't found any logs either on the server or any of the clients that help me here, are there any specific logs I should be looking at? Thanks,
Rob