Timeout and Reset/Restart TransientError BITS jobs
We are having issues with the metadata on the update occupying the CPU on our SCCM management point which causes TransientErrors on any of the BITS jobs that are in process during the CPU timeout.
The problem is that the commands to reset the BITS queue on the SCCM clients don't work even in the built-in Administrator account with elevated powershell as there isn't "sufficient permissions." forcing us to reinstall the client on ALL of our machines.
SCCM BITS jobs should retry or rerun after being in the TransientError state for some time, maybe 15-30 minutes.
Jeroen Bakker commented
The BITS jobs can be removed when running under the system account.