Matt Hinson

Ibrafe, You probably already have an answer to this since it's been almost a month, but figured I'd chime it as I've just seen this. Are you currently managing the OSX, Linux, and Server OS's via SCCM? If so, simply create collections with a query to find all machines for each OS type (separate collections). Then, create a collection including the no client query, limit it to All Systems and create Exclusion rules for the collections of OS's you created to exclude them from your No Client Collection. Hope it works out for you. -Matt

Could you provide you ClientIDManagerStartup.log for this client? Also, you say you are unable to install the client through SCCM; does this mean you were trying to leverage client push? If so, does your SCCM site server have admin permissions on the client or do you have a client install account that has admin permissions on the client? Also, what do your boundaries look like? Are you using AD Site definition, IP subnet definition, or IP Address range definition?

This is a byproduct of leveraging unknown computer support. During the TS process, SCCM has to create an object for any "Unknown" computers so that the SCCM database can "recognize" it and thus service it in the TS. If during the TS, the TS fails, SCCM does not remove the "orphaned' Unknown computer object. It has to be manually deleted. http://blogs.technet.com/b/inside_osd/archive/2012/05/02/managing-unprovisioned-computers-in-system-center-2012-configuration-manager.aspx

Shawn, Also reference this if you need: http://technet.microsoft.com/en-us/library/bb680705.aspx Good luck!

Have your checked your boundaries/boundary groups and ensured they are associated with the correct DPs your client(s) are pulling from?

Hi Shawn, Just to clarify, are you currently leveraging SCCM to deploy images? As long as you have the correct NIC drivers injected into the boot image you are using for the task sequence, it'll pick up the NIC. If you have not done that, that is your first step. Your second step will then be to update the boot image on your DPs, then you will want to create new media that will include the new updates you made to your boot image. As far as needing PXE or MDT, you don't need either. PXE is nice, but too much overhead in my opinion and you don't need MDT if you are using SCCM (sorry for all the MDT lovers out there, I know that is blasphemy!). Also, neither of these are going to help you with your issue. Any non-recognition of the NIC is due to drivers not being in the boot image. Best, Matt

Create a new collection and leverage direct membership of the Unknown Computer object type. You don't have to worry about selecting any "sub properties", just select Unknown Computer from the drop down and then put "%%" in the text box at the bottom. This will aggregate the unknown computer objects for you to select and place into the new collection that you can modify the collection properties on and thus allow you to create the OSDComputerName variable needed to rename the computer in the TS.