After you advertise a program to a Legacy Client, the program never runs on the client in Systems Management Server 2003

Article translations Article translations
Article ID: 886069 - View products that this article applies to.
Expand all | Collapse all


After you advertise a program to a Legacy Client, the program never runs on the client. The advertisement status message in Status Message Viewer in the SMS Administrator console states that the client returns a 10002 status message. This indicates that the advertisement is received from the site. The client may also return a 10036 status message that is similar to the following:
The program for advertisement "Advertisement_ID" has not be run yet ("Package_Name" - "Program_Name"). The program settings indicate that this program has a user logon condition that must be satisfied before it can be run, and this condition has not yet been satisfied. SMS will run this program once the user logon condition is satisfied.
However, the client does not return a 10005 status message, a 10008 status message, or any error status messages. A 10005 status message indicates that the program started for the advertisement. A 10008 status message indicates that the advertisement completed successfully.

On the client, the following conditions are true:
  • In the Advertised Programs Monitor tool in Control Panel, the advertised program's Scheduled to Run property is always set to Next logoff.
  • The Smsapm32.log file in the %windir%\Ms\Sms\Logs folder shows that the Advertised Programs Monitor indefinitely reschedules the program to the next log off. However, the program does not actually run, and the client returns no status messages.


This problem occurs when you create a program to run only when a user is logged on with user rights and when the advertisement's assignment schedule is set to Assign immediately after this event: Logoff. This problem occurs only on Legacy Clients.


To work around this problem, set the advertisement's assignment schedule to make it assigned immediately after the logon event or as soon as possible.


This behavior is by design.


Article ID: 886069 - Last Review: October 27, 2006 - Revision: 1.2
  • Microsoft Systems Management Server 2003
kbprb kbsms2003spfix kbsms2003bug kbsmspackage kbsmsdistribution kbsmsadmin kbsmsclients KB886069

Give Feedback


Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from