Ok, here is the background:
-25 computer lab with SCCM 2012 Client installed.
-New image advertised to the lab
-Most computers take the image fine, and finish, but are not bound to domain.
-Due to prior problems, when I image machines I generally go into AD and delete the account. Then bind the computers, giving them the same names as before, and add them back to the correct OU.
Here's where it gets funny.
After imaging and rebinding, I deployed a simple task sequence to the collection in SCCM. After waiting 24 hours, the progress for the Deployment showed all machines in the "Unknown" category. Upon investigation, the last client check in was prior to imaging.
So, Problem/question #1: It looks like since I deleted the records in AD, and then remade them, SCCM lost track of which computers they really were. Has anyone else seen this? If so, what is the best way to accomplish this?
While trying to fix this, I decided to Delete the records in SCCM as well, hoping that HeartBeat Discovery will find the new AD accounts and add them back into SCCM.
Question 2: Will this work? Or will the discovery agent see that records with the same names have already been deleted and not add them?
Thanks for any suggestions!
Andy