Difference between revisions of "Microsoft KB Archive/253994"

From BetaArchive Wiki
(importing KB archive)
 
m (Text replacement - """ to """)
 
Line 12: Line 12:
 
<div id="TitleRow">
 
<div id="TitleRow">
  
= <span id="KB253994"></span>SMS: Network Discovery Does Not Change &quot;client=1&quot; to &quot;client=0&quot; When SMS Client Is Uninstalled =
+
= <span id="KB253994"></span>SMS: Network Discovery Does Not Change "client=1" to "client=0" When SMS Client Is Uninstalled =
  
  
Line 56: Line 56:
 
== CAUSE ==
 
== CAUSE ==
  
This behavior occurs because the Network Discovery agent does not include the &quot;client&quot; property in discovery data records (DDRs) that it generates.
+
This behavior occurs because the Network Discovery agent does not include the "client" property in discovery data records (DDRs) that it generates.
  
 
</div>
 
</div>
Line 86: Line 86:
 
=== sp_SMSDisplayOldClient ===
 
=== sp_SMSDisplayOldClient ===
  
This procedure lists all systems that have not been discovered by Windows NT Logon Discovery or Heartbeat Discovery within the specified day interval and whose client property is currently set to &quot;installed&quot; (1).<br />
+
This procedure lists all systems that have not been discovered by Windows NT Logon Discovery or Heartbeat Discovery within the specified day interval and whose client property is currently set to "installed" (1).<br />
 
<br />
 
<br />
 
Syntax: sp_SMSDisplayOldClient [<code>dayinterval</code>]<br />
 
Syntax: sp_SMSDisplayOldClient [<code>dayinterval</code>]<br />
Line 93: Line 93:
 
=== sp_SMSUpdateOldClient ===
 
=== sp_SMSUpdateOldClient ===
  
This procedure changes the client property to &quot;not installed&quot; (0) on all systems that have not been discovered by Windows NT Logon Discovery or Heartbeat Discovery within the specified day interval and whose client property is currently set to &quot;installed&quot; (1).<br />
+
This procedure changes the client property to "not installed" (0) on all systems that have not been discovered by Windows NT Logon Discovery or Heartbeat Discovery within the specified day interval and whose client property is currently set to "installed" (1).<br />
 
<br />
 
<br />
 
Syntax: sp_SMSUpdateOldClient [<code>dayinterval</code>]<br />
 
Syntax: sp_SMSUpdateOldClient [<code>dayinterval</code>]<br />

Latest revision as of 13:52, 21 July 2020

Article ID: 253994

Article Last Modified on 10/25/2006



APPLIES TO

  • Microsoft Systems Management Server 2.0 Standard Edition
  • Microsoft Systems Management Server 2.0 Service Pack 1
  • Microsoft Systems Management Server 2.0 Service Pack 2



This article was previously published under Q253994

SYMPTOMS

Clients that have been uninstalled from a site may still be reported as existing clients in the discovery database, preventing Windows NT Remote Client Installation from attempting to reinstall uninstalled clients. This issue occurs only under the following circumstances:

  • Windows NT Remote Client Installation is the only enabled installation method.
  • Network Discovery and Heartbeat Discovery are the only enabled discovery methods.


CAUSE

This behavior occurs because the Network Discovery agent does not include the "client" property in discovery data records (DDRs) that it generates.

RESOLUTION

To resolve this problem, obtain the latest service pack for Systems Management Server version 2.0. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

236325 How to Obtain the Latest Systems Management Server 2.0 Service Pack


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 Systems Management Server 2.0 Service Pack 4.

MORE INFORMATION

There are two stored procedures to implement this fix: sp_SMSDisplayOldClient and sp_SMSUpdateOldClient. The 60052.sql script creates both of them.

sp_SMSDisplayOldClient

This procedure lists all systems that have not been discovered by Windows NT Logon Discovery or Heartbeat Discovery within the specified day interval and whose client property is currently set to "installed" (1).

Syntax: sp_SMSDisplayOldClient [dayinterval]

dayinterval is the number of days within which a client is considered current. Set this value to something higher than the Heartbeat Discovery interval. The range is 1 - 366.

sp_SMSUpdateOldClient

This procedure changes the client property to "not installed" (0) on all systems that have not been discovered by Windows NT Logon Discovery or Heartbeat Discovery within the specified day interval and whose client property is currently set to "installed" (1).

Syntax: sp_SMSUpdateOldClient [dayinterval]

dayinterval is the number of days within which a client is considered current. Set this to something higher than the heartbeat discovery interval. The range is 1 - 366.

NOTE: To provide ongoing maintenance, you can schedule sp_SMSUpdateOldClient to run as a recurring SQL command in the Systems Management Server (SMS) Administrator console. To do so:

  1. Stop the SMS_SITE_COMPONENT MANAGER and SMS_EXECUTIVE services.
  2. Run the 60052.sql script by using SQL Query Analyzer or ISQL/W.
  3. Restart the services that you stopped in step 1.
  4. In the SMS Administrator console, expand the Site Hierarchy, Site Code, Site Settings, Database Maintenance, and SQL Commands nodes.
  5. Right-click the node, point to New and then click SQL Command.
  6. Type a descriptive name for the command.
  7. In the SQL Command box, type the following line:

    exec sp_SMSUpdateOldClient [dayinterval]

  8. Select a log path.
  9. Set an appropriate schedule.
  10. Click OK.



Additional query words: prodsms

Keywords: kbqfe kbhotfixserver kbbug kbfix kbsms200presp4fix KB253994