Ran successfully in a user session the log is 61 346 events. It seems there is something in the tool preventing it to run anywhere except from within a logged on session.?Īfter running PROCMON, something strange is happening.

If I run the exact same script with the exact same userX credential but from a Scheduled Task or as a Windows Service, it doesn't work!

We have hundreds of docking stations to update.Right now, we would have to do it manually by logging in and running the script.This is a nightmare.Īlso, if I test running the command within a logged on session, let's say userX, it works. Having to log in and run the command defeats all automation possibilities. The goal is to deploy the firmware update via SCCM overnight when it's safe to do so. The EXACT same script is ran (simply ThinkPad_Hybrid_Dock_TVSU_FW.exe /all /silent):ġ-In SYSTEM session (via sccm or scheduled task) it ALWAYS fails with: Update fail.Ģ-In a logged on user session, running the EXACT same script in the EXACT same way, it ALWAYS works: Update success.Īny idea if this is by design? What could prevent it from running in the SYSTEM account? This destroys the purpose of having a /silent switch. The goal is to update the docking station's firmware. I am using the Lenovo Firmware Update Tool:

Lenovo docking station firmware update