Export (0) Print
Expand All

Service Pack 2 Operations Release Notes

Updated : June 21, 2001

These release notes contain information about Microsoft® Systems Management Server (SMS) version 2.0 Service Pack 2 (SP2) that you need after you have successfully installed SP2 and that is not available in the product documentation. Please read this file thoroughly after you install the SMS software. See also the Installation Release Notes.

To search these Release Notes, press CTRL+F.

The compact disc that includes this readme file contains SMS 2.0 with all of the Service Pack 2 fixes incorporated. Throughout this document it will be referred to as the "SMS 2.0 SP2 compact disc"

If you have comments or suggestions about SMS 2.0, please send them to smswish@microsoft. com. We value your feedback.

Problems Addressed by this Service Pack

For the most recent information about the problems addressed by SMS 2.0 SP2, see the Microsoft Knowledge Base article Q258682, SMS: List of Bugs Fixed in Systems Management Server 2.0 Service Pack 2.

Upgrading: Client

Upgrading Multi-User SMS 1.2 Clients Running Windows NT 3. 51

If a computer running Windows NT 3. 51 is used by multiple users, multiple profiles are defined on that computer. If that computer is upgraded from SMS 1.2 SP4 to SMS 2.0 SP2, then some SMS 1.2 items might remain in user profiles. For example, a profile might retain the SMS 1.2 SP4 SMS Client program group.

Also during log on, an error message might appear stating the Smsrun32.exe file could not be found. This error occurs because Smsrun32.exe, was removed during upgrade and no longer exists and the file is trying to be run by Windows NT.

The HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Windows\load value equals Smsrun32.exe still exists in the registry and must be removed.

Note: These problems occur only on computers running Windows NT 3. 51.

WORKAROUND: If these conditions exist, take the following actions on the client computer for each affected user:

  • In the Program Manager, select and delete the SMS Client program group. Repeat this step for each affected user.

  • Using the Registry Editor (Regedt32.exe), open the HKEY_CURRENT_USER hive. In the HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Windows\load key, delete the Smsrun32.exe value. Repeat this step for each affected user.

The program group and error message will not appear on subsequent logons.

Remote Control of Windows NT 3. 51 SP5 Clients after Upgrade

Clients running Windows NT 3. 51 SP5 that have been upgraded from SMS 1.2 to SMS 2.0 SP2 cannot receive the remote CTRL+ALT+DELETE key combination from a Remote Tools session.

When an SMS 1.2 SP4 client running Windows NT 3. 51 SP5 is upgraded to SMS 2.0 SP2 with Remote Tools Client Agent enabled, the SMS 2.0 SP2 version of Kbstuff. sys is installed and then deleted from the <winnt>\system32\drivers directory. Because the remote CTRL+ALT+DELETE key combination uses Kbstuff. sys, the key combination does not work. Other Remote Tools including Remote Boot, Remote Chat, Remote File Transfer, and Remote Execute are not affected.

WORKAROUND: After SMS 1.2 is uninstalled and the client fully upgraded, open Control Panel and double-click the Systems Management icon on the client. On the Components tab, click Remote Control, and then click Repair Installation. This causes the client to reinstall the SMS 2.0 version of Kbstuff. sys in the <winnt>\system32\drivers directory. After it appears there, you must reboot the client in order for the key combination to work.

Note: This issue applies only to Windows NT 3. 51 SP5.

Client Components on a Client Running Windows NT are Not Restarted When Client is Upgraded to SMS 2.0 SP2

When the client is upgraded from SMS 2.0 or SMS 2.0 SP1 to SMS 2.0 SP2, all client components are stopped. Most components will be restarted, however Software Metering does not function, and software distribution packages scheduled to run in the user context cannot run immediately. Also, if the APM client component is enabled after upgrade and installed during the next client agent polling cycle, the user-context application launcher will not start. This prevents running any user mode packages on the client.

If a user is logged on, those components run in the user context cannot be restarted until the user-context application launcher (Launch32.exe), which is responsible for starting and monitoring SMS client components on computers running Windows NT, is restarted.

This behavior affects Software Metering and advertisements that are scheduled to run in the user context.

WORKAROUND: To restart Launch32.exe, have the user log off and then log back on to the client computer.

Installation: Server

Blank Passwords Not Recommended for SMS Accounts

In some cases, SMS 2.0 allows empty or blank passwords (that is, passwords that do not have any characters) for SMS accounts. You should never use blank passwords in your production environment.

WORKAROUND: For reasonable security, use a password of at least six characters, with at least one character from each of at least three of these groups: lower case, upper case, numbers, and symbols.

Installation: SMS Client

SMS Client Installation over RAS and Slow Line Speeds

Logon discovery and installation over a RAS connection does not work if the detected connection speed is lower than 40 Kbps, and the logon scripts have not been modified to accept a lower threshold.

Slownet.exe consistently detects line speeds that are slower than those reported by the dial-up adapter on the client. For example:

Client Modem

RAS Server Modem

Dial-up Reports

SLOWNET Reports

USR 33.6 Kbps

USR 33.6 Kbps

28.8 to 33.6 Kbps

35 Kbps

IBM 56 Kbps

USR 33.6 Kbps

28.8 Kbps to 57.6 Kbps

35 Kbps to 38 Kbps

IBM 56 Kbps

USR 56 Kbps

57.6 Kbps to 115 Kbps

56 Kbps to 116 Kbps

WORKAROUND: To modify the logon scripts to accept a connection speed threshold that is lower than 40 Kbps, make the following changes in the scripts:

  1. Back up SMSls. bat in the SMS\Data\NT_logon directory to SMSls. org.

  2. Modify the following lines in the SMS\Data\NT_logon directory\SMSls. bat file:

    OK_TO_PROCEED Replace: %SMS_LOCAL_DIR%\MS\SMS\CORE\BIN\SLOWNET.exe %0
    With: %SMS_LOCAL_DIR%\MS\SMS\CORE\BIN\SLOWNET.exe %0 1000

    SLOWNETUSER Replace: %SMS_LOCAL_DIR_USER%\MS\SMS\CORE\BIN\SLOWNET.exe %0
    With: %SMS_LOCAL_DIR_USER%\MS\SMS\CORE\BIN\SLOWNET.exe %0 1000

    SLOWNETTEMP Replace: %TEMP%\SLOWNET.exe %0
    With: %TEMP%\SLOWNET.exe %0 1000

    SLOWNETSERVER Replace: %0\. . \SNBOOT.exe
    With: %0\. . \SNBOOT.exe 1000

    Note: This example presumes a minimum connection speed of 1000 bps, but this value can be any value less than 40,000.

  3. The SMSls. bat file will be updated on logon points on the next scheduled logon point update cycle.

SMS Client Installation over RAS and Windows NT 3. 51

Logon discovery and installation methods that use logon scripts over a RAS connection are not supported for computers running Windows NT 3. 51. However, after the SMS client software is installed, these client computers can function over RAS.

WORKAROUND: Use SMSman.exe to install SMS client software on computers running Windows NT 3. 51 over RAS.

SMS Client Installation over RAS and Windows 2000

Logon discovery and installation methods over a RAS connection are not supported for computers that are running Windows 2000. However, after the SMS client software is installed over a LAN, these client computers can function over RAS.

WORKAROUND: To allow SMS clients to function from a RAS connection:

  1. Install the SMS client software over a local area network.

  2. From Control Panel, open Systems Management, click the General tab, and then select the Mobile Computer check box. (This can only be done with Administrative rights. )

  3. Click NO to any Travel Mode dialog box prompts that request revoking the client's assignment to its SMS site.

SQL Server

Enabling Windows NT Performance Monitor Counters for SQL Server

If the site server database is on a SQL 6. 5 SP4 Server and the version of SQLctr60. dll is less than 6. 50. 357, then the SMS Administrator console and Windows Management service will hang occasionally.

WORKAROUND: We recommend using this fixed version of SQLctr60. dll found on the SMS 2.0 SP2 compact disc:

