SCCM CB PXE problems

[neonetman]

I've installed a working SCCM CB server, and tested some sample tasks sequences to ensure everything was working (whcih it was)

 

I've now migrated all my collections, software, deployments etc from my 2007 server,and am now having an issue with PXE booting one of the PCs

 

When I power on, it sits for ages before coming up with

 no boot filename received

When i check the system status messages in the console I get the following:-

The PXE Service Point intructed device to boot normally since it has no PXE deployment assigned.

. I initially had this device in a collection with a PXE enabled task sequence, however I've now deleted it as I would expect an unknown machine to get the "abortpxe" boot.

 

I'm so close to getting sorted, yet I seem to have hit a brick wall with this

 

Can anyone suggest?

 

Cheers

[Steve21]

That's normal really. Unless you've forced a required deployment to it. If you have an available one set, you'd need to hit F12 etc to boot into the pxe and select one manually etc

 

On your Task Sequence what is it set to in regards to Deployment? Normally you'd have like All Systems and All Unknown systems set as available if you want to manually pick when it builds

 

Steve

[neonetman]

Should it not pick up the "abortpxe" boot if there's no task sequence assigned? That's what it did before I migrated data.

 

It currently sites for about 30 seconds before it decides it's got no filename

[Steve21]

What do you call none assigned? There's no TS deployed at all that'll match it? Or it's not assigned as required?

 

When you let it boot, it should contact the SCCM, download the WDSNBP, Check against Policies, (Give option to F12) then exit PXE if not. Assuming nothing is required to deploy.

 

If you haven't even deployed a TS to unknown computers, or you don't have the computer in the database already, you'll get the no file name received like you said

 

Steve

[neonetman]

Sorry - I'm not explaining very clearly:-

 

When I first installed SCCM on the new server, if I PXE booted a PC (before I created any deployments/task sequences), it would contact the server, look for policy, the go to abortpxe

I then added a device, assigned a required task list. The device booted and ran the task sequence as planned. If the same machine booted again, because it had the PXE flag set, it would again contact the server, look for the policy and the go to abortpxe

 

 

Now, after migrating all my content across from the old server, machines that are not registered do not come up with "looking for policy" and then fail to abortpxe - instead they just get no boot filename

 

Obviously I assume that getting the boot file, and then going to abortpxe is the correct behaviour, as that was the default prior to migrating data in - yet I can't find out how to get back to that

[buzzard]

Do you have any paths in your content you migrated that reference the old server at all? How did you migrate the data to the new server? I usually work through this - https://technet.microsoft.com/en-us/library/gg712697.aspx?f=255&MSPPError=-2147217396 Edited November 15, 2017 by buzzard

[neonetman]

No that I can see - but as a reasnably newcomer to SCCM I'm not sure if I'm missing something

[Steve21]

You shouldn't be getting abortpxe at all. It should be a standard pxe exit if there's nothing to do.

 

But in regards to my questions above:

 

Is this pc known to the SCCM server? e.g. in the database if you migrated it. Or is it unknown e.g. never touched it before now?

 

If it's unknown, do you have a Task Sequence Deployed to Unknown machines as Available? (Or any other TS deployed if it's known already)

 

If this is a new server (rather than rebuild), did you setup switches/DHCP to point to it for PXE boots?

 

(Sorry for step by step questions but bit hard to help without knowing bit more )

 

Steve

[neonetman]

I've tried with both a device that's migrated (although it has no MAC address in it), and also with a complete unknown.

 

We have no TS applied to unknown computers (nor did we on our last server)

 

If I assign a task sequence, and imprt the PC it will run the TS, so I know DHCP/PXE is working.

 

What I'm used to getting (from the old server, and from this one before I migrated data in) was what is in the screenshot below, however I'm not getting that

[Steve21]

I honestly have no idea what you guys are doing on your end...

 

If you're saying you never have a TS applied to unknown computers you'll never get a pxe for them as it doesn't have anything assigned (as per the log message in your 1st post).

 

If you are manually creating a machine in SCCM and then using it that route to deploy to that's very long winded for no reason But you still shouldn't be getting an abortpxe, as it should be using whatever you're passing it via option 66/67 in DHCP etc as it's bootfile (or via switches if you're doing it that route). Unless you've changed IPs too as I asked above.

 

But as you're saying nothing is deployed to the machine, and there's no task sequences assigned to it, there is nothing that copying old packages across should have changed to affect it, unless you copied over boot images etc too?

 

Just humour me, and assigned a TS to unknown machines (as available, not required) and try it again and see what it says. (Assuming this is an unknown machine again, and hasn't been imported)

 

Steve

[neonetman]

Thanks for your help Steve - as to what we're doin - that would be bimbling through with the blind leading the blind. Thankfully, I've jsut about got it cracked now