Microsoft KB Archive/829863

= Advertisement Has a Status of &quot;Succeeded&quot; Even Though the Packaged Program Has Not Run On the Client Computer =

Article ID: 829863

Article Last Modified on 10/27/2006

-

APPLIES TO


 * Microsoft Systems Management Server 2003

-





SYMPTOMS
In the Status column of an advertisement, &quot;Succeeded&quot; appears even though the program has not run yet on the client computer.



CAUSE
This problem may occur if client computers run the Microsoft Systems Management Server (SMS) 2003 Legacy Client and all the following conditions occur in the order that they appear in the following list:
 * 1) You create a package to run a program, and you select the Only when a user is logged on option in the Program can run list in the Properties dialog box of that program.
 * 2) You make that program dependent on another program where you select the SMS logs user off option in the After running list in the Properties dialog box of that program.
 * 3) You advertise the first program.
 * 4) The user does not log on the computer again after the second program runs, and SMS logs the user off.

This problem occurs because, when a program is a part of a dependent program chain, the SMS 2003 Legacy Client does not send an additional &quot;Waiting for user condition&quot; status message after it sends the first status message. In this or a similar scenario, when the advertisement is processed, the SMS 2003 Legacy Client sends a &quot;Waiting for user condition&quot; status message. When the user condition is met, the dependant program runs. After the dependant program runs, SMS 2003 Legacy Client sends a &quot;Succeeded&quot; status message. However, in this particular case, it does not then send an additional &quot;Waiting for user condition&quot; status message while it waits for the user to log on the computer again.



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section of this article.



MORE INFORMATION
When you advertise a package that runs a program that has dependencies on a child program, different problems may occur, depending on the options that you select in the After running list of that child program (the program that the advertised program depends on). You can select from the following options:
 * SMS restarts computer
 * Program restarts computer
 * SMS logs user off

Mandatory Assignments
For advertisements where you configure a mandatory assignment, the option that you configured in the After running list in the child program performs its action, and then the SMS 2003 Legacy Client or the SMS Advanced Client sends a &quot;Waiting for user condition&quot; message to the SMS server.

The following table describes the cases where the client program sends a &quot;Waiting for user condition&quot; message in this scenario:

Optional Assignments
For optional advertisements, the SMS Advanced Client never sends the &quot;Waiting for user condition&quot; status message. The SMS 2003 Legacy Client only sends the &quot;Waiting for user condition&quot; status message if you select one of the following options in the After running list:
 * SMS restarts computer
 * Program restarts computer

The SMS 2003 Legacy Client does not send this status message if you select the following option:
 * SMS logs user off

The following table describes the cases where the client program sends a &quot;Waiting for user condition&quot; message in this scenario:

Keywords: kbpending kbbug KB829863

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.