CD\SQLSETUP\SQLHOTFIX\i386\SQLctr60. dll

To install the file, replace the existing SQLctr60. dll on the site's SQL server in the \MSSQL\BINN directory with the updated version, then reboot the computer.

Restrictions on the Use of Nordic Sort Order

Microsoft SQL Server is configured to use character set 850 Multilingual and either of the following configurations:

  • Sort order Scandinavian dictionary order, case-insensitive, uppercase preference (ID 58)

-or-

  • Sort order Scandinavian dictionary order, case-insensitive (ID 60)

By definition, these configurations do not differentiate between the characters "V" and "W. "

Because the unique identifier for Systems Management Server clients (that is, the SMSID) takes advantage of each of the alphanumeric characters, a conflict arises whenever a site has two clients that are differentiated only by the single character V or W (for example, SIT0100V and SIT0100W).

In this example, assuming that SIT0100V is written to the SMS site database first, when Inventory Data Loader attempts to add SIT0100W, the current record for SIT0100V is added as a history record of SIT0100W. Therefore, the existing inventory record appears to have disappeared from the SMS site database until an inventory delta MIF file for SIT0100V is produced.

WORKAROUND: Before you upgrade an SMS 1.2 site to SMS 2.0, find out about restrictions on the use of Nordic sort order in Knowledge Base article Q194146, SMS: Nordic SQL Server Sort Orders Cause Inventory Problems.

Remote Site Database Error After Upgrading Site Server's Operating System

If an SMS site database runs on a site system other than the site server, and the site server's operating system is upgraded from Windows NT 4.0 SP4 to Windows 2000, then SQL Server Database Monitor will report the following error when trying to connect to the site server: "Could not connect to registry key HKEY_LOCAL_MACHINE\Software\Microsoft\SMS. "

WORKAROUND: On the site server, run SMS Setup from the SP2 compact disc and choose the option to upgrade the site. Continue through Site Upgrade but make no changes. SQL Server Database Monitor will restart automatically as part of the upgrade, and it will now work.

Note: Performing a site reset will not correct the problem. For details about working around this issue, see the Knowledge Base article Q259781.

Interoperability with SMS 1.2

Distributing Software to Clients in SMS 1.2 Child Sites

If at least one SMS 1.2 site reports to an SMS 2.0 site in your site hierarchy, you can distribute software from SMS 2.0 sites to SMS 1.2 clients. However, no information about this process is available in the SMS 2.0 product documentation.

WORKAROUND: For information about distributing software from SMS 2.0 parent sites to clients at SMS 1.2 child sites, see SMS 1.2 and 2.0 Interoperability.

PGC Icons and Groups are not Removed from Clients During Upgrade

When you upgrade an SMS 1.2 site to SMS 2.0, Program Group Control (PGC) icons and groups are normally removed from clients, because PGC is not supported in SMS 2.0. However, if the logon server has already been upgraded to SMS 2.0 (the SMS_SHR directory has been removed), the PGC groups and icons are not removed from clients.

WORKAROUND: To remove the PGC groups and icons from clients, do any of the following:

  • Disable all the PGC groups and icons in the SMS 1.2 site before you upgrade it to SMS 2.0. This ensures that the PGC programs will not be in use when you upgrade the site.

  • Use SMS Installer or another scripting tool to create a script to remove the PGC groups and icons.

  • Install a new SMS 2.0 site and maintain the existing SMS 1.2 site until clients have migrated from PGC-based applications.

Security

Do Not Use the MS-DOS SUBST Command

SMS client functionality such as the Advertised Program Manger (APM) might be lost on servers (including site systems) due to SMSCliToknAcct& lockout on the server, if the following conditions are true:

  • An account lockout policy is enabled on the server hosting the share.

  • The MS-DOS subst command is used on an SMS client to map a drive to a folder within any share on the server. (However you can use the subst command to connect to the share point itself. )

SMS does not normally connect to remote drives while running software inventories. However, Windows NT 3. 51, Windows NT 4.0, and Windows 2000 cannot distinguish a drive mapped using the MS-DOS subst command from a local drive. As a result, the Software Inventory Client Agent attempts to connect to the mapped drive and fails. This failed connection attempt causes the SMSCliToknAcct& to be locked out. When the account is locked out, it cannot make connections required for it to carry out its functions, and the functionality is therefore lost on the server.

WORKAROUND: Do not use the MS-DOS subst command to map drives.

Note: The MS-DOS subst command is not needed in Windows 2000, which supports mapping drives to sub-share level resources.

SMS Client Connection Accounts can be Affected by Account Lockout

In Windows NT User Manager for Domains, if account lockout is enabled and any single SMS client uses an invalid password to try to access an account, that account will be locked out when the number of bad logon attempts is met. This has implications for SMS clients because of the various client connection accounts they use. For example, an SMS client that has been offline for a long time can cause a lockout because all its client connection accounts' passwords might have expired. When the SMS client attempts to return online with an old, invalid account password, it causes that client connection account to be locked out.

WORKAROUND: To avoid locking out clients, never change the password of an SMS client connection account. Instead, create new SMS client connection accounts with new passwords. After the new account information is propagated to all domain controllers, client access points, and clients, you can change or delete the old accounts.

For more information about account lockouts, see the "Account Lockouts" section in SMS 2.0 Security Essentials.

Using SMS with Windows 2000

Additional Information About Using SMS with Windows 2000

Detailed information about using SMS with Windows 2000 is available on the Systems Management Server Web site. This information is not available on the SMS 2.0 SP2 compact disc.

WORKAROUND: See SMS – Windows 2000 Compatibility.

Internationalization

No Separate Readme for Localized Version

Earlier releases of localized versions of SMS provided a separate readme file for issues specific to that localized version. Beginning with SMS 2.0 SP2, all issues specific to all localized versions of SMS are documented in the Internationalization sections of the Installation readme file and the Operations readme file. There is no longer a language-specific readme file.

Issues specific to International Client Packs (ICPs) are documented in the Readme_ICP. htm file, which is included when you install each ICP. All three readme files (Readme. htm, Readme_operations. htm, and Readme_ICP. htm) contain the most up-to-date information as the release date.

For issues specific to a localized version of SMS 2.0 SP2 (or later) read the Internationalization section of the readme files on the product compact disc or on the Systems Management Server Web site.

Microsoft Year 2000 Product Analyzer Japanese Language Version Readme Error

The readme file included with the Microsoft Year 2000 Product Analyzer describes two versions of the product analyzer: a command-line version, Y2kscn32.exe, and a wizard version, Y2kscan.exe. The wizard version, Y2kscan.exe, is not included in the Japanese language version.

WORKAROUND: None.

Microsoft Year 2000 Product Analyzer: Alpha Release

The database for the alpha release of the Microsoft Year 2000 Product Analyzer is available in English only. When a user runs the wizard version of this product (Y2kscan.exe), the interface is displayed in English.

WORKAROUND: None.

Names of Default Collections Use Language of Central Site

Any collection, package, or advertisement that is passed down a hierarchy assumes the name it was assigned at the site where it was created, and appears with that same name throughout the hierarchy. The default collections are a special case of this.

As each site is created, the default collections are created at that site, and the name of the collection reflects the site's language. When the site attaches to a parent site, the collection definitions for the default collections are overwritten with the definitions used at the parent site. If the child and parent use different languages, the collection names will be in the language of the parent site. This extends all the way up the hierarchy: default collections are assigned the name used at the central site. The implications of this depend on the codepages used by the affected sites:

  • If the two sites are using the same codepage, the SMS Administrator console at the child site displays the collection name correctly, but in the language of the central site.

  • If the two sites are using different codepages, the SMS Administrator console at the child site cannot display the collection name correctly. The names of the default collections will be corrupted.

WORKAROUND: If the two sites use the same codepage, administrators at the child site must learn to recognize the names of the default collections when they are in the language of the central site.

