Hi All,
we are using SCCM 2012 R2 on Windows Server 2012 for OS Deployment of Windows 7 Enterprise X64.
First of all, it's hard to ask this question because I read so much about the obsolete record story so I should already be a pro on this :-).
We have a strange behavior on new clients. This is how we proceed:
Task Group 1
1. Import single computer with MAC Address in SCCM and add to OSD Collection. --> Results in empty Computer Object.
2. Start Client via USB stick with boot media.
3. Client installs Win 7 successfully working with the computer object created in step 1.
So OSD works very well at all and the client is up and running afterwards. For test reasons we currently do a lot of re-installations in the following way.
Task Group 2
1. Without any modification on the client created in Task Group 1, shutdown the client.
2. Delete the computer object for that client in SCCM Console.
3. Import the computer object again through the console with its MAC Address and add to OSD Collection
4. Start Client via USA stick with boot media.
5. Client installs Win 7 successfully.
Again, everything works well but now sometimes (lets say 4 of 10) clients come up and a second computer object with the same Name is created while the one used for OSD is marked as obsolete. The SMS Data Discover Manager Component is reporting that a new object was created with a possible cause of changed hardware. First, it's the same computer (laptop) used and second, to which hardware ID should SCCM compare ? I've deleted the object and couldn't even find a record in the DB for it, so why is SCCM forcing the client to use a new SMS GUID (i can see it in the clientID log) and creating a new record, marking the old one obsolete. I can also see that the SMS GUID of the obsolete record is set as previous SMS GUID on the new record. So all would be correct, but I can't find the reason why SCCM is initiating this process for that record.
There is not much time between building, deleting and re-installing the client, because we are testing some stuff right now.
So my questions are:
- How can SCCM mark the empty object using OSD as obsolet ? this object has no information's at that point (no SID, no HWID) just the netbios name on it. I also checked the vSMS_R_Systems table and the object truly has nothing set.
- Is SCCM storing some kind of information's like hardware ID in the DB even after the computer object is deleted ?
For sure, SMBIOS GUID is not changed (same machine), Machine SID is not changed, Hardware not changed. So why the hell is SCCM creating a new record although the existing record doesn't have any information's on it ?
Please help!
Cheers