LabMice.net - The Windows 2000\XP\.NET Resource Index
Home | About Us | Search

Last Updated December 16, 2003

SMS Server
  Where to Start
  Administration
  Clients
  How to Articles
  Installation
  Inventory
  Novell Integration
  Remote Control
  SMS Installer
  Software Deploy
  Software Metering
  Troubleshooting

 

BackOffice
  AppCenter
  BizTalk Server
  Exchange
  Host Integration
  IIS
  ISA Server
  MOM
  Proxy Server
  Site Server
  SMS Server
  SNA Server
  SQL Server
Book Reviews
Career Tools
Networking
Resource Centers
Scripting
Security
User Groups
Utilities
Cybercheese

 

 

 

 

 

 

 

SMS Clients

 

SMS 2.0 Client Features
Learn about SMS 2.0's improved client features, including resource discovery and client agents. Source: Windows & .NET Magazine (May 1999)

Service Pack Upgrade Considerations for Clients
Microsoft Knowledge Base Article: 237543 - When a Systems Management Server (SMS) 2.0 site is upgraded to a service pack, all clients reporting to the site are automatically upgraded. In a site with a significant number of clients, you may need to consider your network bandwidth when you are creating your upgrade strategy.

Systems Management Server 2.0 Service Pack 1 ICP1 Client Hotfix Bundle
Microsoft Knowledge Base Article: 247306 - Microsoft has released various hotfixes to correct specific issues for Systems Management Server (SMS) 2.0 clients. Microsoft has packaged these hotfixes into a single client hotfix bundle to simplify applying these hotfixes on an SMS 2.0

 

"How to" Articles
Avoiding Client Lockouts When Using Client Connection Accounts
Microsoft Knowledge Base Article: 237759 - This article describes orphan clients and steps for recovering from this problem. This article also describes a procedure to plan for account rotation in domains with secure account policies.

Configuring and Suppressing SMS 2.0 Client Agent Messages
Microsoft Knowledge Base Article: 212905 - In Systems Management Server 2.0, you can configure Client Agent Messages. Some messages can be suppressed, others can be customized.

Excluding Computers from Windows NT Remote Client Installation
Microsoft Knowledge Base Article: 207729 - Following is an explanation of how an administrator specifies computers to be excluded from discovery and installation by the Windows NT Remote Client Installation service. In addition, you may want to exclude specific workstations and/or servers that reside within site boundaries from becoming Systems Management Server 2.0 clients.

Forcing Changes in Remote Tools Settings to 32-bit Clients
Microsoft Knowledge Base Article: 198691 - When settings are changed at the site for the Systems Management Server Remote Control Agent, some of these changes are not automatically implemented at existing clients in the site. In particular, the protocol, the compression type, and the video acceleration are not changed on existing clients. Newly installed clients will get current settings for the Remote Control Agent.

How to Avoid Client Contention Between SMS 1.2 and SMS 2.0
Microsoft Knowledge Base Article: 199987 - When a Systems Management Server 2.0 client is authenticated in a Systems Management Server 1.2 site, the 1.2 site may attempt to replace the 2.0 client software with 1.2 client software. To prevent this from occurring, replace the Smsls.bat

How to Configure the Client Verify Cycle for Systems Management Server 2.0 Clients
Microsoft Knowledge Base Article: 246040 - Every 30 days by default, Systems Management Server 2.0 clients go through a client verify cycle to ensure that the client components are correctly installed and working properly.

How to Pre-stage SMS Clients to Avoid Network Bandwidth Contention During Installation
Microsoft Knowledge Base Article: 202338 - This article discusses specific scenarios where client staging and pre-install are useful and presents planning and pre-implementation steps as well as manual steps for client pre-installation.

How to Recover When a Client Connection Account Is Locked Out
Microsoft Knowledge Base Article: 236052 - This article describes how to recover Systems Management Server (SMS) 2.0 clients when the SMSClient_SiteCode account password is changed and the clients are no longer able to connect to a Client Access Point (CAP) server.

How to Remove a Systems Management Server 2.0 Client
Microsoft Knowledge Base Article: 199078 - There are three methods for initiating the removal of the Systems Management Server client software from a client. (updated 11/29/2000) 

How To Run Smsman.exe and Specify an NDS Logon Point
Microsoft Knowledge Base Article: 201179 - Describes how to install the Systems Management Server 2.0 client.

SMS 1.2 Clients Visiting SMS 2.0 Sites
Microsoft Knowledge Base Article: 199237 - This article describes the procedure on how to prevent Systems Management Server 1.2 clients from being upgraded by Systems Management 2.0 sites that they visit.

