I tried running the PowerShell update script through Hexnode but it doesn’t seem to be working on some devices. Could the BITS service being disabled be causing this? How do I fix it?
I tried running the PowerShell update script through Hexnode but it doesn’t seem to be working on some devices. Could the BITS service being disabled be causing this? How do I fix it?
You’re spot on! The Background Intelligent Transfer Service (BITS) is required for Windows Update orchestration to work. If it’s disabled on any of your target devices, the script will fail silently.
Before running your main update script, remotely push this quick fix through Hexnode first:
|
1 2 3 |
# Ensure BITS is enabled and running for remote updates Set-Service -Name BITS -StartupType Automatic Start-Service -Name BITS |
This will re-enable and start the BITS service on the affected devices. Once that’s done, re-run your update script and it should work fine.
The main update script also automatically checks and starts both the BITS and Windows Update services as part of its built-in dependency verification step, so keeping your script updated ensures this is handled automatically going forward!
Regards,
Mary Romero
Don't have an account? Sign up