List of Bugs Fixed in Systems Management Server 2.0 Service Pack 5 (816549)

MORE INFORMATION

• Sound card drivers and other processes may use the SMS Client Token account (SMSCliToknAcct&) to connect to other computers over the network. When this occurs, an account lockout results because a local SMS Client Token with a unique password exists on each computer. This is particularly problematic when a process or driver on a workstation connects to a domain controller by using the SMS Client Token account context. This can cause a lock out of the token account for all domain controllers, blocking software distribution to the domain controllers.
• Site-to-site communication is now encrypted with digital signatures to increase security. This makes it more difficult to use"packet sniffers" to obtain site-specific information.
• When you click Add to add a new user in the SMS User Wizard, and then click Browse , the Browse window that appears does not show the local domain. Only accounts in child domains are listed.

• An access violation occurs if Available Programs Manager (APM) cannot access a remote file (.ins, .ofr, .pkg, .ico, .lkp).
• The Advertised Program Manager Spy tool, Apmspy.exe has been rebuilt for release with SP5. This is necessary because the dependant Clibase.dll file has changed.
• The package offer file (.ofr) and the instruction file (.ins) are not removed when the collection is deleted. The advertisement is still available to the client.
• Packages that use command line switches fail on Microsoft Windows XP clients if the Software Installation Account (NTPush) is used. When you try to distribute a package by using a Software Installation Account and targeting Windows XP clients, the package does not complete successfully. This occurs when either the program command line uses a switch or the command line switches are called inside an installer package.
• If you advertise a program that was generated by the SMS Installer, to Windows XP clients and specify Use Windows NT client software installation account in the program properties, the advertisement fails. However, the advertisement executes as you expect if only Run with administrative rights is selected.
• Microsoft Windows 2000 clients fail to run advertised programs if Run with NT client installation account is specified.
• Advertisements targeted to a computer only present the APM"new software available" notification icon for users who log on to a computer later. This occurs although the advertisement was successfully run by a previous user.
• The Apmspy.exe tool has been improved. The tool can now display more offers than in previous version. The tool is now compatible on computers that are running Windows XP and Microsoft Windows Server 2003.
• SMS 2.0 sites cannot read the instruction file created by Courier Sender from an SMS 2003 site. Because the file is not in the expected SMS 2.0 format, the SMS 2.0 site rejects the file as corrupted. The Courier Sender logs the following:".ins has a bad internal format".

• An account with the same name as one of the default administrator accounts listed in the Permitted Viewers list may obtain remote control access to a client. To increase the security of the permitted viewers list, SP5 makes it possible for the default administrator account to connect to a remote control client, even if the administrator account is not listed in the permitted viewers list. This makes it possible to secure the permitted viewers list by removing all the default entries (international administrator accounts). The security ID (SID) for the administrators group has been hard-coded in the product as a Permitted Viewer. This makes it possible for you to clear the permitted viewers list for increased security while making it possible for administrators to remote control clients.
• If the Software Metering component of the SMS Executive service does not upgrade during an SMS installation, the whole SMS site may stop responding. This might prevent the processing of packages and inventory.
• Client drivers such as mouse, keyboard, and mirror fail to upgrade when you apply a service pack.
• When you log on to a client computer with a low rights user, License Metering uses offline mode. This occurs because the License Metering client uses the logged on user account, and it may not have sufficient permissions to create the Dbup.ini file on the server. SP5 makes it possible for low-rights users to create this file.

• SMS NT Server Discovery adds erroneous data to the System Discovery Internet Protocol (IP) Address Array properties.
• Microsoft Windows Logon Point Installation no longer requires domain administrator permissions to create the Logon Point directory structure as no SMS service is installed. The Network Access Layer (NAL) code has been changed to access the IPC$ share instead of accessing the Admin$ share. The Admin$ share requires domain administrator rights.
• SMSCliSvcAcct& is configured to recycle passwords. You can apply a Group Policy Object to a computer that limits the maximum password age, affecting the functionality of the SMS Client. Before SP5, as soon as the password expired, the client had to be reinstalled to establish a new password.
• All installed client components enter a Repair Pending state when you upgrade a Microsoft Windows 2000 client to Microsoft Windows Server 2003. This occurs because the registry permissions are incorrectly set during the upgrade by the Client Configuration Installation Manager (CCIM).