If the two sites use different codepages, at the central site, rename the default collections to use only ASCII characters. The collection names will then be displayed correctly at all sites. In addition, assign ASCII-only names to all collections, packages, and advertisements at any site that is or will be a parent to a site using a different codepage.

An alternative method is to maintain an SMS Administrator console at the child site on a computer that uses the language of the central site.

SMS Client Computers Running Windows 2000 MultiLanguage Version Report Corrupted Hardware Inventory Strings

SMS client computers running Windows 2000 with MultiLanguage pack applied, and that have set a double-byte character set (DBCS) language as the operating system language, report corrupted hardware inventory strings. DBCS languages include Japanese, Korean, Traditional Chinese, and Simplified Chinese.

The Hardware Inventory Client Agent returns corrupted strings for the following classes:

  • Win32_Directory

  • Win32_DiskPartition

  • Win32_Keyboard

  • SMS_LogicalDisk

  • Win32_NTLogEvent

  • SMS_Processor

Corrupted strings are displayed when using Resource Explorer to view information about these clients, and queries on these classes do not produce accurate results.

WORKAROUND: Do not change the user interface language to a double-byte language.

Network Monitor Filters and Double-Byte Character Sets

In Network Monitor capture filters, pattern matching strings cannot be saved within a filter as ASCII if the strings contain double-byte character sets.

WORKAROUND: Ensure that you are in Hex mode when you save filters that contain double-byte characters.

Set Location for New Reports Under Support Directory

Unless you set the location of the updated reports included with this Japanese language service pack, attempts to run the reports from SMS Administrator consoles on computers other than the site server will produce only an error message.

WORKAROUND: Set the location of each report, as described in the following procedure.

To import new reports:

  1. Copy the updated reports provided with this service pack to the \Sms\Cinfo directory on the site server, which is the default share location for Crystal Info, or to another shared folder of your choice. Only the reports in one of these shared folder locations can be imported into Reports in the SMS Administrator console.

  2. Start \SMS\Cinfo\Winnt\SetLocation.exe
    The SetLocation dialog box appears.

  3. Type the following configuration information in the appropriate boxes.

Box

Value to Enter

Site Code

The site code (which you supplied when you installed SMS).

Server

The name of the server where the SMS Provider is installed—either the site server or the server where the SMS site database resides.

Account

The user name used to install SMS.

Directory

The location of the shared directory where you placed the new reports. For example:

D:\Sms\Cinfo\Samples\SMS\NewReports
  1. Click Update Directory. A SetLocation message box appears, indicating the update was successful.

  2. Click OK, and then click Exit.

  3. In the SMS Administrator console, in the console tree, expand Tools.
    The available tools appear in the details pane. Notice this includes Network Monitor, SMS Service Manager, and Software Metering, as well as Reports.

  4. In the console tree, expand Reports. A set of folders appears in the console tree. These folders contain reports representative of the folder name.

  5. In the console tree, click Reports. The list of predefined folders appears in the details pane.

  6. On the Action menu, point to New, and then click Folder.
    The New Folder dialog box appears.

  7. In the Folder text box type the name of your folder, for example NewReports, and then click OK.

  8. On the Action menu, point to New, and then click Report Object.
    The New Report Object dialog box appears.

  9. In the Report File text box, type the complete filename of the report (for example \\computername\Cinfo\Samples\Sms\NewReports\P_01b. rpt), and then click OK.

  10. Repeat the procedure to add each of the other new reports.

The new reports appear in the details pane.

Microsoft will not provide any support services related to these reports or your use of the information contained herein. You assume all risk related to such use.

Network Monitor: Captured Addresses Using Double-Byte Character Sets

When you first open a Network Monitor address database after you upgrade to your site to the Japanese version of SMS 2.0 SP2, addresses using double-byte character strings might appear to be broken. This occurs when the system already had an ANSI default. adr file before the upgrade.

WORKAROUND: Perform the following steps:

  1. Upgrade your SMS site to SP2.

  2. Copy the Unicode version of the default. adr file from the \smssetup\netmon\directory on the SMS 2.0 SP2 compact disc to the SMSSETUP\Netmon\directory (where directory is i386 or Alpha).

NetWare Bindery: Clients Hang During Logon

When SMS clients running Windows 95 or Windows 98 log on to a NetWare bindery server, the SMS logon script opens and fails to close two command-prompt windows. The client appears to hang until these windows are closed.

Note: This issue applies only to the Japanese language version of SMS 2.0 SP2.

WORKAROUND: After the Snboot.exe and SMSnw1.exe have run, the user at the client must manually close the command-prompt windows they run in. The executable files require a maximum of five seconds to run. Users who attempt to close either window while the executable file is still running will receive a message warning them that the application is still running.

Software Metering

When a software metering server that uses a Japanese code page sends a license denial message to SMS clients that use a U. S. English code page, the license denial is unreadable and the application is denied.

WORKAROUND: None.

Updated Crystal Info Report Files

Report files have been updated for the Japanese version of SMS 2.0 service packs, but they are not automatically installed. Installing the updated report files will overwrite existing reports.

Note: These reports are unchanged from SP1. If you have already updated the reports using this same procedure from SP1, there is no need to update them again.

WORKAROUND: To replace existing reports with the updated versions, copy the *. rpt files from the \Support\Reports directory on the Japanese SMS 2.0 SP2 compact disc to the SMS\CInfo\Samples\SMS directory on the site server.

See also Restrictions on the Use of Nordic Sort Order

Crystal Info Version 6 (Reports)

Crystal Reports Services Installed as System Accounts

Crystal Reports services (Info Agent, InfoAPS, and Info Sentinel) might be installed as local system accounts. This prevents Crystal Reports from running.

WORKAROUND: Change the account used by Crystal Reports services to the SMS Service Account, which was specified when SMS was installed.

To make this change on a server running Windows NT 4.0, open Control Panel, click Services and double-click each Crystal Reports service.