Using the SMS Windows NT Client Software Installation Account
Microsoft Knowledge Base Article: 235811 - The Advertised Programs Manager uses the Systems Management Server Windows NT Client Software Installation account to support advertised programs on Windows NT clients that require a special security context.

Technical Details

Client Access Point and Distribution Point Selection
Microsoft Knowledge Base Article: 205406 - Systems Management Server (SMS) clients use existing connections from the Client Access Points (CAPs) and Distribution Points (DPs) designated in their site by default. If no existing connection exists, clients randomly select from the CAP/DP list for their site. Sites are defined by local or fast network connectivity, ensuring load balancing across all CAPs and DPs in the site.

CRC Checking and Installation of Client-Side Hotfixes
Microsoft Knowledge Base Article: 246331 - Systems Management Server (SMS) 2.0 verifies that Windows NT clients are running the correct versions of the client components. The SMS Client service does this by comparing the cyclical redundancy check (CRC) values of the client component on the client with the CRC values of the same programs in the site server's Sms_root_folder\Bin\Platform folder.

Limited Support for Dual Boot Clients
Microsoft Knowledge Base Article: 199248 - Dual boot support in System Management Server 2.0 is limited to computer that have a System Management Server role of client. This is supported only on 32-bit Windows clients, that is, Windows 95, Windows 98, and Windows NT, or multiple instances of Windows NT. The default location for the MS\SMS tree will be under %Windir%

Network Impact from Client Configuration Installation Manager (CCIM) During a 23-Hour Cycle
Microsoft Knowledge Base Article: 231232 - In large network environments where computers are shut off each day, network performance issues may be observed when the computers are turned on each morning, even when logon scripts are not used. This behavior can be caused by the Client Configuration Installation Manager (CCIM) on several different computers going though a maintenance cycle at the same time

Slownet Determines Network Speed at Logon
Microsoft Knowledge Base Article: 224388 - Slownet.exe is called at logon in SMSLS to determine the network connection speed between the client and the logon point. Depending on the client platform, the file to which Slownet maps can be any of the following files:

Smsman Requires Logon Installation or Discovery to Be Enabled
Microsoft Knowledge Base Article: 235535 - In Systems Management Server (SMS) 2.0, clients cannot be manually set up until either Windows Networking Logon Discovery (Logon Discovery) or Windows Networking Logon Client Installation (Logon Installation) is enabled.

What Is CHECK20?
Microsoft Knowledge Base Article: 199653 - Check20.exe is an executable file that is included in Systems Management Server 1.2 Service Pack 4 to allow interoperability between version 1.2 and 2.0 clients in a multi-site environment. Check20.exe is referenced in the Runsms.bat and Smsls.bat files. One reason for this change to the Systems Management Server logon scripts was to prevent the 1.2 client code from overwriting client files installed by a 2.0 site

Troubleshooting: Known Bugs and Issues 
Ping Test on Windows NT Clients May Require Credentials
Microsoft Knowledge Base Article: 192490 - A credentials dialog box appears on a Remote Administrator's User Interface, asking for credentials to initiate a ping to a client. Most Administrators do not expect to enter credentials before performing a ping test to a client.

Smsls Hangs Client with Unsupported Network Redirector
Microsoft Knowledge Base Article: 235043 - If a client is running an unsupported network redirector, such as a third-party TCP/IP stack, running Smsls.bat may cause the computer to stop responding (hang). Also, running the Systems Management Installation Wizard (Smsman.exe) with an unsupported redirector may cause the installation to hang without any error message.

Win95 Client Software Causes Unexpected Login Failure: Status 8890
Microsoft Knowledge Base Article: 235770 - Some Microsoft Windows client computers (Windows 95 or Windows 98) running Novell's IntranetWare client version 2.5 or 3.1 may experience an error 8890 (object already authenticated) when installed with Microsoft Systems Management Server client software.

Windows 9x NetWare Clients Not Running SMS Logon Script
Microsoft Knowledge Base Article: 201640 - When a Windows 9x NetWare client that is using the Microsoft Client for NetWare logs on to a Novell NetWare server, it might not correctly run the System Management Server 2.0 login script (Smsls.scr). As a result, the client computer may not verify the System Management Server client software and report inventory

Entire contents
© 1999-2003 LabMice.net and TechTarget
All rights reserved

This site and its contents are Copyright 1999-2003 by LabMice.net. Microsoft, NT, BackOffice, MCSE, and Windows are registered trademarks of Microsoft Corporation. Microsoft Corporation in no way endorses or is affiliated with LabMice.net. The products referenced in this site are provided by parties other than LabMice.net. LabMice.net makes no representations regarding either the products or any information about the products. Any questions, complaints, or claims regarding the products must be directed to the appropriate manufacturer or vendor.