What's New in SMS 2003 Service Pack 3
System Requirements for SMS 2003 Service Pack 3
A description of minimum requirements necessary for the proper installation and operation of SMS 2003 SP3.
Asset Intelligence
This add on extension of SMS 2003 enhances the ability to track software licenses, upgrade readiness, and more.
Windows Vista support
A description of the Windows Vista™ Editions supported by SMS 2003 SP3.
64 bit processor support
Information regarding the extension of 64 bit support.
Accurate file size inventory above 2GB
File sizes greater than 2GB are now reported accurately.
Hotfixes incorporated into SMS 2003 Service Pack 3
A list of hotfixes that have been included in the SP3 upgrade.
Systems Requirements for SMS 2003 Service Pack 3
SMS 2003 Service Pack 3 introduces changes that affect the supported operating systems both for site server roles and for clients. For a complete list of system requirements for SMS 2003, see SMS 2003 SP3 Supported Configurations available at the Systems Management Server 2003 Product Documentation web site.
Site Server Requirements:
SMS 2003 Service Pack 3 Site servers have need of the following minimum requirements.
Software Requirements:
All SMS 2003 Service Pack 3 site system roles are supported only on systems running Microsoft® Windows® 2000 SP4 or later, or Microsoft Windows® Server 2003.
Internet Information Services (IIS) must be installed as part of the Windows Server installation for certain SMS site system roles.
SQL Server 7.0 SP4, SQL Server 2000 SP3a or later, or SQL Server 2005 or later can be used to host the SMS database for SMS 2003 SP3.
Hardware Requirements:
The following table shows the minimum hardware requirements for servers running SMS 2003 SP3.
Hardware component |
Requirement |
|---|---|
Microprocessor |
550 MHz or faster; Intel Pentium/Celeron family, or compatible processor recommended |
Memory |
256 MB of RAM (maximum 4 GB of RAM) |
Hard disk |
2 GB of available hard disk space on an NTFS partition |
Drive |
CD-ROM or DVD-ROM drive |
Display |
Windows 2000-compatible video graphics adapter |
Peripheral |
Keyboard and Microsoft Mouse or compatible pointing device, or hardware that supports console redirection |
Network |
Network adapter |
SMS Client System Requirements
SMS 2003 SP3 introduces the following changes in the way SMS Legacy and Advanced clients are supported.
Legacy Client Operating Systems
Installation of the SMS 2003 SP3 Legacy Client is not supported on any client operating system capable of Advanced Client installation.
Advanced Client Operating Systems
Installation of the SMS 2003 SP3 Advanced Client is not supported on client platforms less than Microsoft Windows 2000 SP4 or Microsoft Windows XP SP2.
SMS 2003 SP3 provides support for 64-bit server platforms as SMS Advanced Clients. It also offers full support for Windows Vista™ clients as an SMS 2003 SP3 Advanced Client.
Hardware Requirements:
The following table shows the minimum hardware requirements for SMS 2003 SP3 clients.
Hardware component |
Requirement |
|---|---|
Microprocessor |
300 MHz or faster recommended, 133 MHz minimum; Intel Pentium/Celeron family or compatible processor recommended |
Memory |
128 MB or higher recommended (64 MB supported but can limit performance and some features) |
Hard disk |
80 MB of available hard disk space |
Display |
Super VGA (800×600) or higher-resolution video adapter and monitor |
Peripheral |
Keyboard and Microsoft Mouse, or compatible pointing device |
Network |
Network adapter |
Asset Intelligence
The Asset Intelligence feature extends the capabilities of SMS 2003 to facilitate tracking of Microsoft software application licenses, provide administrators with compliance tracking reports and a means to control software piracy. By providing accurate software installation and usage data, in a readily digestible format, Asset Intelligence enables better evaluation of licensing needs and usage within an organization.
New capabilities include enhanced software identification, hardware upgrade tracking, and many new reports with drill through capabilities. Drill through reports make it easy to take a summary view of an organization's hardware or software and drill through to subsequent reports until the desired detail is achieved, even to the level of a comprehensive view of a single computer, including hardware, software, and license status.
The new Microsoft License Ledger reports are presented in a format congruent with Microsoft Licensing Statements to better facilitate license management. Information presented on these reports indicate such parameters as number of installations of a specific product, license status for each computer and software item, and sales channel for software licenses.
Added support for computers running Vista includes reports to monitor computers acting as Key Management Servers (KMS) and licenses nearing expiration. Additionally, a standard report indicates readiness for upgrade to Vista, identifying necessary disk, memory, and processor improvements for each computer.
Windows Vista Support
SMS 2003 Service Pack 3 adds support for Vista as an SMS client. Windows Vista Business Edition, Windows Vista Enterprise Edition, and Windows Vista Ultimate Edition are supported. Windows Vista Home Basic Edition and Windows Vista Home Premium Edition are not supported. For more information about supported configurations, see "SMS 2003 Supported Configurations for SP3" on the Systems Management Server 2003 Product Documentation web site.
64 bit Processor Support
SMS 2003 Service Pack 2 added support for clients running in 32-bit mode on 64-bit processors. SMS 2003 Service Pack 3 extends that support by adding a new class, Add Remove Programs (64), to collect 64-bit software inventory information from computers using 64-bit processors. For more information about supported configurations, see "SMS 2003 Supported Configurations for SP3" on the Systems Management Server 2003 Product Documentation web site.
Accurate file size inventory above 2GB
Virtual Machines and other advanced computing features depend more and more on large files. Prior to SMS 2003 Service Pack 3, inventoried file sizes were stored as a 32-bit integer. As a result, files larger than 2GB were reported with erroneous size information. SMS 2003 Service Pack 3 has increased this to a 64-bit integer, thus adding support for inventory of files much larger than 2GB.
Hotfixes Incorporated Into SMS 2003 Service Pack 3
KB Article |
Title |
|---|---|
240980 |
Smscfg.cpl may not be loaded with more than 20 network adapters |
830614 |
Systems Management Server 2003 bandwidth throttling does not completely use allocated bandwidth |
905751 |
Some packages are not uncompressed in the share folder on the distribution point in a multi-tier Microsoft Systems Management Server 2003 Service Pack 2 hierarchy |
915198 |
You may receive inaccurate reports when you run SMS hardware inventory reports on the parent site server |
915801 |
Error message when you use the Distribute Software Updates Wizard in SMS 2003 Service Pack 2: "Unknown error 0x80071017" |
915864 |
You cannot use any feature of Systems Management Server (SMS) 2003 Remote Tools to access an SMS client after you enter valid credentials |
916461 |
Collection members may randomly drop out of a collection on a Systems Management Server 2003 site |
916523 |
If an SMS 2003 site database is larger than 2 GB, the database size is reported incorrectly in the SMS Administrator Console |
917366 |
An error is logged when you use the Distribute Software Updates Wizard in the SMS 2003 Inventory Tool for HP ProLiant and Integrity Updates: "Install Failed" |
917367 |
After choosing to "Always accept" updates for a publisher, the Security Warning dialog still appears for each update signed by that publisher |
917369 |
Manual download of an update from properties dialog produces file hash error |
917435 |
Errors are logged in the sender.log file and the sched.log file on Systems Management Server 2003 |
918104 |
Multiple instances of the same SMS Legacy Client computer appear in the SMS 2003 Administrator console |
918914 |
The ddm.box inbox folder is backlogged with many DDRs, and the SMS database is not updated with newly created objects in Systems Management Server 2003 |
920108 |
The Manage Site Accounts tool does not add or modify Client Push accounts in Systems Management Server 2003 SP2 |
921309 |
Systems Management Server 2003 Distribute Software Update Wizard is unable to download custom update files when the UNC path name contains a space |
921463 |
Active Directory System Group Discovery may update the time stamp for SMS clients that no longer update their DNS records on a computer that is running SMS 2003 with Service Pack 2 |
921466 |
Unable to access Windows logon screen on a Systems Management Server 2003 Client computer when countdown dialog box appears |
923026 |
After you remove software updates from an SMS 2003 package, the package update link table incorrectly lists these programs |
924842 |
An SMS 2003 management point computer receives many 10907 status messages and stops responding |
924891 |
The languages of all the updates are listed as Portuguese (Brazil) when you run the Distribute Software Updates Wizard in SMS 2003 |
925142 |
Imported Package Definition Files that contain dependant programs are not run successfully on Systems Management Server 2003 clients |
925791 |
Systems Management Server 2003 clients cannot communicate with a management point when the management point computer name contains an underscore character |
926130 |
A re-imaged Systems Management Server 2003 Client computer is not discovered by the Active Directory discovery methods |
926617 |
You experience a performance problem in Replication Manager of Systems Management Server (SMS) 2003 |
927497 |
An incorrect organizational unit name appears in the Discovery data list of a discovered object after you run the Active Directory System Discovery method in SMS 2003 |
927723 |
Error message in the Sched.log file in SMS 2003 with Service Pack 2: "WARNING: Found duplicate Send Request ID already exists" |
932993 |
The Delete Aged Discovery Task can take a long time to complete when user or user group discovery is enabled |