Special Ed Posted August 16, 2012 Report post Posted August 16, 2012 I'm running a simple OSD of Win7 through SCCM 2012. I'll boot from a CD/PXE and when my WinPE connects and I select my TS to run, it creates an "Unknown" device in SCCM with the MAC address of my target machine in it's properties. After the TS completes, I have another device created with my proper machine name in SCCM, client installed, etc. The original 'unknown' device is still there. Did I miss a setting someplace that would cause this behavior? I would have expected my completed TS would then update the original "unknown" device so that it has the updated machine name etc. I don't want to have to delete a bogus 'unknown' everytime I run an OSD. Quote Share this post Link to post Share on other sites More sharing options...
sdrichard Posted August 17, 2012 Report post Posted August 17, 2012 Is the unknown machine tagged as obsolete? Quote Share this post Link to post Share on other sites More sharing options...
Special Ed Posted August 17, 2012 Report post Posted August 17, 2012 Nope. Quote Share this post Link to post Share on other sites More sharing options...
sdrichard Posted August 17, 2012 Report post Posted August 17, 2012 Just curious, have you tried imaging another machine and see if the unknown device will update itself (updated mac info) to the new machine being imaged? Quote Share this post Link to post Share on other sites More sharing options...
Special Ed Posted August 20, 2012 Report post Posted August 20, 2012 I'm still working on the details of this.. but this appears to be 'normal behavior' which bugs me as I think it's poorly implemented. It appears that if a machine fails during a TS, or is interupted, SCCM leaves the unknown device in the system. Even if I re-image that machine, starting a new TS from scratch, it actually leaves the old object in place. Which was weird. If you watch a TS from start to finish, you can see the unknown device get created at start, which is normal, and then get renamed later at the end of the TS. This appears to be documented and there are discussions about if it's a 'bug' or a feature. Here's some posts on the process. But it appears that admins are going to have to keep an eye on cleaning up unknown devices for a while. Initial post http://verbalprocessor.com/2012/04/06/unknown-computer-bug-in-configuration-manager-2012/ Update http://verbalprocessor.com/2012/04/17/unknown-computer-bugupdate/ Final post http://verbalprocessor.com/2012/05/07/unknown-computer-bugfinal-update/ Quote Share this post Link to post Share on other sites More sharing options...
tmiller_hockey Posted August 20, 2012 Report post Posted August 20, 2012 Thanks for the information! Quote Share this post Link to post Share on other sites More sharing options...
