[sccm 2012] PXE Boot

[mbrunt]

Hi,

 

I'm running SCCM 2012 RTM. Going well so far apart from this big that I cannot seem to solve. I've followed all steps in this guide(Configuration Manager 2012 - Release Candidate - www.windows-noob.com) but when I get to Step 7 this is what i get...

 

 

So I press F12, but then I get this...

 

 

My DHCP server is on a different server than my SCCM server, these are both on the same subnet. My client is on a seperate subnet to the servers. I've had PXE boot working fine using standard WDS with MDT, but just can't get this working... heres my DHCP options...

[Gatt]

Are you deploying an X64 image or an x86 image?

 

Only asking as your "bootfile name" is smsboot\x64\pxeboot.com

 

Meaning you can ONLY deploy an x64 bit image...

 

x86 or x64 Boot Images during SCCM OS deployment | - danovich.com.au -

[mbrunt]

Yeah its 64bit hyper v that i'm deploying too.

[Gatt]

is the OS your deploying 64 bit though?

[AliG]

I had the same issue on my first attempt of sccm 2012 and spent nearly 2 weeks trying to get it working, i then reformatted and started again and briefly had the same issue but found articles surrounding the below helpful.

 

Check your boot folders are populated in SMSBOOT\x86 and x64 if not search for articles on this also there are occasions were the c:\windows\temp\bootimages folder gets corrupted or incorrect permissions lots of articles to search for on this.

 

I had to create a new WINPE boot disk from waik using the Deployment Tools Command Prompt then import it into SCCM

 

Also even if you are not using 64bit you must create both it seems

[mrbios]

point boot file name in DHCP to wdsnbp.com instead of pxeboot.com

[ChrisH]

... and if that doesn't work you need to make sure the "Deploy this boot image from the PXE service point" box is ticked on the data source tab of the boot image properties.

[mbrunt]

ok so pointing boot file in dhcp to wdsnbp.com didnt work either. Have checked data source tab and the Deploy this boot image from pxe service point is indeed ticked.

[ChrisH]

the correct path should be

\boot\x86\wdsnbp.com

on your DHCP. That is what mine is set to. You could use the x64 as well. The other thing is SCCM seems to want both x86 and x64 boot images available even if it isn't using one of them.

[mrbios]

