Stuck on Executing BatchPatchRemoteAgent.exe

[doug]

It’s probably not actually “stuck.” You can see on the remote host if the “BatchPatchRemoteAgent.exe” is still listed in the running processes. If yes, then it’s still running. The Windows Update Agent has gotten slower and slower over time at searching for updates, in particular when run on machines with slow processors. Microsoft has released a number of updates to the Windows Update Agent over the past year, all with the intention of of improving performance in those cases, but we have found that it has been mostly unsuccessful. I have one machine that took 6 minutes to scan this month, and a second machine that took almost 3 hours. This isn’t a BatchPatch issue per se but rather is an issue with the Windows Update search on the target computer. Even when searching manually using the control panel GUI and not using BatchPatch, the machines that are slow with BatchPatch will also be slow with manual searching.

-Doug

[z10n]

batchpatch requires “batchpatchremoteagent.exe” installed correct? how do I do that to my host machine? where do can get it

[zzglenn]

Thanks Doug.

Yeah, its a mix. Some servers run a download, update, install within minutes and others just sit there for hours. Some will time out others will finish. Ok I will keep an eye on things.

z10n the remote agent runs when you execute a job from the batchpatch console. It will use psexec to send the agent to the target system to run. No need to install.

[Author]

Posts