• SP5 adds support for Microsoft Windows 2003-based computers. Administrators can now create queries and collections based on Windows 2003.
• When an advertisement contains a program name with a special character, such as a backslash ( \ ) or a quotation mark ( " ), you may receive the following error message:
  "_com_error exception in MMC Admin UI!"
• The SMS Senders on Windows 2003 computers improperly retrieve the most recent error message, instead of the actual error message that occurs. You must restart your computer to obtain the correct error message code.
• Previous service pack installations did not write the full version number to the Smssetup.log file. Only a version number of 2.0 and a build number of 1493 was reported. This made it difficult to determine which service pack level was currently installed, and which service pack level was being installed. SP5 now adds the current full version (2.00.1493.XXXX) and the future full version (2.00.1493. SP level ) to the Smssetup.log file.
• Bad Discovery Data Records (DDRs) are created in Windows Server 2003 domains. The Name field of the DDR has a limit of 64 characters, causing Discovery Data Manager (DDM) to fail to parse the .ddr file. SP5 now calculates the length the Name field must have.
• Secondary Site installation or upgrade fails on computers that are running Microsoft Windows NT 4.0 Server. Setup does not create the SMSServer_<sitecode>account.
• The Network Monitor Control Tool has been removed. The support files that the Network Monitor Control Tool must have are not supported on Windows Server 2003 computers. The Network Monitor tool is still available.
• SP5 offers secure communication between sites. SMS sites now exchange signed instructions by using public keys between sites. The Preinst.exe file in SP5 provides functionality to create files that contain public keys. The new Preinst.exe file is available on the release CD and is installed to the \SMS\bin\$(PLATFORM) folder on the SMS site computer.
• An impersonation error occurs when you refresh Status Message Queries in the SMS Administrator console on computers that have Windows NT 4.0 Service Pack 6 (SP6) and WBEM 1.1 installed.
• The International Client Pack (ICP) setup does not prevent installation onto a non-English Secondary site. This occurs when the Secondary site was installed by the Primary site over the network. During this push operation, the language setting in the registry of the Secondary site is not correctly created. The language key is correctly set in the registry of Secondary sites that is created by using the SMS CD.
• When you use the SMS Administrator console to remove a Secondary Site, the removal may consume 100% CPU resources on the Secondary site computer. The Secondary site removal continues and never stops. This may occur when conditions on the Secondary site computer generate a Retry/Cancel dialog, however the dialog prompt is never displayed. SP5 intercepts this dialog and permits the removal to complete.
• Previous versions of service pack setup would install on SMS installations with newer service packs installed. For example, Setup would permit installation of Service Pack 3 (SP3) on an SMS site that already had Service Pack 4 (SP4) installed. SP5 Setup verifies an older version is installed before applying the new service pack.
• Previous ICPs would install on older service packs. For example, the SP4 ICP installs on a site server that has SP3 installed.
• When you perform an Unattended installation of SMS 2.0 on a Microsoft Windows 2000 Domain Controller in Native Mode, the SMS_KEY_CREATION_SERVICE generates an error 997. This can prevent the Site Component Manager (SCM) from receiving the correct password, and results in SCM failure.
• The SMS 2.0 SP5 Administrator console cannot administer an SMS 2003 site database. An error is logged in the SMS Provider log on the SMS 2003 site.
• The SMS 2.0 service pack setup permits you to install an SMS 2.0 Administrator console over an existing SMS 2003 Administrator console. When you run setup for the SMS 2.0 service pack, the option to"Install the sms administrator console and related tools" is not activated. However the option to"Upgrade an existing sms installation" is activated. If you select the upgrade button, the SMS 2003 files are overwritten by the SMS 2.0 files.
• Event 7000 is generated in the Application Event Viewer log when you try to install a second Client Access Point (CAP). The Sitecomp.log file records, " Could not start service SMS_SERVER_BOOTSTRAP_H305. The operating system reported error 997: Overlapped I/O operation is in progress. " in the log file. This occurs because the new service has not yet replicated to all domain controllers. With SP5, SMS 2.0 waits for the account replication to complete.
• When you upgrade an SMS 2.0 site to a new version by service pack or hotfix bundle, the upgrade may fail and you receive the following error message:
  Could not create trigger 2K_Application_Info__DATA1_ins on Y2K_Application_Info__DATA1

Previous Service Packs