Article ID: 828776
Article Last Modified on 10/27/2006
APPLIES TO
- Microsoft Systems Management Server 2.0 Standard Edition
SUMMARY
After a user logs on to a computer that has the Systems Management Server (SMS) 2.0 client software installed, advertisements that are assigned to the user may not run. This article discusses troubleshooting steps to help an SMS administrator resolve the issue.
MORE INFORMATION
SMS 2.0 uses the following steps in the order presented to determine if a user is logged on to the Computer:
- SMS 2.0 confirms that the smsclitoknacct& account has SEDebugPrivilege permissions.
- SMS runs a query to determine whether Launch32.exe is running. If SMS finds Launch32.exe, SMS determines that the user is logged on.
To troubleshoot advertisements that do not run when a user logs on to the computer, try the following methods to help determine the problem:
- Open the %Windir%\Ms\Sms\Logs\Launch32.log file and see if the time stamp at the bottom of the log is current. A current time stamp indicates that Launch32.exe successfully started.
- Search the %Windows%\Ms\Sms\Logs\SMSMon32.log file for any errors in the GetSMSShellProcessHandle. If the GetSMSShellProcessHandle returns a NULL, it was not able to determine if Launch32 .exe was in the task list. You can use Task Manager or Tlist.exe to determine if Launch32.exe is running. Tlist.exe is included in the Microsoft Windows 2000 Support Tools and the Microsoft Windows NT 4.0 Resource Kit.
- Use process counters in Performance Monitor to determine if Launch32.exe started. If the Launch32.exe Process counter is not available in Performance Monitor, it may have encountered a problem. As a result, it may have been disabled. In this situation, the SMS client cannot determine if a user is logged on.
For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
248993 PRB: Performance Object Is Not Displayed in Performance Monitor
Keywords: kbbug KB828776
