Handling Duplicate Systems in SMS 2.0 Bruce Jones Alliance Support Professional Premier Microsoft Co

1
Handling Duplicate Systems in SMS 2.0Bruce
JonesAlliance Support ProfessionalPremierMicros
oft Corporation
2
Overview

• Handling duplicate systems white paper
• What is a duplicate GUID?
• What kinds of problems does it cause?
• How do we clean the client?
• How do we clean the database?
• Sample action plan
• Question and answer

3
What Is a GUID?

• GUID globally unique identifier
• Similar to SMS 1.2 SMSID
• Stored three places on client and in database
• HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\Client\
  Configuration\Client Properties\SMS Unique
  Identifier (one line but wrapped here for
  readability)
• windir\ms\sms\core\data\smsuid.dat
• windir\smscfg.ini
• System_DISC and System_DATA tables

4
What Is a Duplicate GUID?

• Definition multiple machines with the same GUID
• Similar to SMS 1.2 duplicate SMSIDs
• Not a result of
• Reinstalling one machine repeatedly
• Changing a machine name repeatedly

5
Causes of Duplicate GUIDs

• Upgrading an SMS 1.2 site with existing duplicate
  SMSIDs
• Imaging
• SMS Installer repackaging during SMS client
  installation process - Q183398
• Most common imaging

6
Commonly Reported Problems

• Machines disappear in collections
• SMS Executive (Dataloader)
• High memory utilization
• CPU utilization
• Windows NT Remote Client Installation doesnt
  work
• Excessive inventory resynchronizations

7
Similar problems Not caused by duplicate GUIDS

• Same machine appears multiple times in a
  collection
• Discovery properties of one machine get mixed
  with those of another
• Shared docking stations - Q259249
• DNS reverse lookup table mismatch - Q244335

8
Not Supported

• Imaging GUIDs and SMSIDs has never been supported
• SMS Administrators Guide page 145
• Like SMS 1.2, SMS 2.0 does not support client
  cloning because each client must have a unique ID

9
Two Methods to Clean the Client

• Manual
• Deinstall smsman /u /s or 20clicln.bat
• Remove GUID from 3 client locations
• Newuid.exe from SMS Resource Kit
• Newuid.exe /s /allocate
• Customizable

10
Identifying Specific Clients

• No perfect solution
• Strategy machine name changes
• Compare discovery, data, history tables
• When more than two machines share one GUID
  imaging?
• Queries (see white paper)
• TSQL query to generate report
• WQL queries
• Clean any master images (Q257808)

11
Three Ways to Deliver Newuid.exe

• Logon scripts
• Copy down once locally
• Run only if tag file exists or
• Advertisements
• Query provided in white paper
• Must run job repeatedly
• Manually

12
Four Methods to Clean the Database

• How to clean up duplicate computer IDs - Q254735
• Delete special six WQL queries
• Delete special direct membership rule
• SQL task TSQL query

13
Considerations

• Not all machines run a logon script
• Deletes based on machine name changes
• Must keep duplicates in database if software
  distribution method is used
• No longer have to delete history
• TSQL query can be automated

14
Sample Action Plan

• Run daily TSQL reports to identify and clean new
  images
• Run Newuid.exe in logon script
• Advertise Newuid.exe weekly
• Run TSQL script every two weeks, or immediately
  on any heavily affected server
• Help desk handles exceptions manually

15
Questions and Answers

• Be sure to see the Handling Duplicate
• Systems in SMS 2.0 white paper for
• queries and details mentioned in this
• presentation.

16
(No Transcript)