On a server running Windows 2000, right-click My Computer on the desktop and click Manage. Navigate to Services (under Services and Applications, right-click each Crystal Reports service, select Properties, and make your changes on the Log On tab.

Crystal Reports Service Configuration for Computers Running SMS Administrator Console on Windows 2000 Remotely

When the SMS Administrator console is installed on a computer running Windows 2000, Crystal reports might not function correctly. Some common errors include:

  • Report Node, or the main report folder under the tools node, might not expand

  • Delayed response before failure messages are displayed

  • Miscellaneous error messages including, "failed to connect to APS", while using the SMS Administrator console locally

  • Miscellaneous error messages including, "failed to connect to APS", while using the SMS Administrator console from a Terminal Services session

Note: Using the SMS Administrator console from a Terminal Services session can produce a wide variety of other problems not related to Crystal Reports. Ensure your configuration matches one in this scenario before assuming this workaround is applicable to your situation.

WORKAROUND: To change the Info Sentinel service to log on as the local system account:

  1. Launch Services.

  2. Right-click the Info Sentinel service, and then click Properties.

  3. On the Log On tab, under Log on as, click Local System account, then click OK.

  4. Right-click Info Sentinel, and then click Restart.

Note: This configuration should only be implemented on a computer that is running Windows 2000 and is not an SMS site server. Crystal Reports services, including Info Agent, Info APS, and Info Sentinel that run on the SMS site server, should be configured as indicated in Crystal Reports Services might be Installed as System Accounts.

Printed and Online Documentation

Details for Obtaining Printed Copies of the SMS 2.0 Administrator's Guide

The online version of the SMS 2.0 Administrator's Guide is available on any computer that has the SMS Administrator console installed. This online version is more up-to-date than the printed version; however, you might want to have a printed copy.

WORKAROUND: If you obtained SMS through the Select or Open program, you can order copies of the SMS 2.0 Administrator's Guide by calling Microsoft World Wide Fulfillment at 1-800-248-0655. Use part number 271-00617. If you did not get SMS through the Select or Open programs, you can call Microsoft Supplemental and Replacement Parts, at 1-800-360-7561 and request part number 271-00617.

See also SMS Administrator's Guide: Errors in Printed Versions

Novell NetWare

Known Issues Regarding Novell NetWare Client v4. 7 for Windows NT/2000

When NetWare Client v4. 7 for Windows NT/2000 is installed on a computer running Windows NT 4.0 or Windows 2000 Professional, it is set as the first default file services redirector. In this state, the NetWare Client 4. 7 software can interfere with applications that make connections to servers running Windows. This can cause unpredictable behavior, such as connection errors and application General Protection Faults (GPF).

In particular, the following specific problems might be encountered with SMS operation on computers running Windows NT 4.0 and Windows 2000:

  • Issue 1. NetWare Client v4. 7 for Windows NT/2000 causes a GPF on SMS clients because the account that starts the SMS client processes does not have access to all drives mapped (logical disks) on that workstation. This problem might occur in clients running the Hardware Inventory Agent when the Win32_LogicalDisk is specified for Hardware Inventory through SMS_Def. mof. The alternative class, SMS_LogicalDisk, is enabled by default in SMS 2.0 SP2 to prevent this problem from occurring. This problem might also occur if other processes attempt to list all logical disks or when the account that lists the logical disks does not have access to the mapped drives.

  • Issue 2. NetWare Client v4. 7 for Windows NT/2000 opens handles but does not close them properly when SMS makes connections to NetWare servers configured as site systems.

  • Issue 3. NetWare Client v4. 7 for Windows NT/2000 might cause SMS server components to fail to authenticate to other computers running Windows NT 4.0 or Windows 2000. For example, communication might be disrupted between the site server and the site database servers if they are different computers and the SMS Provider is installed on the site database server. Or, Standard Sender might not be able to communicate to a parent or child site. This problem often results in an error message that states "Attempt to access Invalid Address. "

WORKAROUND: You can work around this Windows communication issue by changing the redirector order, however problems connecting to NetWare servers will remain.

Issue 1

In SMS_Def. mof, the entry for WIN32_Logical_Disk should be disabled, and the entry for SMS_LogicalDisk should be enabled. This selection is now the default for SMS_Def. mof in SMS 2.0 SP2 and later releases. This prevents Hardware Inventory from causing a GPF, but will not prevent other processes from causing the same GPF.

Issue 2 and 3

On Windows NT 4.0:

  1. In Control Panel, double-click the Networks icon.

  2. Click Services, and then click Network Access Order.

  3. If Novell NetWare is listed first, click that entry, then click Move Down.

  4. Ensure that Microsoft Windows NT is listed first in the provider order list.

On Windows 2000:

  1. On the desktop, right-click My Network Places, and then click Properties.

  2. Click the connection you want to modify.

  3. On the Advanced menu, click Advanced Settings, and then click the Provider Order tab.

  4. In Network Providers, click the NetWare Services network provider, and click the Down Arrow button.

  5. Ensure that Microsoft Windows Network is listed as the first provider in the list of Network Providers.

New Support for NetWare

SMS 2.0 SP2 adds the following NetWare support:

  • SMS 2.0 SP2 site servers can use the Novell intraNetWare Client for NT 4. 7 to communicate with site systems running NetWare 4. x or 5. x. See Known Issues Regarding Novell NetWare Client v4. 7 for Windows NT/2000 for issues with using the Novell 4. 7 redirector.

  • SMS site system roles of logon point, client access point, and distribution point can now be applied to both NetWare 4. x and NetWare 5. x servers. However, clients must be running SMS 2.0 SP2 or later to connect to site systems running NetWare 5. x.

  • SMS 2.0 SP2 clients can use TCP/IP or IPX to connect to site systems running NetWare 5. x.

  • All client operating systems that support connectivity to NDS site systems also support connectivity to NetWare 5. x NDS site systems, using IP or IPX.

WORKAROUND: None.

Supported NetWare Redirectors

Supported NetWare redirectors are not listed in the SMS 2.0 documentation, but they are listed in the following tables. For more information, search for "redirectors" in the the SMS topics of the Microsoft Knowledge Base.

SMS supports the following Novell and Microsoft redirectors for NetWare site systems:

SMS Site Servers Connecting To

Redirectors Supported

NDS site systems

Novell intraNetWare Client version 4.6 SP2

NetWare bindery emulation site systems

Microsoft Gateway Services for NetWare
Novell intraNetWare Client version 4.6 SP2

NetWare bindery site systems

Microsoft Gateway Services for NetWare
Novell intraNetWare Client version 4.6 SP2

SMS supports the following redirectors for client operating systems connecting to NetWareNDS site systems:

Client operating system

Redirectors Supported

Windows NT Server 4.0 SP4

Microsoft Gateway Services for NetWare
Novell intraNetWare Client version 4. 6 SP2

Windows NT Server 3.51 SP5

Novell intraNetWare Client version 4.11b

Windows NT Workstation 4.0 SP4

Microsoft Client Services for NetWare
Novell intraNetWare Client version 4. 6 SP2

Windows NT Workstation 3.51 SP5

Novell intraNetWare Client version 4.11b

Windows 95 and Windows 98

Novell intraNetWare Client version 3.2

NetWare bindery emulation site systems

Microsoft Gateway Services for NetWare
Novell intraNetWare Client version 4. 6 SP2

Windows 3.1

No support

Windows for Workgroups 3.11

No support

MS-DOS

No support

SMS supports the following redirectors for client operating systems connecting to NetWare bindery emulation site systems:

Client operating system

Redirectors Supported

Windows NT Server 4.0 SP4

Microsoft Gateway Services for NetWare
Novell intraNetWare Client version 4.6 SP2

Windows NT Server 3.51 SP5

Novell intraNetWare Client version 4.11b

Windows NT Workstation 4.0 SP4

Microsoft Client Services for NetWare
Novell intraNetWare Client version 4.6 SP2

Windows NT Workstation 3.51 SP5

Novell intraNetWare Client version 4. 11b

Windows 95 and Windows 98

Novell intraNetWare Client version 3.2

NetWare bindery emulation site systems

Microsoft Gateway Services for NetWare
Novell intraNetWare Client version 4.6 SP2

Windows 3.1

Novell VLMs version 2.71

Windows for Workgroups 3.11

Novell VLMs version 2.71

MS-DOS

Novell VLMs version 2.71

Note: 16-bit clients that log on to a bindery emulation server from DOS are not supported. Users must be logged on to Windows and be using NetWare VLM 2.71 to connect to bindery emulation systems.

SMS supports the following redirectors for client operating systems connecting to NetWare bindery site systems:

Client operating system

Redirectors Supported

Windows NT Server 4.0 SP4

Microsoft Gateway Services for NetWare
Novell intraNetWare Client version 4. 6 SP2

Windows NT Server 3.51 SP5

Novell intraNetWare Client version 4.11b

Windows NT Workstation 4.0 SP4

Microsoft Client Services for NetWare
Novell intraNetWare Client version 4. 6 SP2

Windows NT Workstation 3.51 SP5

Novell intraNetWare Client version 4. 11b

Windows 95 and Windows 98

Novell intraNetWare Client version 3.2

NetWare bindery emulation site systems

Microsoft Gateway Services for NetWare
Novell intraNetWare Client version 4. 6 SP2

Windows 3.1

Novell VLMs version 2.71

Windows for Workgroups 3.11

Novell VLMs version 2.71

MS_DOS

Novell VLMs version 2.71

Note: 16-bit clients that log on to a bindery server using Windows 3.x and NetWare VLM 2.71 to connect are supported. 16-bit clients using Windows 3.x and Lanman 2.2c that log on to Windows NT before or after launching Windows 3.x are also supported.

WORKAROUND: None.

Product Compliance

Product Analyzer Database Update No Longer Updated

Product Analyzer automatically attempts to download an updated database every 30 days, however the final Product Analyzer database was dated March 1, 2000. This database will not be updated.

WORKAROUND: If you do not want to download the database, follow these steps:

  1. Start the Product Analyzer, and click Custom Settings.

  2. Select the drives to be analyzed, and then click the database you want to use.

  3. Click Do Not Change Database.

  4. Follow the rest of the screens, and let the analyzer run.

Note: Product Analyzer custom settings that prevent the database from being automatically downloaded cannot be saved. You must perform the above steps every time you run Product Analyzer, if you want to prevent the database from being downloaded automatically.

Remote Tools

Remote Control Slow to Fully Initialize

In a complex domain environment with hundreds of trust relationships across many LAN/WAN-based domains, the Remote Tools Client Agent might take up to a full minute for each entry in the Permitted Viewers list before it can fully initialize. If the client computer is shut down when the Remote Tools Client Agent is initializing, a "Process unable to shut down" warning message might appear. This warning requires the user at the client computer to either terminate the process or wait to shut down.

WORKAROUND: To remove unnecessary entries in the Permitted Viewers list do the following:

  1. In the SMS Administrator console, navigate to Client Agents (Systems Management Server, Site Database, Site Hierarchy, site name, Site Settings, Client Agents).

  2. Right-click Remote Tools Client Agent, and then click Properties.

  3. On the Security tab, select a permitted viewer in the Permitted Viewers list that is not required for remote control administration. To remove the selected name, click Delete.

Longer Connection Times with Remote Control

A Remote Control connection takes longer (5-10 seconds) to use IANA port numbers when connecting to clients that have not been upgraded to SP2, because Remote Control significantly changed between SP1 and SP2. Connection times to SP2 clients are not affected.

The following is a list of IANA port numbers:


	sms-rcinfo   2701/tcp  SMS RCINFO
	sms-rcinfo   2701/udp  SMS RCINFO
	sms-xfer    2702/tcp  SMS XFER
	sms-xfer    2702/udp  SMS XFER
	sms-chat    2703/tcp  SMS CHAT
	sms-chat    2703/udp  SMS CHAT
	sms-remctrl   2704/tcp  SMS REMCTRL
	sms-remctrl   2704/udp  SMS REMCTRL

WORKAROUND: Upgrade clients to SMS SP2.

Screen Accelerators not yet Available for Computers Running Windows 2000

Regardless of the video driver in use on computers running Windows 2000, the screen acceleration will always report Low in the Remote Control Show Status option on SMS 2.0 clients.

WORKAROUND: None.

Remote Control Video Refresh Rate on Clients Running Windows NT 4.0

Some newer, high performance video drivers cannot take advantage of the video accelerator that is built into Remote Control. When Remote Control is used with one of these newer video drivers, the administrator's computer screen refreshes more slowly than with an older video driver.

WORKAROUND: If a speedy refresh rate is important, install one of the video drivers for which video acceleration is supported on SMS 2.0 (no service pack).

SMS Administrator Console

Determining the SMS Administrator Console Software Version

The software version of the SMS Administrator console is available by right-clicking on the Site Database node, and then clicking the About Systems Management Server menu option.

WORKAROUND: None

SMS 2.0 SP1 Administrator Console does not Allow Remote Control of Some Clients

If you are using the SMS 2.0 SP1 Administrator console and try to remotely control SMS 2.0 SP2 clients, you will receive a list of IANA port numbers. The last line of the list may state, "Remote Control Agent not found."

For more information, see the note above, Longer Connection Times with Remote Control.

WORKAROUND: Upgrade the SMS Administrator console to SMS 2.0 SP2.

Software Distribution

Forcing an Assigned Advertisement to Re-run

Because any client can receive multiple advertisements for the same program, SMS merges duplicate advertisements and combines their schedules. If a client receives several advertisements that all have assignment times, SMS attempts to run the program at the earliest assignment time. If the program is completed successfully, it is not scheduled to run again at any of the other assignment times. Creating additional advertisements does not force the program to re-run.

For example, if a program has run successfully on a client through an assignment for advertisement A, receiving advertisement B for that same program, but with a later assignment time, has no effect on the client.

WORKAROUND: To force assigned programs to re-run, do one of the following:

  • If all the clients in the target collection should re-run the program whether or not they have ever run it successfully, add an additional assignment to the existing advertisement.

  • If only those clients that have never run the program successfully should re-run it, create an additional advertisement for the program to the same collection with a new assignment time that is after the original assignment time.

Advertised Programs Client Agent Settings not used on Client

During client installation, the software distribution settings specified on site server are used, even if the Client cannot change agent settings option is cleared. After installation, if the option is cleared, users can change software distribution settings.

WORKAROUND: If you want clients to use the software distribution settings on the server, select the Client cannot change agent settings option on the site server.

Upgrading Clients from Windows 95 to Windows NT Workstation Version 4.0

If you use the Windows NT Workstation 4.0 package definition file to create and advertise the Automated upgrade from Windows 95 program that upgrades clients running Windows 95 to Windows NT Workstation 4.0, the status that is reported is based only on the ability to start the Winnt.exe program on the client. That is, if Windows NT Setup is successfully started, a successful MIF file is generated and reported to SMS, even if Windows NT Setup encounters errors while running.

Note: Windows NT 4.0 does not support a true upgrade of computers running Windows 95. The package definition supplied for Windows NT 4.0 performs a parallel installation of Windows NT 4.0 on Windows 95 clients, resulting in a dual-boot system. Any applications or settings on the Windows 95 client must be re-installed and configured in Windows NT 4.0.

WORKAROUND: Clients running Windows 95 that succeed in upgrading to Windows NT Workstation 4.0 will reject the advertisement because, by default, the advertisement is configured to apply only to clients running Windows 95. To determine which computers reported success in running the advertisement and later rejected it based on the supported platform, use advertisement status (navigate to Systems Management Server, Site Database, System Status, Advertisement Status, advertisement status).

Restriction on Windows NT Domain Names for Clients Running Windows 95 and Windows 98

SMS clients running Windows 95 and Windows 98 cannot correctly identify the user groups they belong to if the name of the Windows NT domain that the SMS site server resides in uses any characters other than the hash mark (#), the dash (-), and alphanumeric characters. In such cases, programs that are advertised to user groups to which the user at such a client belongs might not be run at that client.

WORKAROUND: If a site will include SMS clients that run Windows 95 or Windows 98, give the site server's domain a name that uses only alphanumeric characters, and optionally the hash mark (#) and the dash (-). Or, if you must use additional characters in the site server's domain name, use an alternate method to advertise programs to the members of a user group. For example, create a collection based on some other characteristic of the members of the user group, or to a collection listing the users who are to receive the advertisement, and then advertise to that collection.

SMS Client Connection Accounts Must Be Used To Access Client's Domain Controllers

In SMS 2.0 SP2, each SMS client must use an SMS client connection account to access its domain controllers. This requires explicit action only if the client and the site server are in different domains.

By default, SMS client connection accounts are created only in the domain where the SMS site server resides. If the SMS site server resides in a different domain than the SMS clients, SMS client connection accounts must be explicitly added to the clients' domain. For example, if your network uses a Master/Resource Domain model with the site server in a different domain from the clients, you would need to add SMS Client Connection accounts to the clients' domains.

This new requirement is due to a change in SMS functionality that addresses risks of account lockouts that could occur in earlier versions of SMS 2.0. These account lockouts, when they occurred, disrupted software distribution and other key functionality.

WORKAROUND: Complete either of the following actions to ensure that this new condition is met when clients are in domains other than the site server's domain:

  • Create an account to use as a client connection account in each client domain, and add these accounts (including domain name) to the list of SMS client connection accounts for the site.

  • Add the existing client connection accounts to the domains where the clients reside.

Note: For guidelines about maintaining and periodically updating the SMS client connection accounts, see SMS 2.0 Security Essentials.

Unattended Installation of Windows 98 from Windows 3. x

The Windows 98 Setup program displays a warning dialog box, and does not proceed until the dialog box is dismissed by the user. To perform an unattended installation of Windows 98, you must prevent this dialog box from appearing.

WORKAROUND: To prevent the dialog box from appearing, add the following lines to the Win16to98. inf file:


; Setup normally warns you to close other apps, including screen savers, before upgrading. ; 0 = warn as usual, 1 = do not warn for Windows apps, 2 = do not warn for DOS apps, 3 = do not warn for anything ; NOTE: Selecting 3 may cause loss data if unsaved documents are open. Choosing anything but 3 ; may stop and prompt for user input at the beginning of Windows 98 setup. If left commented, 0 will be used as ; the default. NoAppsWarn=3

Using Package Automation Scripts for Installation Programs that Require a Wrapper Program

Wrapper programs allow you to provide additional automation to software installation programs. SMS 2.0 includes several package definition files that use wrapper programs, for example, to install Windows NT 4.0, or to apply SP3 to Windows NT 4.0. These require that the package source directory to be set up in a specific way.

WORKAROUND: The following table describes how to set up package source directories and add the wrapper files to use these package definition files.

Package Definition

If Your Package Source Directory Is

Copy Source Files To

Copy Wrapper Directory From/To

Windows NT 4.0, SP 3

D:\Source\NT4sp3

D:\Source\NT4sp3\i386

..\SMS\Scripts\00000409\NT4\i386
D:\Source\NT4sp3

Windows NT 4.0, SP 3

D:\Source\NT4sp3

D:\Source\NT4sp3\Alpha

..\SMS\Scripts\00000409\NT4\Alpha
D:\Source\NT4sp3

Windows NT Server or Workstation 4.0

D:\Source\NT4pkg

D:\Source\NT4pkg\i386

..\SMS\Scripts\00000409\Nt4\i386
D:\Source\NT4pkg

Windows NT Server or Workstation 4.0

D:\Source\NT4pkg

D:\Source\NT4pkg\Alpha

..\SMS\Scripts\00000409\Nt4\Alpha
D:\Source\NT4pkg

Windows 98

D:\Source\Win98

D:\Source\Win98

..\SMS\Scripts\00000409\Win98\i386
D:\Source\Win98

Error Codes Used in Determining Software Distribution Status

SMS interprets an error code of zero as success when advertised programs are completed, whereas other applications, such as Internet Explorer 3. 02, report a non-zero error code upon successful completion. Advertisements that distribute these applications will report an incorrect advertisement status.

When determining status, SMS software distribution components first check for the existence of an install status Management Information Format (MIF) file generated by the program being run. If an install status MIF is not found, the return code of the program is used to determine installation status. SMS 2.0 and SMS 2.0 SP1 interpret a return code of zero as successful and non-zero codes as failure.

SMS 2.0 SP2 uses the same overall logic listed above, but also interprets the following non-zero exit codes as successful:

  • 3010

  • 3011

  • 1641

  • 1604

Note: These codes are commonly returned to indicate success but a system restart will be required before the process is complete.

WORKAROUND: In general, test software distributions in a lab environment before performing them on your production network. If successful installations report failed installation status due to return codes other than those listed above, contact the vendor of the program to obtain a list of possible return codes that indicate successful status. If necessary, create wrapper programs that intercept and filter those return codes. You can also replace the program's native Setup functions by re-packaging the application using the SMS Installer.

Windows NT 4.0 Service Pack 4 Distribution: Some Required Files not on SMS 2.0 Compact Disc

Do not use the version of Windows NT 4.0 SP4 that is included on the SMS 2.0 compact disc for software distribution.

The package definition file for Windows NT 4.0 SP4 that is included on the SMS 2.0 compact disc contains command lines that reference the Sp4i386.exe and Sp4alpha.exe files. However, these files are not provided on the SMS 2.0 compact disc.

Also, do not use the Y2ksetup.exe setup method for Windows NT 4.0 SP4 in SMS 2.0 software distributions.

WORKAROUND: To use the package definition file that is included with SMS 2.0 to distribute Windows NT 4.0, SP4, copy the Sp4i386.exe and the Sp4Alpha.exe files from the Windows NT 4.0 SP4 compact disc into your package source directory. No additional wrapper files are required.

Using Package Definition Files for Unattended Upgrades from Windows 95 to Windows 98

By default, during the upgrade from Windows 95 to Windows 98, Windows 98 Setup prompts the user to shut down any open programs and waits for a response from the user before continuing. The package definition file for the Windows 98 upgrade does not change this default behavior because of the risk of data loss should an application be shut down by the Setup program.

WORKAROUND: To enable an unattended upgrade from Windows 95 to Windows 98, edit the W95to98. inf file to remove the semicolon from the start of the following line:

;NoAppsWarn=3

note-icon Warning: This workaround causes Windows 98 Setup to close all programs on the target computer, which might result in data loss. If you use this option, tell your users to close all programs before the scheduled upgrade, even if the upgrade is scheduled at a time when the target computers are not usually in use.

Mandatory Programs will not Run on Clients Running Windows NT 3. 51 over a RAS Connection

Advertised programs that have the Assignments are not mandatory over slow links check box selected (on the Schedule tab of the Advertisement Properties dialog box) cannot be run on SMS clients running Windows NT 3. 51 over a RAS connection.

WORKAROUND: If you have clients running Windows NT 3. 51 that work over a RAS connection for any advertisements that are targeted to those clients, do the following:

  1. In the SMS Administrator console, navigate to Advertisements (Systems Management Server, Site Database, Advertisements).

  2. Right-click the advertisement you want to modify, and then click Properties.

  3. On the Schedule tab, clear the Assignments are not mandatory over slow links check box.

Advertisement Changes Based on Windows NT User Group Membership

Changes to Windows NT user group memberships take effect upon the user's next log on. Changes in advertisements that are based on existing user group memberships are detected at the usual polling interval (the user does not need to log off and then log back on). Advertisements that become valid for a user because of the user group membership changes, and that have occurred since that user last logged on, do not take effect until the user's next log on.

WORKAROUND: To ensure that users who are assigned to a new user group receive the programs that are advertised to that user group, instruct them to log off and then log back on to their computer.

Software Metering

Changing the Password for Software Metering Service Account

When the service domain account password is changed for the Software Metering Server service (SMS_LICENSE_SERVER), SMS Executive changes the password in the domain and on software metering servers. However, until the Software Metering Server service is stopped and restarted, it uses the old password to access lists of user groups on the domain controller. After the account password is changed on the domain controller, software metering servers using the old password are denied access to the domain controller. If lockout policies are enabled, the servers will also be locked out. When the Software Metering Server service is stopped for any reason after that, it cannot restart (due to a logon failure).

WORKAROUND: When changing credentials for the Software Metering Server service, specify a new account and password. Leave the existing account in place until all software metering servers have been configured with the updated credentials and have been stopped and restarted. This ensures that all software metering servers can reach the domain controller to get user group information while changes are being propagated. After all software metering servers have been configured, stopped, and restarted, the old account can safely be deleted.

Offline Mode for Clients that are Logged on Locally

When a user logs on to a client running Windows NT locally (rather than logging on to the network), the Software Metering Client Agent operates in offline mode. The client never attempts to connect to the software metering server during that session.

If the client has previously connected to the software metering server and has downloaded license enforcement data, restrictions on the use of specific software are enforced. However, if you have made changes to the properties for registered software while the client was offline, these cannot be enforced until the client connects to the software metering server and downloads the updated enforcement data.

If the client has not downloaded the license enforcement data, no restrictions are applied.

WORKAROUND: None.

Software Metering Account Password Fails Strong Password Test

Software metering uses a default password that does not meet Windows 2000 password complexity requirements. When a software metering server is installed on a Windows 2000 domain controller where password complexity is enforced, the creation of a domain account fails and the server installation is terminated.

WORKAROUND: Specify a domain account and a password of seven characters (no longer) that includes upper and lower case letters, at least one number, and at least one punctuation character. Do not use the default account password when installing software metering servers.

See the Windows 2000 Help for more information about password requirements.

Running Restricted Products on Clients that have Group Permission

If you restrict a metered product to a group, users that do not have Domain Admins group membership are not able to run the product. Software metering is unable to determine which groups the user belongs to, and therefore unable to enforce security by group permissions. However, user and computer permissions continue to work correctly.

WORKAROUND: Ensure that the Software Metering Service account belongs to the Domain Admins group in the accounts domain.

Access Denial Events Are Not Generated

When you define a licensed product, selecting the option to generate Alert Events, Access Denial has no effect in Software Metering. Whether this option is selected or not, status viewer messages are not generated when a client is denied access to a program, nor will Windows NT events be generated, because this feature has not been implemented.

WORKAROUND: You can view the list of denied applications in the Software Metering Console. Choose Software Metering Summary, and on the Licensed tab, select Denials summary type.

Software Metering Tool can use Excessive Amounts of Memory

The Software Metering Tool uses large amounts of memory when it displays the Software Metering page and especially, the Unlicensed Summary page. The amount of memory it uses is directly proportional to the unsummarized records in the database.

WORKAROUND: Summarize all software metering data.

Registering Products with Language ID = Neutral

The default language version for registered software is U. S. English. In order for the Software Metering Client Agent to enforce licenses correctly, the language version used in registering the software must match the language version of the software that is actually run on the client. However, if the software is registered using the Neutral language version, the licenses can be enforced regardless of which language version of the software is used at the client.

WORKAROUND: When you register the product, set the language to Neutral. If you have already registered the product you must remove the registration, then register it again. The language setting cannot be changed after a product is registered.

To determine a program's language ID, view the properties of the executable file by right-clicking the file and then clicking Properties.

Performance of Clients Running Windows 95 and Windows 98 on Busy Networks

On extremely busy or poorly performing networks, software metering clients running Windows 95 or Windows 98 might repeatedly hang for 20 to 30 seconds at a time.

WORKAROUND: Edit the registry of the computer experiencing the problem to create a new registry value, as follows:

  1. Click Start, click Run, and enter the command Regedit. This opens the registry for editing.

  2. In the Registry Editor, open My Computer\HK_Local_Machine\Software\Microsoft\sms\client\client components\license metering\properties.

  3. In the right pane, right-click and create a new DWORD value named GoOfflineAfterFailure, and assign it a value of 1.

The Software Metering Client Agent will now run in offline mode after it experiences a network error.

SMS Administrator's Guide: Errors in Printed Versions

Information About SMS Accounts: Documentation Updates

The following updates were made to the online version of the SMS 2.0 Administrator's Guide for the SMS 2.0 SP2 release:

  • Five new tables (Tables 4. 1 through 4. 5) were added to the "Using Windows NT File and Directory Security" topic. These tables provide more detailed information about the default permissions set on SMS shares and directories on client access points (CAPs), logon points,distribution points, software metering servers, and SMS site servers. However, Readme. htm has updated data for SP2.

  • A new table (Table 4. 6) has been added to the "Understanding SMS System Accounts" topic to summarize the accounts used by SMS. This table provides the following information about each account:

    • The functions performed by the account.

    • Whether the account is created automatically.

    • Whether the account is required.

  • The existing information in the "Understanding SMS System Accounts" topic has been updated and expanded. Each account is now described more fully in individual sections.

The SMS accounts information in the SMS 2.0 SP1 online Help has also been updated. The updates to online Help include a new topic ("About Managing SMS Accounts and Passwords") that provides guidelines to enhance security and effectively manage SMS accounts.

Note: Other more minor changes were made to the online SMS 2.0 Administrator's Guide. Where it differs from the printed book, the online version created for SP2 is correct.

WORKAROUND: For the most up-to-date information about SMS accounts, see SMS 2.0 Security Essentials.

SMS Client Remote Installation Account: Documentation Error

The note in the "About the SMS Client Remote Installation Account" topic in the online Help (SMS20hlp. chm) is incorrect. This note states that the SMS Client Remote Installation account is required to install the SMS client software on Windows NT-based computers in NetWare environments, because NetWare resources will not use the SMS Service account. This is not correct.

To install the SMS client software on Windows NT-based computers, whose logged on users do not have local administrative rights, you can use either the SMS Service account or an SMS Client Remote Installation account. Either account can be used in Windows NT and NetWare environments. At least one of these accounts must have local administrative rights on the computers where the SMS client software will be installed, or the installation will not succeed. Clients running Windows NT in NetWare environments can use the SMS Service account for remote client installation if they are also members of the Windows NT domain in which the SMS Service account exists. Otherwise, a local administrative account must be specified.

If you do not specify the SMS Client Remote Installation account for SMS client software installation (or if this account does not have local administrative rights on the client), the SMS Service account will be attempted. To enhance security, specify one or more SMS Client Remote Installation accounts that should be used for SMS client software installation.

During site setup, the SMS Service account is made a member of the Domain Admins group for the site server's domain and, as such, it has administrative rights on all Windows NT systems in that domain. An SMS Client Remote Installation account does not need to be a member of the domain Administrators group, but it does need local administrative rights on the computers where the SMS client software will be installed. A macro can be used to specify the local account to use on the SMS client computer.

To specify the local account used on the SMS client computer with a macro:

  1. From the Accounts tab in the SMS Administrator console, open Site Properties.

  2. Enter %Machinename%\AccountName (%Machinename%\ should be typed exactly, AccountName is the name of the account on the SMS client. ) This macro will substitute the client computer name for the %Machinename% variable.

Updated Flowcharts in Online Help

The flowcharts in the SMS 2.0 SP2 online Help differ from those that appear in the printed version of the SMS 2.0 Administrator's Guide. Where there are differences, the flowcharts in the online Help are more detailed and accurate.

WORKAROUND: When referring to flowcharts, use the online Help versions.

SMS Express Setup Information: Documentation Update

The online SMS 2.0 Administrator's Guide (SMSadmin. chm) contains more accurate information about SMS Express Setup than the printed documentation.

WORKAROUND: For the most up-to-date information about SMS Express Setup, see the SMS 2.0 SP2 release of the online SMS 2.0 Administrator's Guide, Chapter 6, Chapter 9, and Chapter 22.

Online SMS 2.0 Administrator's Guide Contains Updates to Chapter 17

The online SMS 2.0 Administrator's Guide (SMSadmin. chm) contains more accurate information about product compliance than the printed documentation.

WORKAROUND: When you need information about product compliance, see the online SMS 2.0 Administrator's Guide, Chapter 17.

Error in Online Help: Dependent Programs Not Supported on 16-Bit Clients

As indicated on page 389 of the SMS 2.0 Administrator's Guide, 16-bit clients cannot run a dependent program before the program that is advertised.

WORKAROUND: Reference page 389, "Software Distribution on 16-Bit Clients," in the printed SMS 2.0 Administrator's Guide.

Crystal Info Reports Provided with SMS: Documentation Update

The reports provided with SMS 2.0 SP2 differ from the reports listed in Chapter 19, "Creating Administrative Reports" in the SMS 2.0 Administrator's Guide.

WORKAROUND: None.

Courier Sender is Supplementary Only: Printed Documentation Error

Chapter 1, "Introducing Systems Management Server Version 2.0" in the SMS 2.0 Administrator's Guide states that the Courier Sender provides communication between sites that have unreliable or non-existent network connections. It is not true that you can use Courier Sender in place of other network connections.

WORKAROUND: Use one of the other sender types for most intersite communications. If you have a slow or unreliable link between a site and its parent, you can use Courier Sender to send packages between the sites. This error has been corrected in the online version of the SMS 2.0 Administrator's Guide (SMSadmin. chm).

Server Installation: Documentation Update for Running an Unattended Setup

Chapter 6 of the online version of the SMS 2.0 Administrator's Guide (SMSadmin. chm) has been updated to include information about creating an initialization file to perform an unattended installation of SMS 2.0. The new topic, "Running an Unattended Setup," includes detailed descriptions of each of the setup keys in an SMS Setup initialization file and their corresponding values. Each key description also specifies the type of installation that requires that key.

The printed version of the SMS 2.0 Administrator's Guide does not include this information.

WORKAROUND: For detailed information about running an unattended setup of SMS 2.0, see the online version of the SMS 2.0 Administrator's Guide.

Site Reset Cannot Be Used to Restore Access Permissions for the SMS Server Connection Account: Security Documentation Error

In the online Help, the last bulleted list item in the "About Managing SMS Accounts and Passwords" topic is incorrect. The text states, "If you inadvertently delete the SMS Server Connection account or change its password, you can restore this account by resetting your site." This is not correct. Site reset will only update the password on an existing SMS Server Connection Account. However, if you delete the SMS Server Connection account or restore a site backup, or if you change the account name you cannot restore it by resetting your site.

WORKAROUND: Use the ACL Reset tool (Aclreset.exe) to restore access permissions for the server connection account to the SMS directory tree and registry tree. You can find this tool on the Maintenance & Recovery site.

Hardware Requirements: Documentation Update

The following hardware requirements for installing SMS 2.0 on a site server are updated from those listed in Appendix A, "System Requirements and Supported Platforms," in the SMS 2.0 Administrator's Guide:

  • Intel, Alpha, or a compatible system that is included in the Windows NT 4.0 hardware compatibility list

  • Pentium 133 (or compatible) or faster microprocessor (Pentium 200 recommended)

  • 64 MB to 96 MB of RAM, 16 MB of which are dedicated to SQL Server (128 MB recommended)

  • 1 GB of available hard disk space (6 GB recommended)

  • Video resolution of at least 800 x 600 pixels, 256 colors

  • CD-ROM drive

Software Requirements for Site Servers and Other Computers Running SQL Server: Documentation Update

The information in this section updates the information in Chapter 6, "Installing SMS 2.0 Sites," and Appendix A, "System Requirements and Supported Platforms," in the SMS 2.0 Administrator's Guide.

The following software is required to install and run SMS 2.0 SP2:

  • Windows NT Server 4.0 SP4 or Windows NT Server, Enterprise Edition 4.0 SP4. For your convenience, SP4 for Windows NT 4.0 is provided on the SMS 2.0 compact disc. You can install this service pack from either of the following locations (note that you must install the service pack before you install SMS 2.0):

    • The Install NT4.0 SP4 option on the initial SMS 2.0 Setup screen

    • The \NTQFE\Nt4sp4\I386 or \NTQFE\Nt4sp4\Alpha directories on the SMS 2.0 compact disc (run the Nt4sp4.exe file)

Note: Windows NT Server 4.0 SP5 (or later) can be used with SMS 2.0, but specific installation steps must be followed as described under Prerequisites in the Installation Readme (readme. htm).

  • Microsoft Internet Explorer 4.01 SP1 (or later) is required to run SMS Help and some Network Monitor components. Install Internet Explorer 4.01 SP1 from the initial SMS 2.0 Setup page by selecting the Install NT4.0 SP4 option. (Note that you must install the service pack before you install SMS 2.0. )

  • Microsoft SQL Server 6. 5 SP4 (or later) is required on the computer that will maintain the SMS site database.

    SMS 2.0 Setup can install SQL Server 6. 5 or 7. 0 from a SQL Server installation compact disc that you supply. If SMS 2.0 Setup installs SQL Server 6. 5, it automatically applies SP4.

    If you use an existing installation of SQL Server 6. 5, you must install SQL Server SP4 before you install SMS 2.0. For your convenience, SP4 for SQL Server 6. 5 is provided on the SMS 2.0 SP2 compact disc. You can install this service pack from the Sqlsetup\Sp4\<platform> directory.

Updates to Tables in Appendix A of the SMS 2.0 Administrator's Guide

The following updates to Appendix A of the SMS 2.0 Administrator's Guide do not appear in either the printed or the online version of that book.

  • The update of Table A3, "Client Feature List for Clients Using Windows Networking Software," adds information pertaining to clients running Windows 2000.

  • Table A4, "Supported Windows 2000 Platforms for Site System Roles," is similar to Table A1 "Supported Platforms for Site System Roles," in the 2.0 Administrator's Guide, but it provides information pertaining to servers running Windows 2000.

Table A.3 Client Feature List for Clients Using Windows Networking Software

Client

Client Installation

Hardware Inventory

Software Distribution

Remote Tools

Software Inventory

Network Monitor

Software Metering

Windows 3.1

 

Yes

 

Yes

 

Yes

 

Yes

 

Yes

 

No

 

No

Windows for Workgroups 3.11

 

Yes

 

Yes

 

Yes

 

Yes

 

Yes

 

No

 

No

Windows 95

 

Yes

 

Yes

 

Yes

 

Yes

 

Yes

 

No

 

Yes

Windows 98

 

Yes

 

Yes

 

Yes

 

Yes

 

Yes

 

No

 

Yes

Windows NT 3.51, Service Pack 5a

 

Yes

 

Yes

 

Yes

 

Yes

 

Yes

 

No

 

Yes

Windows NT 4.0

 

Yes

 

Yes

 

Yes

 

Yes

 

Yes

 

Yes

 

Yes

Windows NT 4.0, Enterprise Edition

 

Yes

 

Yes

 

Yes

 

Yes

 

Yes

 

Yes

 

Yes

Windows NT 4.0 Terminal Server Edition

 

Yes

 

Yes

 

Yes

 

No

 

No

 

Yes

 

No

Windows 2000 Professional

 

Yes

 

Yes

 

Yes

 

Yes

Yes 1

 

Yes

 

Yes

Windows 2000 Server

 

Yes

 

Yes

 

Yes

 

Yes

Yes 2

 

Yes

 

Yes

Windows 2000 Advanced Server

 

Yes

 

Yes

 

Yes

 

Yes

Yes 3

 

Yes

 

Yes

Windows 2000-based servers supporting Terminal Services

Yes 4

 

Yes

 

Yes

Yes 5

 

No

 

Yes

 

No

Windows 2000-based servers supporting Windows Clustering

 

No

 

No

 

No

 

No

 

No

 

Yes

 

No

Table A.4 Supported Windows 2000 Platforms for Site System Roles*

Site System Role

Windows 2000 Server

Windows 2000 Server Supporting Terminal Services

Windows 2000 Advanced Server

Windows 2000 Advanced Server Supporting Terminal Services

Primary site server

 

Yes

 

Yes

 

Yes

 

Yes

Secondary site server

 

Yes

 

Yes

 

Yes

 

Yes

Site or software metering database server (SQL Server 6.5, Service Pack 5 or later)

 

Yes

 

Yes

 

Yes

 

Yes

Site or software metering database server (SQL Server 6.5, Enterprise Edition, Service Pack 5 or later)

 

No

 

No

 

Yes

 

Yes

Site or software metering database server(SQL Server 7.0 Standard Edition)

 

Yes

 

Yes

 

Yes

 

Yes

Site or software metering database server(SQL Server 7.0 Enterprise Edition)

 

No

 

No

 

Yes

 

Yes

Site or software metering database server (SQL Server 2000)

 

Yes

 

Yes

 

Yes

 

Yes

Logon point

 

Yes

 

Yes

 

Yes

 

Yes

Client access point (CAP)

 

Yes

 

Yes

 

Yes

 

Yes

Distribution point

 

Yes

 

Yes

 

Yes

 

Yes

Software metering server

 

Yes

 

Yes

 

Yes

 

Yes

Component servers

 

Yes

 

Yes

 

Yes

 

Yes

* Note that Windows 2000 Server supporting Windows Clustering is not supported for site system roles.

Related Links

1Accelerated video for remote tools isn't supported on clients running Windows 2000.
2Accelerated video for remote tools isn't supported on clients running Windows 2000.
3Accelerated video for remote tools isn't supported on clients running Windows 2000.
4SMS logon installation cannot be used to install any client on servers supporting Terminal Services. You can use SMSman.exe or the Windows NT Remote Client Installation method to install SMS clients.
5Software distribution is limited to assigned advertisements or packages that don't require user input on servers supporting Terminal Services.
Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft