You've imported a new computer into SCCM 2012 R2 and have put it into a Collection which has a Operating System Task Sequence deployed to it. When you boot the machine up, however, it talks to the SCCM server and then returns an abortpxe error message.
Furthermore, when you check the SMSPXE.log file on your SCCM server, you see that although SCCM knows about the machine it has no advertisement available for it:
Cause:
The Task Sequence hasn't been advertised to the Collection correctly.
Fix:
Part 1
Check that the Task Sequence is actually available to the client. Locate the client in whichever Collection you have added it to and right click > Properties of the client. Under the Deployments tab you should be able to see your Operating System Task Sequence:
If there is nothing visible here then you need to go to your Operating System Task Sequence > Right Click > Deploy and then aim it at the relevant collection.
Part 2
If the machine can see the Deployment then it's time to check the actual settings in the deployment itself. It's easy to miss when you whiz through the "Deploy" a Task Sequence wizard but it's important to check that you've actually made the TS available to PXE. To do this, right click on the Deployment and view the Properties. Switch to the Deployment Settings tab and make sure that the TS is available to whichever areas are appropriate:
If both Parts 1 and 2 are looking OK then it's time to go back to basics and have a shot or two in the dark:
- Fully delete the client from SCCM and re-import it.
- Try rebooting your SCCM server.
- Try restarting the WDS service.
No comments:
Post a Comment