/build/static/layout/Breadcrumb_cap_w.png

SCCM 2007 Manage Computers

HI

I am relatively new to SCCM 2007 and have a couple of questions.

I have noticed a number of duplicate computers and quite a few duplicate GUIDs. We are about to migrate our systems from XP to Windows 7. The computers will have the same computer name. What is the best procedure for clearing up these duplicates - can you just delete the computers prior to re-imaging. If so what are the consequences does deleting a computer cause any problems with SCCM. We are using Ghost to deploy the OS at the moment but will look into OSD via SCCM in the near future. We do not install the client on the image - but use SCCM to deploy it - as I know that this can cause duplicate GUIDs - not sure how we have so many. One reason could of been the fact that we might of renamed the computers while moving them to another room. This I believe can cause a duplicate GUID. However this would not account for them all?

Any help would be appreciated


0 Comments   [ + ] Show comments

Answers (5)

Answer Summary:
Best way is to remove the machine record if you are rebuilding a device or reinstalling the client and also set the rules to clean up old client data and obsolete clients on a pre-defined frequency.
Posted by: GAKIS 12 years ago
Fourth Degree Green Belt
3

You can delete them but if you are doing AD discovery they will return until cleaned up in Active Directory.

If you reimage a machine or reinstall the client you will get a new Unique ID in sccm and in turn get a duplicate entry.  I find the best way is to remove it if you are rebuilding a device or reinstalling the client and also set your Rules (pending how long you would like) to clean up old client data and obsolete clients.

Posted by: pjgeutjens 12 years ago
Red Belt
1

this might be an interesting article for you:

http://blogs.technet.com/b/csloyan/archive/2010/04/27/system-center-configuration-manager-and-duplicate-guid-s.aspx

assuming of course you haven't already read that. Also, afaik, you CAN manually remove the duplicate entries without repercussions.

Posted by: adilrathore 12 years ago
4th Degree Black Belt
0

The duplicate IDs have always been a cause of concern. You need to follow 2 quick steps:

1. Set the option to automatically create new ID in case a duplicate has been detected.

2. Run maintainance on the database for cleaning up machine records with same IDs. You can also run a report of the workstations with duplicate IDs just track the situation.


Comments:
  • Just to add to it from the process perspective, before reimaging a workstation the concerned engineer can drop a mail to the SCCM / AD admins to cleanup the records from their respective databases. This would make the data more reliable. - adilrathore 12 years ago
  • Silly question.... where is the option found listed in #1? - dheinz 11 years ago
Posted by: rodtrent 12 years ago
Orange Belt
0

Here's a few additional pieces of info to get you going...

 

Find and Fix Duplicate GUID issues in SMS and SCCM

Content provided by myITforum. Read the rest: http://myitforum.com/myitforumwp/2011/10/20/find-and-fix-duplicate-guid-issues-in-sms-and-sccm/


OSD/Task Sequence/PXE – Duplicate SMBIOS GUIDs (System UUIDs) in SCCM 2007

Content provided by myITforum. Read the rest: http://myitforum.com/myitforumwp/2011/10/21/osdtask-sequencepxe-duplicate-smbios-guids-system-uuids-in-sccm-2007/

Posted by: psalwey 12 years ago
White Belt
0

Make sure you are cleaning up the computers in AD when reimaging. Also you can choose to either merge, block, or create new records when you find conflicting records. Here is a pretty good reference:

http://ckrim.blogspot.com/2010/12/obsolete-objects-reuse-your-old-sccm.html

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