Im facing a small problem in my SCCM 2007. During OS Deployment we pre-stage the client in the SCCM server by importing computer information using Mac Address and computer name. And then we add this information into our custom OSD collection. Once the OS is deployed into that computer 1 record is added into All systems Collection & 1 in OSD collection (although its added straight away when we import computer information). Now the problem iswhenwe deploy the image 3-4 times again into the same computer 3-4 Records are added into All Systems Collection which makes makes the collection looook like a junkyard. My question is how to solve this duplication problem in the collections ? And because of this duplication the same computers face PXE boot issues to SCCM 2007 because no advertisments are available to those computers

Seeeeeeeeeeeeems like nobody is facing the same problem or doing the MASS OS Deployment

How are your deployments done? Full Media, Boot Media, or from RAP?From Boot Media or Full Media, we have a pre-execution hook that deletes the record from the SCCM database...seems to work fairly well. If you want, I can post snippets of that code, along with pre-excution hook instructions (from MS).

I have the some "problem",I install with WDS and then it duplicate the GUID for the machine. I also have problem when installa and reinstalling computer during my test phase that the object get dorrypt and i have to delete completly from database and the add it again after a short wile.

Im using PXE method to connect to the SCCM 2007 and then start the OSD on client computers Here are the screenshots about the problem which i m facing @ moment You can see mutiple Duplicate Records because i have done the image on the same computer 4 times in 2 days Status Screenshot about the same duplicate Records Because of this problem i m not able to PXE boot to the SCCM 2007 for OSD. If i want to start OSD on the same computer then i delete the computer records in the above collection which i mentioned. Import computer information again to the collection and then it starts PXE booting again to SCCM 2007. Hence only then i m able to do the OSD

Chaudry, How do you do collections like you did on the pictures for different types of hardware? I have been trying to figure this out, and had no luck. Could you please post the query statement you used. Thanks

Donnie Taylor wrote: How are your deployments done? Full Media, Boot Media, or from RAP?From Boot Media or Full Media, we have a pre-execution hook that deletes the record from the SCCM database...seems to work fairly well. If you want, I can post snippets of that code, along with pre-excution hook instructions (from MS). Hi, I would really appreciate it if you could post the code and instructions for deleting the record via a a pre-execution hook. I want to do the exact same thing. Thanks in advance, Chris

The answer is you will always get a new resource ID when you build a machine. I've tried several different scripts, but the engine that creates machine resource ID's in SCCM always creates a new record once the OS is loaded and the SCCM client is installed (and communicated back to SCCM). Right now we have a custom .hta file that adds machines to a collection. I'm looking at a script that will run as one of the last task sequences. This script will then delete the machine from that "imaging" collection. This way advertisements for OS deployment will not show up on the newly-built client. We are also looking at advertising the build task sequences to specific people, rather than collections. These people are our technicians that build the machines. But anyway, there may be a way to loop through SCCM and delete ALL records obsolete or not from SCCM just before the new machine is built. That way there will always be only one record. The problem with that is, someone might but the wrong machine name in and delete someone else's machine from SCCM.

I use the following script to remove all instance of the machine (by Name) from SCCM as the last step in my task sequence. Note this script need to run as a user with admin right to SCCM: Set WshNetwork = WScript.CreateObject("WScript.Network") sComputer = WshNetwork.ComputerName 'Get the computer name 'Find all instances of this computer name and delete sSMSServer = "[SCCM Server Name]" sSiteCode = "[Site Code]" Set lLocator = CreateObject("WbemScripting.SWbemLocator") Set gService = lLocator.ConnectServer(sSMSServer,"root\sms\site_" & sSiteCode) set ResIDs = gService.ExecQuery("SELECT * from SMS_R_System where Name = '" & sComputer & "'") for each oResID in ResIDs 'WScript.Echo "Deleting " & oResID.Name oResID.Delete_ Next