Advertisement Has a Status of "Succeeded" Even Though the Packaged Program Has Not Run On the Client Computer (829863)
The information in this article applies to:
- Microsoft Systems Management Server 2003
SYMPTOMSIn the Status column of an advertisement, "Succeeded" appears even though the program has not run yet on the client computer.CAUSEThis 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: - 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.
- 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.
- You advertise the first program.
- 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 "Waiting for user condition" 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 "Waiting for user condition" status message. When the user condition is met, the dependant program runs. After the dependant program runs, SMS 2003 Legacy Client sends a "Succeeded" status message. However, in this particular case, it does not then send an additional "Waiting for user condition" status message while it waits for the user to log on the computer again. STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section of this article.
Modification Type: | Minor | Last Reviewed: | 6/13/2005 |
---|
Keywords: | kbpending kbBug KB829863 kbAudITPRO |
---|
|