WSUS - Command Line installation of updates

Best Practices for authoring updates with command line installer.

Command line installs are not recommended since they do not provide progress information and have minimal error reporting, resulting in poor user experience for customers.

When using command line installers, Partner teams must ensure the following:
  • Always specify a return value for Success pending Reboot (typically this value is 3010)
  • Ensure the file specified is an executable
  • Ensure no UI is presented to the user (typically by using a command line argument like /q or /quiet). See the MU Policy (on http://muweb) for more info on this.
  • Never initiate a reboot, instead return an appropriate return value to indicate that a reboot is required
  • Map all custom return codes in the update metadata.

How to add custome error codes to command-line updates

You can add all your custom error codes returned by your EXE to the Windows Update Agent by mapping the values to two specific states that MU understands: Status (Succeeded, Failed, Canceled) and Reboot Required (Yes, No).

Error code range:
MU supports full 32-bit return codes eg (536871172). Partner teams are responsible for ensure their return codes do not conflict with system defined error codes or other codes already in use.

Required errors to add to Command-line updates
  • 0 – results Success
  • 3010 – results Success Pending Reboot (if your package returns Decimal)
  • BC2 – results Success Pending Reboot (if your package returns Hexdecimal)


Last edited Aug 10, 2009 at 6:08 PM by rhearn, version 1

Comments

No comments yet.