Configuration Manager looking for policy, and PXE aborts.

Question

_{Friday, November 13, 2015 12:55 PM}

1. Machine doesn't exist on SCCM

2. I've manually imported the machine into SCCM via the MAC Address I put the machine in a test collection and advertise a imaging task to that, I still get Configuration Manager is looking for policy and pxe aborts

3. We have task advertised to the Unknown Computers group so if this troublesome machine is unknown to SCCM it should have picked up the advertisements that are advertised to the unknown Computers collection. It doesn't I still get Configuration manager is looking for policy and PXE aborts.

4. I haven't had any luck looking for duplicate guids, I can't find a proper query that actually works

5. The time and date on the machine is correct.

What do I do?

All replies (6)

_{Friday, November 13, 2015 1:16 PM ✅Answered}

Examine smspxe.log. It will tell you which ResourceID was used to determine if a deployment was available.

Torsten Meringer | http://www.mssccmfaq.de

_{Friday, November 13, 2015 12:58 PM}

Check the Task Sequence is deployed to ConfigMGr clients, boot media and PXE.

Cheers Paul | http://sccmentor.wordpress.com

_{Friday, November 13, 2015 1:03 PM}

it is.

Also any other machine in my environment can boot pxe and get the policy and I am able to image it without any issues, so I know it's not an issue with WDS or PXE in ConfigMgr.

_{Friday, November 13, 2015 1:09 PM | 1 vote}

Are you using some sort of Ethernet dongle to image the computer. When you added the computer is the MAC unique when you look at the SMSpxe.log what does it tell when this computer is being image. Does it show the right MAC.

To me if everything is deploy right like you said and this computer doesn't get the unknown computer task sequence it's because SCCM is aware of him but might have 2 computer with the same MAC/GUID that is in another collection that doesn't have a TS apply to it.

I would start looking at this.

_{Friday, November 13, 2015 2:38 PM}

Take a look at this blog post: http://blogs.technet.com/b/cmpfekevin/archive/2013/11/21/import-computer-does-not-show-up-in-collection.aspx

What is your limiting collection for the test collection?

Also, if you deployed the task sequence to unknown computers, make sure you remove the manually imported device and all references to it.  Then it will truly be unknown and *should* pick up the deployment to unknown computers.

Jeff

_{Wednesday, August 23, 2017 2:02 PM | 1 vote}

On your Boot Image Properties in Data Source tab make sure the "Deploy this boot image from the PXE-enabled Distribution Point" is checked