SMS: Client Incorrectly Reported as Not Installed in the Administrator Console

ID: Q241279


The information in this article applies to:
  • Microsoft Systems Management Server version 2.0


SYMPTOMS

Systems Management Server clients may appear as 'not installed' in the Administrator console, which may contradict their SMS client-based components actual status. This status is displayed by clicking the Components tab in the Systems Management Server tool in Control Panel.

Clients who were formally listed as 'installed' in the Administrator console may revert to 'not installed' and their status may fluctuate.


CAUSE

This behavior occurs because the client computer has been turned off for more than 24 hours before starting up and discovery may occur before the Client Cconfiguration Installation Manager has updated its heartbeat time.

Discovery determines whether the client is installed by checking if CCIM has updated its heartbeat time within the last 24 hours.

If the client computer has been turned off for more than 24 hours, when it start up, Logon Discovery or CCIM itself may do discovery before the CCIM has updated its heartbeat time. This causes discovery to report the client as not installed (client = 0) in the Data Discovery Record (DDR). The DDR is then transfered to the site server and added to the database.

In general, if the computer remains turned on, this incorrect value is corrected the next time either logon discovery takes place or the next time CCIM writes a heartbeat DDR to the Client Access point.


RESOLUTION

A supported fix that corrects this problem is now available from Microsoft, but it has not been fully regression tested and should be applied only to systems experiencing this specific problem. If you are not severely affected by this specific problem, Microsoft recommends that you wait for the next Systems Management Server service pack that contains this fix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information on support costs, please go to the following address on the World Wide Web:

http://www.microsoft.com/support/supportnet/overview/overview.asp
The English version of this fix should have the following file attributes or later:

   Date      Time       Version      Size    File name   Platform
   -------------------------------------------------------------
   10/14/99  04:58p  2.0.1380.1055  232,288  Abnwcli.dll  i386
   10/01/99  10:22a  2.0.1380.1051  256,864  BindCliN.dll i386
   09/10/99  03:49p  2.0.1380.1023  158,544  Ccim32.dll   i386
   10/20/99  02:33p  2.0.91.3     3,214,006  CliCore.exe  i386
   10/01/99  10:22a  2.0.1380.1051  157,536  Falclin.dll  i386
   10/20/99  11:07a  2.0.1380.1056  337,248  Mslmclin.dll i386
   10/01/99  10:22a  2.0.1380.1051  266,592  NdsClin.dll  i386
   10/20/99  02:03p  2.0.1380.1058   73,056  Smsdiscv.dll i386
   10/20/99  02:06p                      67  Compver.ini  all
   10/14/99  04:59p  2.0.1380.1055  409,360  Abnwcli.dll  Alpha
   09/10/99  03:49p  2.0.1380.1023  253,200  Ccim32.dll   Alpha
   10/20/99  02:33p  2.0.91.3     4,236,160  CliCore.exe  Alpha
   10/01/99  10:22a  2.0.1380.1051  285,968  Falclin.dll  Alpha
   10/20/99  11:08a  2.0.1380.1056  576,784  Mslmclin.dll Alpha
   10/20/99  02:03p  2.0.1380.1058  120,080  Smsdiscv.dll Alpha 
NOTE: Due to file dependencies, the most recent hotfix or feature that contains the above files may also contain additional files.



STATUS

Microsoft has confirmed this to be a problem in Systems Management Server version 2.0.


MORE INFORMATION

To install the hotfix, perform one of the following on the Systems Management Server Site server: either the Using The Hotfix Installer steps or the Manual Installation steps at the Systems Management Server Site Server.

Using The Hotfix Installer

i386 platforms only

  1. Copy the hotfix folder structure to a share on your network. Q241279.exe is a Microsoft Windows Installer file that updates specific files on your site server.


  2. Log on to your site server using an account with administrative privileges.


  3. On the site server, close the SMS Administrator console.


  4. Run the Q241279.exe file and follow the directions in the wizard. The file can be run in quiet mode using the /s switch.


Manual installation

  1. Stop the SMS_EXECUTIVE and the SMS_SITE_COMPONENT_MANAGER services.


  2. Replace the Clicore.exe file in the <Sms_root>\Inboxes\Clicomp.src\Base\<Platform> folder with the version obtained from the hotfix.


  3. Replace the Compver.ini file in the <Sms_root>\Inboxes\Clicomp.src\Base folder with the version obtained from the hotfix.


  4. Replace the Abnwcli.dll file in the <Sms_root>\Bin\<Platform> folder with the version obtained from the hotfix.


  5. Replace the BindClin.dll file in the <Sms_root>\Bin\<Platform> folder with the version obtained from the hotfix.


  6. Replace the NdsClin.dll file in the <SMS_root>\Bin\<Platform> folder with the version obtained from the hotfix.


  7. Replace the Falclin.dll file in the <SMS_root>\Bin\<Platform> folder with the version obtained from the hotfix.


  8. Replace the Mslmclin.dll file in the <SMS_root>\Bin\<Platform> folder with the version obtained from the hotfix.


  9. Replace the Ccim32.dll file in the <SMS_root>\Bin\<Platform> folder with the version obtained from the hotfix.


  10. Restart the SMS_EXECUTIVE and the SMS_SITE_COMPONENT_MANAGER services. Allow the updated Compver.ini, Clicore.exe, and Ccmcore.exe files to be propagated to all Logon points and Client Access Points in the site.


NOTE: The default Client Configuration Installation Manager (CCIM) polling interval is 23 hours. Therefore, it may take up to 23 hours for the hotfixed files to be propagated to the clients. To speed up this process, you can stop and restart the SMS Client Service on each client. You can also create a software distribution for one of the Resource Kit tools Setevnt.exe or Cliutils.exe along with the appropriate parameter(s) to start a CCIM work cycle. For information on the proper syntax to use with these tools, see the Resource Kit documentation.

Additional query words: prodsms client=no

Keywords : kbClient kbMMC kbSMS200 kbSMS200bug kbDiscovery
Version : winnt:2.0
Platform : winnt
Issue type : kbbug


Last Reviewed: January 5, 2000
© 2000 Microsoft Corporation. All rights reserved. Terms of Use.