Hotfixes Included in SMS 2003 SP2
The hotfixes listed in the following table are included in SMS 2003 Service Pack 2.
KB Number |
KB Title |
836553 |
The Schedule.box folder becomes backlogged with job files in large SMS hierarchies |
841381 |
Software inventory component performs a full delta software inventory on an SMS 2003 client computer after a daylight-saving time change occurs |
843023 |
The Re-run command is unavailable when a user tries to rerun an advertisement in Systems Management Server 2003 |
843219 |
MIF files build up in the Badmifs folder, and SMS client inventory information is missing in Systems Management Server 2003 |
843362 |
Users of the SMS Administrator console with only Read permission to a collection can install SMS clients |
872772 |
Other child sites are unexpectedly removed after you delete a child site from the parent site in Systems Management Server |
872811 |
Active Directory User group names have a backward slash mark inserted and are truncated during Systems Management Server 2003 Active Directory User Discovery |
873395 |
"Please enter a three-letter site code" error message when you use the Systems Management Server 2003 Administrator Console to modify the address of a child site |
883496 |
Client Access Points are installed to the default NTFS file system drive when you use the No_SMS_on_drive.sms file in Systems Management Server 2003 |
884053 |
Advanced Clients on a VPN connection cannot locate the management point in Systems Management Server 2003 |
885266 |
A registry entry remains on a Systems Management Server 2003 Advanced Client computer after you remove a software update that was built by using the Windows Installer version 3.0 SDK |
885278 |
A race condition occurs when more than one Sender thread tries to process the same send request at the same time in SMS 2003, SMS 2003 SP1, and SMS 2.0 SP5 |
885438 |
An SMS 2003 management point is not rolled back to a previous state after you remove a management point hotfix |
886136 |
A package is sent to the wrong clients or is not sent at all if you try to distribute a package to a collection that is based on a query in Systems Management Server 2003 |
886197 |
64-bit versions of Windows Server 2003 and Windows XP do not appear in the supported platforms list in Systems Management Server 2003 |
886685 |
Sending request files (.srq) are not processed and site routing packages are deleted before the routing request file is processed in Systems Management Server 2.0 |
886687 |
"Failed source list update for product" error message is logged in the Srcupdatemgr.log file on a Systems Management Server 2003 client computer |
886797 |
Some users do not receive a program that is advertised to a user group in Systems Management Server 2003 |
886902 |
The CCM component in Systems Management Server 2003 tries to install the Advanced Client on 64-bit versions of Windows even though the Advanced Client is already installed |
887603 |
The Backup SMS Site Server task does not run when it is scheduled to run in Systems Management Server 2003 |
888311 |
Deploying an operating system by using the Operating System Deployment Feature Pack fails when Active Directory sites are used as site boundaries in SMS 2003 |
888987 |
Status message 2715 is generated many times after you install the Device Management Feature Pack for Systems Management Server 2003 |
889162 |
You cannot use the Active Directory System Group Discovery discovery method in SMS 2003 to retrieve the additional Active Directory information about certain computers that are assigned to this Active Directory |
890193 |
An "Access denied error" entry is added to the Ccm.log file if the client push process tries to install the Advanced Client on an SMS 2003 site server |
891513 |
You may receive an empty result when you try to run a report by using the built-in Reporting feature in Systems Management Server 2003 Service Pack 1 |
892351 |
The "Windows Security" dialog box may intermittently lose the focus after you enable the SMS Remote Tools Client Agent service on SMS 2003 Advanced Client computers |
894604 |
SMS Management Point can Return Uncompressed Data |
895539 |
SMS 2003 Advanced Client takes lots of time to download many policies |
896602 |
SMS-related registry keys and registry values may appear in incorrect locations in the registry in SMS 2003 |
897074 |
The SMS 2003 Administrator Console shows a package status as "Install Pending" even when the package files are installed on the distribution point |
828205 |
The site server computer does not appear as an assigned client in Systems Management Server 2.0 |
831670 |
An expired advertisement reruns on clients after you reactivate the advertisement in SMS 2.0 |
831757 |
SMS 2.0 APM fails with the entry "The local device name is already in use" in Smsapm32.log when you use the software installation account |
836432 |
Large MIF hardware inventory files process slowly in Systems Management Server 2.0 |
838655 |
The SMS Discovery Data Manager component may take a long time to process discovery data records after the component starts in Systems Management Server 2.0 |
883492 |
User folders are removed when an administrator tries to reinstall the Systems Management Server 2.0 client |
886685 |
Sending request files (.srq) are not processed and site routing packages are deleted before the routing request file is processed in Systems Management Server 2.0 |
891565 |
The Microsoft Systems Management Server 2.0 Scheduler component cannot schedule a master send request |