This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
I have several computers to which I have deployed a TS for OS deployment. These computers have previously been known to SCCM, but are now deleted from AD and the CM database, so they should be treated as unknown computers. When booted using PXE, smspxe.log shows that the client is not in the database:
The client then loads Windows PE and then immediately reboots. I captured the smts.log from Windows PE and this is the problem:
However, I have two deployments to the Unknown Computers collection:
And when I test using a clean VM, the wizard starts and the two advertisements do show up. I even have a deployment to the collection of which these computers were previously part of. I don't know what else to check. I have 16 computers from this model of which 13 won't install and 3 succeeded in finding the deployment and installing the image. I would be grateful if someone could point me in the right direction.
Any particular reason why you have 2 available deployments for the same TS against the unknown collection? Perhaps delete the old one? Also, check if the time on the client is not in sync with your mp.
Sorry, I should have noted about the screenshot - these are two different task sequences installing different images, I just removed the details from the screenshot.
But what you point out about the time, may be worth checking - I remember some years ago that time skew caused such kind of problems during deployment. I will report on this next time I try it, probably tomorrow. Thanks for the suggestion!
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(150.4, 92%, 24%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EXM%3C/text%3E%3C/svg%3E)
Hi,
Hello.
The issue is not related to a networking driver - I verified using Command Prompt that an IP address is successfully obtained by DHCP.
As per your second suggestion - what do you mean by "manually import MAC addresses to a specific collection"?
I opened a case with Microsoft for this issue last week. The problem seemed to be a duplicate SMBIOS which caused confusion with the identification of the devices. All of these machines had the same SMBIOS. We added the SMBIOS value as an exception in the Hierarchy Settings - Client Approval and Conflicting Records. Then, all devices started to pick up the task sequence successfully and installed the OS image.