SMS 2.0 does not fully install client components (831955)


The information in this article applies to:

  • Microsoft Systems Management Server 2.0 SP5

SYMPTOMS

When you try to install a Systems Management Server (SMS) 2.0 client by running the Smsls.bat file or the Smsman.exe file, SMS may not fully install the client components. If you experience this problem, all the following symptoms generally occur:
  • If you open Control Panel, double-click Systems Management, and then click the Components tab, no components are listed.
  • The only SMS client process that is running is the Clisvcl.exe process. Occasionally the Clicore.exe process runs.
  • The following registry subkey is missing:

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\Client\Sites\System

  • The following registry subkey is inaccessible and has incorrect permissions:

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\Client\client components

Additionally, the SMS client log files contain errors that are similar to the following.

In the Clisvc.log file:
Warning - cannot read client service reset schedule
Warning - cannot read client service reset interval; setting to 30 days.
Warning - cannot write client service reset schedule
In the Cqmgr32.log file:
Warning: SetRegKeyPermissions returned 2 for key path Software\Microsoft\SMS\Client\Client Components\SMS Client Base Components\Copy Queue
-*ERROR* Could not instantiate Destination Iterator
In the Wnremote.log file:
Warning: could not open base component installation properties
In the Clicore.log file:
Newer version of clibase available - SMS apps need to be stopped

CAUSE

This problem occurs when all the following conditions are true:
  • The user who runs the Smsls.bat file or the Smsman.exe file is a member of the local Power Users group or has equivalent permissions.
  • More than one SMS site uses the same domain for its logon points, and not all the sites have installed the same version of the Clicore.exe file.
  • You try to install a client that falls in the site boundaries of an SMS site that contains a newer version of the Clicore.exe file than the version that is currently in the SMSLOGON\x86.bin folder on the logon points.
  • The Clicore.exe file on the logon points contains a version of the Clibase.dll file that is older than the version of the clibase.dll file that is inside the Clicore.exe file on the client access points (CAPs) for the site where you want to install the client.
In this scenario, the Clicore.exe file will create the registry subkey

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\Client\client components

with incorrect permissions, and the installation will not be completed.

RESOLUTION

A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Systems Management Server service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support

Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.The English version of this hotfix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
   Date         Time   Version         Size       File name            Platform
   ----------------------------------------------------------------------------
   25-Feb-2003  16:35  2.0.1493.5140     238,944  Abnwcli.dll          x86
   25-Feb-2003  21:35  2.0.92.10         383,500  Apasetup.exe         x86
   25-Feb-2003  16:35  2.0.1493.5140     263,008  Bindclin.dll         x86
   25-Feb-2003  22:40  2.0.92.10       1,377,876  Ccmcore.exe          x86
   25-Feb-2003  22:40  2.0.1493.5177   1,252,768  Clibase.dll          x86
   25-Feb-2003  22:40  2.0.1493.5177   3,498,252  Clicore.exe          x86
   25-Feb-2003  16:55  2.0.1493.5144      90,480  Clisvcl.exe          x86
   25-Feb-2003  22:40  2.0.1493.5177     320,012  Cliunins.exe         x86
   25-Feb-2003  22:40  2.0.1493.5177       8,512  Cliver.exe           x86
   25-Feb-2003  22:40                         67  Compverbase.ini
   25-Feb-2003  22:40                         67  Compversmsapm32.ini
   25-Feb-2003  22:40                         67  Compverswdist.ini
   25-Feb-2003  16:15  2.0.1493.5136      35,168  Cqmgr32.dll          x86
   25-Feb-2003  16:35  2.0.1493.5140     161,120  Falclin.dll          x86
   25-Feb-2003  16:35  2.0.1493.5140     340,832  Mslmclin.dll         x86
   25-Feb-2003  16:35  2.0.1493.5140     272,736  Ndsclin.dll          x86
   25-Feb-2003  23:10  2.0.1493.5186      13,168  Ntlg_rem.exe         x86
   25-Feb-2003  23:10  2.0.1493.5186     195,440  Nt_logon.dll         x86
   25-Feb-2003  17:10  2.0.1493.5147      54,640  Odpsys32.exe         x86
   25-Feb-2003  17:10  2.0.1493.5147      60,784  Odpusr32.exe         x86
   25-Feb-2003  21:35  2.0.1493.5176     257,904  Smsapm32.exe         x86
   25-Feb-2003  22:40  2.0.1493.5177     420,384  Smsclreg.dll         x86
   25-Feb-2003  17:10  2.0.92.10         641,211  Swdist32.exe         x86
