16) 8/24/2004 826854826854  826854.html">How to troubleshoot problems that occur when you use SMS 2.0 or SMS 2003 to advertise programs to SMS clients
(826854) - Describes how you can troubleshoot common problems that may occur when you use SMS 2.0 or SMS 2003 to advertise programs to SMS clients.

17) 8/24/2004 324307324307  324307.html">Your Systems Management Server 2.0 client cannot upload software metering log files to the SMS site server
(324307) - Fixes a problem in SMS 2.0 where the offline software metering log files are not uploaded to the SMS site server. Symptom occurs if you specify a custom path for the SMS 2.0 installation files. Requires installation of a hotfix to resolve.

18) 8/10/2004 826848826848  826848.html">Overview of remote control video acceleration in Systems Management Server 2.0 and Systems Management Server 2003
(826848) - Describes how SMS can use video acceleration to increase the performance of remote control sessions.

19) 7/21/2004 837372837372  837372.html">How to identify SMS Executive process threads that are responsible for high CPU use on an SMS site server
(837372) - Describes how to troubleshoot the SMS Executive process when one or more of the SMS Executive threads is causing high CPU use on an SMS 2.0 site server or on a SMS 2003 site server.

20) 7/17/2004 840677840677  840677.html">Logon points are not created in a trusted domain in Systems Management Server 2.0
(840677) - Describes how to resolve a problem where logon points are not created in a different domain than the SMS site. Describes symptom details, the cause, and how to resolve this issue.

21) 7/16/2004 322461322461  322461.html">Some clients do not receive the advertisement after you advertise a package to a user group collection in SMS
(322461) - Describes a problem that may occur if you advertise a package to a collection that contains DBCS characters.

22) 7/15/2004 826841826841  826841.html">A list of the available remote control registry values on the Systems Management Server client
(826841) - Describes the registry entries that exist on client computers. You can use registry entries to manually force changes to the remote control settings on SMS client computers.

23) 7/8/2004 820200820200  820200.html">The SMSPackages_Del SQL trigger is removed after you install the hotfix or the SP4 hotfix rollup package
(820200) - Describes problem when you install the Q303848.exe file or the Systems Management Server 2.0 Service Pack 4 hotfix rollup package. The SMSPackages_Del SQL trigger is deleted. The resolution is to re-create the SMSPackages_Del SQL trigger.

24) 7/7/2004 811575811575  811575.html">The Advertised Programs Manager continues to run after the client components are removed during an upgrade of SMS 2.0
(811575) - Fixes a problem in the Advertised Programs Monitor that may cause SMSapm32.exe to keep running, even after the components have been removed.

25) 7/7/2004 840752840752  840752.html">"ERROR: Could not retrieve the Namespace Path" error message when you run Makecoll.exe remotely against a Windows Server 2003-based SMS provider
(840752) - Fixes a problem where you receive an error message when you run the Make Collection utility remotely against a Windows Server 2003-based SMS provider.

26) 6/29/2004 810282810282  810282.html">You cannot advertise a 16-bit program to Windows XP clients in SMS
(810282) - Describes a problem where you cannot successfully advertise programs that were compiled by using the "16-bit EXE" option to Windows XP clients. To work around this problem, compile your programs using the "32-bit EXE" option.

27) 6/29/2004 841826841826  841826.html">The package modifications that you make on an SMS 2.0 site server do not take effect on other site servers
(841826) - Describes a hotfix for a problem where your package modifications are not processed correctly. This hotfix updates SMS Distribution Manager so that it processes package files in the correct order.

28) 6/25/2004 841624841624  841624.html">The SMS Administrator console cannot display Windows Event Viewer, Windows Diagnostics or Windows Performance Monitor for Windows XP Service Pack 2 clients
(841624) - Describes an issue where you cannot use the SMS Administrator console to view some Windows XP Professional SP2 tools.

29) 6/19/2004 322588322588  322588.html">You cannot specify the location of the default Client Access Point when you install Systems Management Server 2003
(322588) - Describes how to specify the location of the Client Access Point after you install SMS 2003, because you cannot specify the location of the Client Access Point (CAP) during the installation of SMS 2003.

30) 6/17/2004 279868279868  279868.html">Using reserved names as site codes in Systems Management Server
(279868) - Because AUX, CON, NUL, and PRN are reserved names in Microsoft Windows, Microsoft does not recommend that you use these names as site codes when you install Microsoft Systems Management Server.