Some of our OSD task sequences are creating two computers in All Systems, the real one that is Client=Yes, Active=Yes, Obsolete=No. Then there's another with the same name, Client=No, Active=NULL, Obsolete=NULL We can't figure out what is causing it, any ideas how to troubleshoot this?

I have seen this happen when AD System Discovery runs during the time a task sequence is running. Have you examined both resources in the console and looked at which discovery methods are creating them, the discovery times, and their creation dates? This will verify if the case is what I've seen in the past.Jason | http://myitforum.com/cs2/blogs/jsandys | Twitter @JasonSandys

That sounds right, the only discovery methods for the duplicates are from AD. Maybe what is happening is on new systems there is no duplicate, but for re-imaged computers or re-used computer names it creates dups. A workaround might be to delete the AD account first. I'll try that, thank you for your help.