SMS tries to install the client components on devices that are running Windows Embedded (831312)


The information in this article applies to:

  • Microsoft Systems Management Server 2.0

SYMPTOMS

Although the Microsoft Systems Management Server (SMS) 2.0 client is currently not supported on devices that are running Microsoft Windows Embedded operating systems, SMS may still try to install the client components on those devices. For example, SMS may try to install the client components on devices that are running Microsoft Windows XP Embedded.

Running the SMS client on Windows Embedded-based devices has not been tested by Microsoft and may cause unpredictable results.

CAUSE

This problem occurs because the various SMS client installation methods do not check to see whether a client is running Windows Embedded before they try to install the SMS client components.

RESOLUTION

Hotfix information

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.

Prerequisites

To install this hotfix, you must have SMS 2.0 Service Pack 5 (SP5) installed on your computer. For additional information about how to obtain the latest service pack, click the following article number to view the article in the Microsoft Knowledge Base:

288239 How to obtain the latest Systems Management Server 2.0 service pack

File information

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
   ----------------------------------------------------------------
   02-Jan-2004  17:37  2.0.1493.5178  169,872  Ccm.dll    x86
Note Because of file dependencies, the most recent hotfix or feature that contains these files may also contain additional files.

Installation information

Method 1: Use 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-KB831312-x86-ENU.exe update file (where X is the service pack version) to the new folder.
  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. Run SMS2.0-SPX-KB831312-x86-ENU.exe (where X is the service pack version), and then follow the instructions in the wizard.

Method 2: Manually install the hotfix

  1. Create a folder in a location that is accessible to your SMS site servers.
  2. Run the SMS2.0-SPX-KB831312-x86-ENU.exe /x command (where X is the service pack version), and then extract the hotfixed files to the folder that you created in step 1.
  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 file Ccm.dll in the SmsRootFolder\Bin\Operating_System folder with the version from the hotfix.
  7. Restart the SMS services.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

WORKAROUND

To work around this problem, follow these steps:
  1. Do not enable Windows NT Remote Client Installation if you also use Network Discovery. If you only have a few Windows Embedded-based devices, you can instead enable Windows NT Remote Client Installation and then prevent the SMS components from being installed on Windows Embedded-based devices by following the steps in Microsoft Knowledge Base article 207729. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

    207729 SMS: Excluding computers from Windows NT Remote Client Installation

  2. If Windows Networking Logon Client Installation is enabled, determine whether a client computer is running Windows Embedded before you run Smsls.bat or Smsman.exe. The following are examples of how you may be able to detect a Windows XP Embedded-based client. However, these may not work for all kinds of Windows Embedded-based devices.
    • Check to see whether the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\ProductOptions\ProductSuite registry value is set to embeddednt. For example, you can use an SMS Installer script to read this registry value.
    • Create a program that calls the GetVersionEx() function and that checks for the VER_SUITE_EMBEDDEDNT flag in wSuiteMask.

MORE INFORMATION

The hotfix that is described in this article only changes SMS_CLIENT_CONFIG_MANAGER (CCM). By default, CCM will not install the SMS client components on Windows Embedded-based devices after you install this hotfix. CCM determines whether a device is running Windows Embedded by checking to see if the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\ProductOptions\ProductSuite registry value is set to embeddednt. If it is, the Client Configuration Request (CCR) is deleted, and the following message is logged in Ccm.log if logging is enabled:
Embedded OS Detected, aborting installation for machine Computer_Name.
You can disable this new behavior by adding the following registry entry:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\Components\SMS_CLIENT_CONFIG_MANAGER

Install Client On Embedded OS=DWORD:00000001

If the value of this entry is set to 0, CCM will not install the SMS client components on Windows Embedded-based devices. This is the default behavior with this hotfix.

If this value is set to 1, CCM will install the SMS client components on Windows Embedded-based devices.

Important Even after you install this hotfix, if you have enabled Windows Networking Logon Client Installation, you still must use the workaround that is described in step 2 in the "Workaround" section of this article if you do not want any SMS files to be installed on the Windows Embedded-based devices.
Modification Type:MinorLast Reviewed:6/5/2006
Keywords:kbHotfixServer kbQFE KB831312
©2004 Microsoft Corporation. All rights reserved.