%11The program for deployment "%1" failed ("%4" - "%5"). A failure exit code of %2 was returned.
User context: %9%12
Possible cause: Configuration Manager determines status for each program it executes. If Configuration Manager cannot find or correlate any installation status Management Information Format (MIF) files for the program, it uses the program's exit code to determine status. An exit code of %2 is considered a failure.
Solution: For more information on the exit code, refer to the documentation for the program you are distributing.%0
The program for deployment "%1" completed successfully ("%4" - "%5"). The success description was "%3%7%8%9". User context: ...
The program for deployment "%1" completed successfully ("%4" - "%5"). User context: %9%12 Configuration Manager determines ...
The program for deployment "%1" could not be executed ("%4" - "%5").%12Additional program properties: Command line: %2 Working ...
The program for deployment "%1" could not be executed ("%4" - "%5").%12Additional program properties: Command line: %2 Working ...
The program for deployment "%1" failed ("%4" - "%5"). A failure exit code of %2 was returned. User context: %9%12 Possible ...
The program for deployment "%1" failed ("%4" - "%5"). A failure exit code of %2 was returned. User context: %9%12 Possible ...
The program for deployment "%1" failed ("%4" - "%5"). Operating System Deployment task sequences cannot run when the computer ...
The program for deployment "%1" failed ("%4" - "%5"). The failure description was "%3%7%8%9". User context: %2%12 Possible ...
The program for deployment "%1" failed ("%4" - "%5"). The program was able to be executed but the system was restarted unexpectedly ...