I have some percent of computers which runs into above state in monthly patch deployments. I could minimal information from execmgmr, udpatesdeployment.log, CliSpy and Client Center etc tools but that doesn’t offer much help to nail down the issue completely. Have any of you dealt to resolve such issue successfully ? Is there any efficient way to handle this ?
It seems I haveDeploymentA, waiting for the completion of DeploymentB, which in turn waiting for the completion ofDeploymentC. Is there any better approach I could take to nail down and resolve the issue. One of my finding is, KB articles installs (SCCM R3, SCCM Asset Intelligence) causes these issue as they restart (upgrade sort of execution) the agent during the execution, I need to confirm these
Vasu