Note Because of file dependencies, the hotfix may also contain additional files.

How to install the hotfix

Using the hotfix installer

Note This method is only for Intel-based computers.
  1. Create a folder in a location that is accessible to your SMS site servers.
  2. Copy the SMS2.0-SPX-KB831955-X86-ENU.exe update file, where X is the service pack version, to the new folder.
  3. From each of the primary and the secondary SMS site servers in your environment, log on to your site server by using an account with administrative credentials.
  4. Quit the SMS Administrator console if it is running.
  5. Run SMS2.0-SPX-KB831955-X86-ENU.exe, where X is the service pack version, and then follow the wizard instructions.

Using manual installation

  1. Create a folder in a location that is accessible to your SMS site servers.
  2. Run SMS2.0-SPX-KB831955-X86-ENU.exe /x , where X is the service pack version, and then extract the hotfix files to the folder that you just created.

    Note If you run SMS2.0-SPX-KB831955-X86-ENU.exe /x on a computer that is running Microsoft Windows Server 2003, and then, in the Choose Directory For Extracted Files box, you specify a mapped drive or a universal naming convention (UNC) path back to the same server, the date and the time stamp of each hotfix file is reset to the current date and the current time. Microsoft recommends that you extract the files to a local drive letter or a remote computer so that the date and the time stamp for each hotfix file matches the date and the time stamp that are listed in this article.
  3. From each of the primary and secondary SMS site servers in your environment, log on to your site server by using an account with administrative credentials.
  4. Quit the SMS Administrator console if it is running.
  5. Stop all SMS services.
  6. Replace the following files in the SmsRootFolder\Bin\Platform folder with the versions from the hotfix:
    • Abnwcli.dll
    • Bindclin.dll
    • Clisvcl.exe
    • Cqmgr32.dll
    • Falclin.dll
    • Mslmclin.dll
    • Ndsclin.dll
    • Ntlg_rem.exe
    • Nt_logon.dll
    • Odpsys32.exe
    • Odpusr32.exe
    • Smsapm32.exe
    • Smsclreg.dll
  7. Replace the Swdist32.exe file in the SmsRootFolder\Inboxes\Clicomp.src\SWDist\Platform folder with the version from the hotfix.
  8. Replace the Apasetup.exe file in the SmsRootFolder\Inboxes\Clicomp.src\Smsapm32\Platform folder with the version from the hotfix.
  9. Replace the Ccmcore.exe and the Clicore.exe files in the SmsRootFolder\Inboxes\Clicomp.src\Base\Platform folder with the versions from the hotfix.
  10. Replace the Compver.ini file in the SmsRootFolder\Inboxes\Clicomp.src\SWDist folder with the Compverswdist.ini file from the hotfix.

    Note Rename the Compverswdist.ini file to Compver.ini.
  11. Replace the Compver.ini file in the SmsRootFolder\Inboxes\Clicomp.src\Smsapm32 folder with the Compversmsapm32.ini file from the hotfix.

    Note Rename the Compversmsapm32.ini file to Compver.ini.
  12. Replace the Compver.ini file in the SmsRootFolder\Inboxes\Clicomp.src\Base folder with the Compverbase.ini file from the hotfix.

    Note Rename the Compverbase.ini file to Compver.ini.
  13. Restart the SMS Services.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

WORKAROUND

To work around this problem, configure all SMS site servers that share a domain for logon points to use the same service pack and hotfixes.

MORE INFORMATION

This problem is more likely to occur after you install SMS Service Pack 5. SMS Service Pack 5 keeps the oldest Clicore.exe file on the logon points until all sites have installed the same version of that file.

This hotfix also includes updated versions of the Nt_logon.dll and the Ntlg_rem.exe server components. This update changes SMS NT Logon Server Manager so that it correctly copies and reads the Compver.ini files on the logon points. SMS NT Logon Server Manager will now read the content of the Compver.ini file instead of just reading the last modified date and time stamp.

After you install this hotfix, SMS_CLIENT_CONFIG_MANAGER (CCM) will process a Client Configuration Request (CCR) for a client where the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\Client\client components registry subkey is inaccessible, the new Clicore file will correct the subkey permissions, and SMS will install the client successfully.
Modification Type:MinorLast Reviewed:4/14/2006
Keywords:kbQFE kbHotfixServer kbfix kbBug kbSMS200preSP6fix KB831955
©2004 Microsoft Corporation. All rights reserved.