Hi Guys, I've got AD discovery setup to run every day, so new workstations that have been added to AD get detected fine. When we are deploying an OS to a brand new machine via SCCM we have to manually import that machine (by specifying its name and MAC address) so that we can add it to the collection that the OS deployment advertisement is targetted at. As part of our OSD task sequence the new machine gets joined to the domain, but the problem is that the next time the AD discovery runs it picks up this same machine from the domain despite already having a record for this machine (the one that we manually imported so that we could do the OSD). How do we stop this duplicate from being created? I refuse to believe that this is by design as I assume most people have a very similar procedure to ours. Thanks ChrisMy website: www.cjwdev.co.uk My blog: cjwdev.wordpress.com

Hi, I normally use this script http://kristianfthomsen.spaces.live.com/blog/cns!59A30145A64F8A9F!156.entry for merging duplicate records, it works with OSD Refresh scnerario aswell. I normally schedule it as a status filter rule but the schedule task in this blog will do the trick. Regards, Jörgen-- visit my System center blog at http://ccmexec.com --

Hello - As far as I know, the AD system discovery won't create any new object for the system, if it’s already discovered and the record is already there in the DB? It will just update an existing record. This is the same method used for the already discovered systems through AD system discovery. I think, that is the process. And if you look at the properties of the workstation from console you may see the Agent Name and Agent Time are updated after AD system discovery. Anoop C Nair

Hi, I normally use this script http://kristianfthomsen.spaces.live.com/blog/cns!59A30145A64F8A9F!156.entry for merging duplicate records, it works with OSD Refresh scnerario aswell. I normally schedule it as a status filter rule but the schedule task in this blog will do the trick. Regards, Jörgen -- visit my System center blog at http://ccmexec.com -- But the manual computer entry is not being marked as obsolete, so does this still apply? Also, surely I shouldn't have to run a script just to make the system work properly when I'm using it as it is supposed to be used.My website: www.cjwdev.co.uk My blog: cjwdev.wordpress.com

I assume most people have a very similar procedure to ours. Have SCCM R2/R3 Feature which eliminates importing the MAC address of computers .You can also eliminate running the Task sequence by unknown users using protected Task sequence. http://www.windows-noob.com/forums/index.php?/topic/2336-password-protect-a-task-sequence/ //Eswar Koneti @ www.eskonr.com

Hello - As far as I know, the AD system discovery won't create any new object for the system, if it’s already discovered and the record is already there in the DB? It will just update an existing record. This is the same method used for the already discovered systems through AD system discovery. I think, that is the process. Well that is what I would have expected, but not what seems to be happening. Both systems have identical values in all of their properties, apart from one having an additional Agent Name property with a value of "Manual Machine Entry" My website: www.cjwdev.co.uk My blog: cjwdev.wordpress.com

I assume most people have a very similar procedure to ours. Have SCCM R2/R3 Feature which eliminates importing the MAC address of computers .You can also eliminate running the Task sequence by unknown users using protected Task sequence. http://www.windows-noob.com/forums/index.php?/topic/2336-password-protect-a-task-sequence/ //Eswar Koneti @ www.eskonr.com I'm not sure which feature you are referring to - all I see mentioned in that link is the password featureMy website: www.cjwdev.co.uk My blog: cjwdev.wordpress.com