[sccm 2012] PXE problem

[newpersn]

Screen shot attached

 

Is there something I'm missing?

 

Thanks

 

Newp

 

[free780]

Have you got any task sequences deployed to the pc? Does sccm know of the pc or is unknown?

[newpersn]

Have you got any task sequences deployed to the pc? Does sccm know of the pc or is unknown?

 

Ive tasked it to deploy an OS, Ive added its MAC in to SCCM so i cant see it being unknown?

[Norphy]

What he said plus is that IP address part of a boundary or boundary group in SCCM?

[newpersn]

What he said plus is that IP address part of a boundary or boundary group in SCCM?

 

That IP is inside the boundary group within SCCM

[FN-GM]

Its usually one of these

 

• No TS Deployed
  
• MAC is incorrect in SCCM
  
• Boundaries and boundary groups incorrect
  

[Norphy]

If you deploy a task sequence to the unknown PCs group, does it boot?

[snagrat]

Have you got a x86 and x64 boot image? I find sometime you need both, but update the one you actually want to use last.

[newpersn]

Its usually one of these

 

• No TS Deployed
  
• MAC is incorrect in SCCM
  
• Boundaries and boundary groups incorrect
  

 

1: I just retasked it and still the same. (it just getting higher in the que)

2: Mac is fine. Both Match

3: They match the range of the network. Both are on the same Vlan aswell. (should i try giving a manual IP higher up the chain)

[Norphy]

One thing that's bitten me a couple of times in the past, have you made the task sequence deployment available to PXE clients? If it's only available to configmgr clients, your PC won't boot.

 

[FN-GM]

On the TS deployment settings have you got this set?

 

[FN-GM]

One thing that's bitten me a couple of times in the past, have you made the task sequence deployment available to PXE clients? If it's only available to configmgr clients, your PC won't boot.

 

[ATTACH=CONFIG]24930[/ATTACH]

 

Beat me!!!

[newpersn]

One thing that's bitten me a couple of times in the past, have you made the task sequence deployment available to PXE clients? If it's only available to configmgr clients, your PC won't boot.

 

[ATTACH=CONFIG]24930[/ATTACH]

 

Being blind here. Where do i find that?

[Norphy]

Go to your task sequence, click on the deployments tab, right click on the deployment and click properties.

 

[newpersn]

Go to your task sequence, click on the deployments tab, right click on the deployment and click properties.

 

[ATTACH=CONFIG]24932[/ATTACH]

 

Thank you. Still didnt make a diffence tho.

 

Is it anything to do with the policy its waiting for?

[free780]

Have you got the respond to pxe clients ticked in the DP settings?

[FN-GM]

Have you got the respond to pxe clients ticked in the DP settings?

 

I don't think that would be the issue. In the screenshot we can see its picked up the SCCM server.

[synaesthesia]

The MAC address looks "odd". Like with some new PC's with BIOSes that report incorrect smbios GUIDs, SCCM often has a paddy because it's then not unique. It either won't therefore PXE boot because it's already known (when deploying to unknown computers, I prefer that method rather than manually adding to a build group) or it's conflicting.

[FN-GM]

Try another bit of hardware if you can.

[newpersn]

The MAC address looks "odd". Like with some new PC's with BIOSes that report incorrect smbios GUIDs, SCCM often has a paddy because it's then not unique. It either won't therefore PXE boot because it's already known (when deploying to unknown computers, I prefer that method rather than manually adding to a build group) or it's conflicting.

 

This is a virtual pc. I've set the mac manauly

 

Just reset it and still the same.

[Norphy]

Does it boot if you allocate your task sequence to the unknown PCs collection?

[newpersn]

I got somewhere before I left work.

 

It boots in to wds. And asks for password. I select the task and it says it can't find it.

[free780]

You may need to distribute the content.

[newpersn]

You may need to distribute the content.

 

How would I do that? I only run the 1 server.

[free780]

You still have to right click on the task sequence and distribute the content.