Try this then: Software library > Boot images > Data Access > tick "copy the content in this package to a package share on distribution points" (at least i think that's the setting im thinking of)

 

Might sound stupid but just check the content locations tab as well and make sure your boot image definitely has a location, might be worth validating it and checking logs to make sure it validates ok too.

 

the correct path should be on your DHCP. That is what mine is set to. You could use the x64 as well. The other thing is SCCM seems to want both x86 and x64 boot images available even if it isn't using one of them.

 

SCCM adds an smsboot folder with all the correct files, but boot does work as well. (and good point, you need to deploy both boot files!)

Edited May 8, 2012 by mrbios

[mbrunt]

finally managed to find my smspxe.log file after a while searching, im getting warning: match processor architecture boot image (0) found............which when you do a google it basically tells me to go to my data source tab and click "deploy this boot image from the pxe service point" which I did right at the beginning of setting sccm up, is there a way to clear the boot image from my service point and deploy it again by unticking the box and ticking it again or something???

 

also SMSBOOT, i thought thats where my boot images lived, whats the BOOT folder do? The boot folder was used when i used wds and mdt?

[mrbios]

finally managed to find my smspxe.log file after a while searching, im getting warning: match processor architecture boot image (0) found............which when you do a google it basically tells me to go to my data source tab and click "deploy this boot image from the pxe service point" which I did right at the beginning of setting sccm up, is there a way to clear the boot image from my service point and deploy it again by unticking the box and ticking it again or something???

 

also SMSBOOT, i thought thats where my boot images lived, whats the BOOT folder do? The boot folder was used when i used wds and mdt?

 

the files in smsboot (or boot) are just what the client PC uses to PXE boot and direct to the boot image file. (don't know exactly but that's the jist i think).

 

Have you tried using the x86 boot image instead? and have you made sure to configure both the x86 an x64 boot images in SCCM? (deploy them both to a distribution point and enable PXE)

 

Point dhcp to smsboot\x86\wdsnbp.com instead of x64. Also make sure you don't have WDS configured, it should have the service installed but not configured, as SCCM does all the settings for it.

[mbrunt]

just noticed this too, sure i wasnt getting that before...

[mrbios]

Out of interest what other options do you have set in DHCP?

[mbrunt]

I dont think its anything wrong with DHCP options as I had them set up in the past for WDS and everything worked fine. The only other DHCP options are some for our Nortel phones, our WINS server, DNS servers and DNS Domain name, and Router otherwise nothing.

 

I think its probably something to do with the two errors I've just posted, the one about Architecture and the one about no response from WDS.

[mrbios]

Ok fair enough, just checking

 

So returning to previous post, have you installed SCCM on top of a working WDS install? because as far as i'm aware SCCM requires WDS to be untouched with regards to configuration.

[Gatt]

In my experience, WDS needs a little bit of config to work with SCCM:

 

It needs to be configured as far as being able to create the :\RemoteInstall folder and the REMINST share

I also configured it to respond to known or unknown client requests (But dont require Admin approval)

And, if DHCP is on the same server then to configure that

 

Other than that I did nothing else, SCCM accepted this and I seen the SMSBOOT and SMSIMAGES folders created in the RemoteInstall folder

[mbrunt]

Ok a bit of news, I right clicked both boot images, unticked "Enable Command Support" clicked apply, let it do its thing and then ticked it again, let it do its thing and then deployed both images again....booting fine now :s totally strange! I can only presume something went wrong the first time I did this.

 

Thanks for all your help! I'm sure I'll be back!

[mbrunt]

one other thing, when I pressed F12 for network boot WINPE booted and asked me for a password, where abouts in SCCM can I change that password?

[mbrunt]

and for the record I have installed WDS but not configured it as I was told I didnt need to...

[Gatt]

Not sure in 2012, but its in the PXE service point role under SCCM 2007

 

Removing the PXE Service Point Password in SCCM 2007 - Gatt's Ramblings

[mrbios]

In my experience, WDS needs a little bit of config to work with SCCM:

 

It needs to be configured as far as being able to create the :\RemoteInstall folder and the REMINST share

I also configured it to respond to known or unknown client requests (But dont require Admin approval)

And, if DHCP is on the same server then to configure that

 

Other than that I did nothing else, SCCM accepted this and I seen the SMSBOOT and SMSIMAGES folders created in the RemoteInstall folder

 

I remember doing that with SCCM2007, but SCCM2012 configured everything for me and just required me to install the WDS role. (bar the DHCP configuration anyway, which i've never personally needed)

 

Sounds like it might not have properly distributed the boot image before? dunno, good to hear it's working though

[Gatt]

Sounds like your Boot Image hadn't benn processed properly

The F8 support is just a coincidence as it sounds like it just needed to be rebuilt and sent to the DP again...

[Gatt]

I remember doing that with SCCM2007, but SCCM2012 configured everything for me and just required me to install the WDS role. (bar the DHCP configuration anyway, which i've never personally needed)

 

Sounds like it might not have properly distributed the boot image before? dunno, good to hear it's working though

 

There are mixed reports about SCCM 2007 and WDS configuration - some say it needs to be, some say it doesn't

So I guess its a bit temperamental in 2007, so they may have resolved it in 2012, or it may suffer the same issues...

[mbrunt]

Sounds like your Boot Image hadn't benn processed properly

The F8 support is just a coincidence as it sounds like it just needed to be rebuilt and sent to the DP again...

 

That's what I thought, it was just the easiest box for me to untick and tick again lol :-)

 

Thanks!