we are currently facing a major issue with patching , the issue is when we deploy microsoft patches to computer groups , machines in group they recive patches but not all the machines install updates in first time , some machines shows failed status . but next time when initate action on failed machines , then failed machines also recive updates and installed successfully.
& that happens in our all baseline.
so i wan’t to know the reson why not all machines successfully installed updates on first time , i don’t want to initate installation on second time.
some Actions i have taken form my side and verifed by my side on failed machines , those actions are below
on client wua version is verifed that is correct
wmi service is also running on all the machines
machines are reporting to correct relay
machine are up
bes client service is also running on those machine.
if any one has another reason . please let me know on urgent basis , so i can resolve the issue qucikly and share with you all.
Since these are third party patches being applied using BigFix as a messenger, the patches that are failing would need ot be investigated using the “Exit Code” being produced on the individual systems. If you have the same “Exit Code” on the majority of your systems, you’ll need to investigate what causes it and change your systems.
This seems like it’s a local issue to your systems.
its gets failed on atleast 2000 at a time and its very diffcult for me take remote of every machine check logs and find exit code.
any other soultion .please let me know
Well without much to go on, my first leap would be that your core server can’t retrieve the patches from the links within the fixlets. On your actions page, you should see a “Downloads” section that tells you whether or not your patches have been successfully cached. Ensure the downloads have completed there. If they display an error, troubleshoot that first.
