Article ID: 917676 - Last Review: October 27, 2006 - Revision: 1.4 A Systems Management Server (SMS) 2003 Advanced Client computer may be slow to receive SMS advertisementsSYMPTOMSIf you distribute software to a Microsoft Systems Management Server (SMS) 2003 Advanced Client computer, the computer may take longer than you expect to receive and run the SMS advertisement. If you examine the Ccmexec.log file on the client computer, you may not see any updates to this file for up to several days. This problem may occur if all the following conditions are true:
CAUSEThis problem occurs when many users are logged into the Terminal Server, but no one is logged into the console session. In this scenario, SMS Agent Host (Ccmexec.exe) is busy processing logon notifications. Therefore, policy processing from the Management Point may be delayed. WORKAROUNDTo work around this problem, you must configure the ShellWaitTime registry value.
For more information about how to configure the ShellWaitTime registry value, click the following article number to view the article in the Microsoft Knowledge Base:
870653
(http://support.microsoft.com/kb/870653/
)
The SMS Agent Host service may take as long as 15 minutes to quit on an SMS 2003 Advanced Client
Alternatively, work around this problem by making sure that someone is always logged into the console session on the client computer.Starting with Systems Management Server 2003 Service Pack 3 (SP3), the following entry will be listed repeatedly in the CCMExec.log file when this problem occurs and verbose client logging is not enabled: WTSQueryUserToken[2](SessionID=0) failed with GLE=1245 STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. | Article Translations
|
Back to the top
