Why running "wuauclt.exe /detectnow" in a Sofware Delibery Job is not doing anything?
Article ID: 107450
Updated On:
Products
CA Automation Suite for Data Centers - Configuration Automation
CA Client Automation - Asset Management
CA Client Automation - IT Client Manager
CA Client Automation
CA Client Automation - Remote Control
CA Client Automation - Asset Intelligence
CA Client Automation - Desktop Migration Manager
CA Client Automation - Patch Manager
Issue/Introduction
When a Software Delivery is used to force Windows Updates by running "wuauclt.exe /detectnow" nothing happens but works fine using psexec.
Environment
CA Client Automation - all versions
Windows versions up to Windows 8.1 as Windows 10, Windows 2016 and newer use "UsoClient.exe startscan" as mentioned in https://blogs.technet.microsoft.com/yongrhee/2017/11/09/wuauclt-detectnow-in-windows-10-and-windows-server-2016/
Windows versions up to Windows 8.1 as Windows 10, Windows 2016 and newer use "UsoClient.exe startscan" as mentioned in https://blogs.technet.microsoft.com/yongrhee/2017/11/09/wuauclt-detectnow-in-windows-10-and-windows-server-2016/
Cause
Software Delivery jobs run under LocalSystem account in a non-logged on session.
But, can be different causes for the lack of action after run the command as mentioned in https://social.technet.microsoft.com/Forums/windows/en-US/3a135ae3-3e69-4086-802e-2a7b59460b16/wuauclt-and-other-questions-about-wsus?forum=winserverwsus
But, can be different causes for the lack of action after run the command as mentioned in https://social.technet.microsoft.com/Forums/windows/en-US/3a135ae3-3e69-4086-802e-2a7b59460b16/wuauclt-and-other-questions-about-wsus?forum=winserverwsus
Resolution
/resetauthorization has been used and worked fine.
The following syntax must be used and with the same parameter order: wuauclt /resetauthorization /detectnow
The following syntax must be used and with the same parameter order: wuauclt /resetauthorization /detectnow
Feedback
Yes
No
Powered by
