Microsoft KB Archive/310127

= SMS: Operating System Appears as &quot;Windows 9x&quot; at Parent Site =

Article ID: 310127

Article Last Modified on 10/27/2006

-

APPLIES TO


 * Microsoft Systems Management Server 2.0 Standard Edition

-



This article was previously published under Q310127



SYMPTOMS
In a Systems Management Server (SMS) implementation where a child primary site reports to a primary site, the operating system that is shown in the discovery data for clients that are running one of the following operating systems may appear as &quot;Microsoft Windows 9x&quot; at the parent site:
 * Microsoft Windows Millennium Edition (Me)
 * Microsoft Windows 98
 * Microsoft Windows 95

However, the same client record at the child primary site shows a more accurate and complete description of the operating system, for example, &quot;Microsoft Windows 98&quot;.



CAUSE
When network discovery defines a client's operating system as &quot;Microsoft Windows 9x&quot;, it flags this as a &quot;low confidence&quot; value in the discovery data record so that a more accurate value (if it exists ) won't be overwritten in the database. This works very well in a single site hierarchy.

When discovery data is forwarded to another primary site (parent site), the Discovery Data Manager component combines the new discovery data with the data that already exists in the database and sends this combined data to the parent site.

When the data is combined, the Discovery Data Manager ignores the &quot;low confidence&quot; flag and sends the &quot;Microsoft Windows 9x&quot; value to the parent site. Because this discovery data record does not have the &quot;low confidence&quot; flag set, the more accurate operating system value is overwritten.



Service Pack Information
To resolve this problem, obtain the latest service pack for Microsoft Systems Management Server 2.0. For additional information, 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

Hotfix Information
A supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that are experiencing this specific problem. This fix may receive additional testing. Therefore, if you are not severely affected by this problem, Microsoft recommends 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 fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:

http://support.microsoft.com/default.aspx?scid=fh;EN-US;CNTACTMS

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 typical support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

The SMS 2.0 post-Service Pack 3 version of this fix should have the following file attributes or later:

  Date         Time   Version         Size       File name    Platform 03-Mar-2001 15:15  2.00.1493.3203  2,429,712  Basesvr.dll  Alpha 03-Mar-2001  9:30  2.00.1493.3143    126,224  Cmprov.dll   Alpha 03-Mar-2001 22:30  2.00.1493.3182    171,792  Compmgr.exe  Alpha 03-Mar-2001 15:15  2.00.1493.3203  1,578,912  Basesvr.dll  Intel 03-Mar-2001  9:30  2.00.1493.3143     81,040  Cmprov.dll   Intel 03-Mar-2001 22:30  2.00.1493.3182    121,440  Compmgr.exe  Intel 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 that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Microsoft Systems Management Server 2.0 Service Pack 5.



MORE INFORMATION
When network discovery is run in an environment where some SMS clients run one of the following operating systems, the network discovery record for each of these clients shows the operating system as &quot;Microsoft Windows 9x&quot;:
 * Microsoft Windows Millennium Edition (Me)
 * Microsoft Windows 98
 * Microsoft Windows 95

This occurs because network discovery cannot access a computer that is running one of these operating systems to determine the specific operating system information unless file and print sharing is enabled.

In a single-tiered environment, this does not present a problem for computers that are SMS clients because the heartbeat discovery record (which is generated immediately upon client installation and at periodic intervals thereafter) does identify the more specific operating system version, and then reports it correctly to the database. Later, if network discovery again reports &quot;Microsoft Windows 9x&quot; as the operating system, the entry is ignored because more specific information is already present.

In a hierarchy with two or more tiers, when network discovery is run at a child primary site and that child site has Windows Me/98/95 clients installed, everything proceeds as previously described, except that the discovery records are then forwarded to the parent site. In this situation, the clients of the child site which appear in the parent site's database can have a more accurate operating system value such as &quot;Microsoft Windows 98&quot; overwritten with the less accurate value of &quot;Microsoft Windows 9x&quot;.

An administrator can see the client's discovery data at the central site fluctuate between these two operating system values depending on which type of discovery data record was last processed for the client.

Because of a dependency between DLLs, this hotfix includes the hotfix for the problem that is described in the following Microsoft Knowledge Base article:

299435 Cannot Run SMS Service Manager After You Apply a Hotfix

Hotfix Installation Instructions
Apply the fix in this article to all primary sites in the SMS hierarchy by using one of the following methods.

How to Use the Hotfix Installer
NOTE: You can use this method only on Intel-based computers.
 * 1) Copy the hotfix folder structure to a share on your network. Note that Q310127.exe is a Microsoft SMS Installer file that updates specific files on your site server.
 * 2) Log on to the site server by using an account with administrative privileges.
 * 3) On the site server, close the SMS Administrator console and the SMS Service Manager.
 * 4) Run the Q310127.exe tool, and then follow the directions in the wizard. You can run the file in Quiet mode by using the /S switch.

How to Manually Install the Hotfix

 * 1) On the site server, close the SMS Administrator console and the SMS Service Manager.
 * 2) Stop the SMS Site Component Manager, SMS Executive, Windows Management, and SMS SQL Monitor services on the site server.
 * 3) Replace the Basesvr.dll file in the  \Bin\  folder with the version of the file that is included with the hotfix.
 * 4) Replace the Cmprov.dll file in the  \Bin\  folder with the version of the file that is included with the hotfix.
 * 5) Replace the Compmgr.exe file in the  \Bin\  folder with the version of the file that is included with the hotfix.
 * 6) Restart the SMS Site Component Manager, SMS Executive, Windows Management, and SMS SQL Monitor services.

Additional query words: prodsms

Keywords: kbqfe kbhotfixserver kbsms200presp5fix kbmisctools kbbug kbdiscovery kbenv kbfix kbnetwork kbui KB310127

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.