An advertised program does not run when a user logs on to the SMS 2003 Advanced Client computer (905794)


The information in this article applies to:

  • Microsoft Systems Management Server 2003
  • Microsoft Systems Management Server 2003 SP1

SYMPTOMS

Consider the following scenario. You advertise a program to a Microsoft Systems Management Server (SMS) 2003 Advanced Client computer. A user logs on to this SMS 2003 Advanced Client computer. In this scenario, the program that you advertised does not run. This symptom occurs if the following conditions are true:
  • The Assign immediately after this event setting is configured to Logon for the program's advertisement.

    Note The Assign immediately after this event setting is configured by using the Schedule tab in the Advertisement Name Advertisement Properties dialog box. You must click the button to add a mandatory assignment.
  • The SMS 2003 Advanced Client computer is running Microsoft Windows 2000, Microsoft Windows XP or a later version of Microsoft Windows.
  • A user logs on to the SMS 2003 Advanced Client computer and the following conditions are true:
    • The user logs on to the SMS 2003 Advanced Client computer after the computer restarts.
    • The user logs on to the SMS 2003 Advanced Client computer before the SMS Agent Host service has started.
  • It takes more than one minute from the starting of the operating system until the scheduler thread in the SMS Agent Host service starts.

RESOLUTION

To resolve this problem, use either of the following methods.

Method 1

To resolve this problem if the SMS 2003 Advanced Client computer is running Windows 2000, install the hotfix that is described in Microsoft Knowledge Base article number 825666. For more information about this hotfix, click the following article number to view the article in the Microsoft Knowledge Base:

825666 LastBootUpTime value does not update when you change the time zone

Method 2

Use this method if either of the following conditions are true:
  • The SMS 2003 Advanced Client computer is running Microsoft Windows XP or a later version of Microsoft Windows.
  • The problem that is described in this article is not resolved after you install the hotfix that is described in Microsoft Knowledge Base article number 825666.
To resolve this problem, edit the registry on the SMS 2003 Advanced Client computer. To do this, add a REG_DWORD MaxRestartTime registry entry that has a value of 5 to the following registry subkey:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\CCM\CcmExec

Note The value of the MaxRestartTime registry entry is set in minutes.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

MORE INFORMATION

If an advertisement is scheduled to run only when a user is logged on, the SMS Advanced Client computer uses two separate methods to notify the SMS scheduler that a user has logged on.

The SMS Agent Host service (Ccmexec.exe) subscribes to the StartShell event. The SMS Agent Host service subscribes by using the System Event Notification service (SENS) to automatically send a notification to the SMS scheduler when a user logs on. However, if the user logs on before the SMS Agent Host service has started and has registered its SENS subscription, the logon notification is not sent to SMS.

Note This subscription is deleted again when the SMS Agent Host service stops.

To handle this issue if a user logs on too quickly, the SMS Scheduler uses the following method when the SMS Scheduler starts.

If the following conditions are true, the SMS Scheduler generates a logon event to simulate the SENS StartShell event:
  • A user is logged on to the computer.
  • It has been less than 60 seconds since the computer restarted.
The SMS Scheduler detects when the computer was last restarted by querying the LastBootUpTime value. The LastBootUpTime value is located in the win32_operatingsystem WMI class under the ROOT\CIMV2 namespace.

Note If the SMS Scheduler generates a logon event, the following entry is added to the Scheduler.log file: Invoking Logon Triggers in startupNote This entry is added to the Scheduler.log file only if verbose client logging has been enabled.
Modification Type:MajorLast Reviewed:10/11/2005
Keywords:kbtshoot kberrmsg kbprb KB905794 kbAudITPRO
©2004 Microsoft Corporation. All rights reserved.