PXE boot problems

[theoldgoat]

Hello,

 

Great forum, although I haven't been able to find the answer to my problem yet, although I'm sure it's here somewhere.

 

Whenever I try to pxeboot new clients I get an IP etc but move on to this error:

 

"Selected boot device failed.

 

Press any key to reboot."

 

I've done a SMSTrace on smspxe.log and whenever I attempt a network boot nothing is appended to the log which suggests that the server is not seeing the requests?

 

I currently have DHCP option 66 set to the SCCM server and option 67 set to reminst\smsboot\x64\pxeboot.com

 

I have tried this as wdsnbp.com instead, and also as x86.

 

Can somebody please help me troubleshoot this issue? Cheers

[theoldgoat]

Some more information that I think may be useful:

 

The SCCM server is virtual, the clients are physical.

IP helpers are in place.

 

The server is running SCCM 2007 R3.

[anyweb]

couple of things to check.

 

1. is dhcp running on the same box or elsewhere ?, i've seen issues with vmware using it's own dhcp server causing issues with OSD in a virtual env

2. is DNS working ? check with nslookup

3. are both boot images distributed to the distribution points ?

[theoldgoat]

Thanks anyweb.

 

1. DHCP is on the DC, so elsewhere. This is a production environment. Unfortunately the guy who configured it all has left and I've taken over from him. The infrastructure was configured for an old SMS server I think and as far as I know the only change that has been made was Options 66 and 67 in DHCP being changed. Would the IP helper need to be changed as well - it would have to point to the new PXE server wouldn't it - I will need to check with comms that this has been done.

 

2. I will check this.

 

3. This was something I was concerned about. The two standard boot images are present (x64 and x86) but there is also a secondary custom x64 boot image with added NIC support. Is it ok for this to be there or should I delete one of the x64 boot images? All three have been distributed to the DP....

[theoldgoat]

Some more information on further tests this morning:

 

When I select "Update Distribution Points" the x86 image updates with no problems, but if I try this for either of the x64 images I get these errors:

 

  Error: Boot image to update:
Microsoft Windows PE (x64)
  Error: Actions to perform:
Add ConfigMgr binaries
Enable Windows PE command line support
Add drivers
  Success: Drivers that will be included:
Intel(R) Display Audio
ST Micro Accelerometer
Intel(R) Management Engine Interface
Bluetooth Hands-free Audio
Bluetooth L2CAP Interface
Bluetooth Remote Control
Dell Wireless 375 Bluetooth Module
Intel(R) Centrino(R) Advanced-N 6230
Intel(R) 82579LM Gigabit Network Connection
O2Micro Integrated MMC/SD controller
O2Micro Integrated MS/MSPRO/xD Controller
Dell ControlVault
Intel(R) ESB2 SATA AHCI Controller
Intel(R) HD Graphics Family
Intel(R) 82579LM Gigabit Network Connection
Intel(R) Active Management Technology - SOL
Intel(R) ESB2 SATA AHCI Controller
Intel(R) HD Graphics Family
Intel(R) Management Engine Interface
Intel(R) ESB2 SATA AHCI Controller
3Com Dual Port 1000-SX PCI-X Server NIC
NVIDIA Quadro FX 5600
DELL PERC 5/E Adapter RAID Controller
3Com Dual Port 1000-SX PCI-X Server NIC
NVIDIA High Definition Audio

  Error: Failed to import the following drivers:
LSI Adapter, SAS 3000 series, 4-port with 1064 - Failed to inject a ConfigMgr driver into the mounted WIM file

  Error: The wizard detected the following problems when updating the boot image.
Failed to inject a ConfigMgr driver into the mounted WIM file
Failed to inject a ConfigMgr driver into the mounted WIM file
Failed to inject a ConfigMgr driver into the mounted WIM file
Failed to inject a ConfigMgr driver into the mounted WIM file
Failed to inject a ConfigMgr driver into the mounted WIM file
Failed to inject a ConfigMgr driver into the mounted WIM file
The ConfigMgr Provider reported an error.: ConfigMgr Error Object:
instance of SMS_ExtendedStatus
{
 Description = "Failed to insert OSD binaries into the WIM file";
 ErrorCode = 2152205056;
 File = "e:\\nts_sms_fre\\sms\\siteserver\\sdk_provider\\smsprov\\sspbootimagepackage.cpp";
 Line = 4262;
 ObjectInfo = "CSspBootImagePackage::PreRefreshPkgSrcHook";
 Operation = "ExecMethod";
 ParameterInfo = "SMS_BootImagePackage.PackageID=\"EDN00007\"";
 ProviderName = "WinMgmt";
 StatusCode = 2147749889;
};

 

Is there a problem with the LSI Adapter, SAS 3000 series, 4-port with 1064 driver with the x64 images

 

I have tried with a different PC this morning as well to see if I got a more meaningful error message from PXE boot and I got this:

 

PXE-T04 - Access Violation

PXE-E36 - Error receiving from TFTP server

PXE-M0F - Exiting Intel boot agent

 

Thanks

[theoldgoat]

There is no IP helper pointing to the PXE service point - because the clients are being built on a different VLAN this needs to be in place.

 

I just need to find the driver file now for the Dell T7500 that has this in it.

 

Cheers for the help!

[theoldgoat]

Meh still not working.

 

In the event log for WDS there is this:

 

Log Name: Application

Source: WDSIMGSRV

Date: 20/01/2012 13:39:59

Event ID: 258

Task Category: (1)

Level: Error

Keywords: Classic

User: N/A

Computer: UK-EDN-V-SCCM-1.Capricornenergy.com

Description:

The description for Event ID 258 from source WDSIMGSRV cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

0xC1030104

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

<System>

<Provider Name="WDSIMGSRV" />

<EventID Qualifiers="49414">258</EventID>

<Level>2</Level>

<Task>1</Task>

<Keywords>0x80000000000000</Keywords>

<TimeCreated SystemTime="2012-01-20T13:39:59.000000000Z" />

<EventRecordID>8908</EventRecordID>

<Channel>Application</Channel>

<Computer>UK-EDN-V-SCCM-1.Capricornenergy.com</Computer>

<Security />

</System>

<EventData>

<Data>0xC1030104</Data>

</EventData>

</Event>

 

Anybody know what could be causing this?

[drmike]

I know this is a year old, but if anyone reads this post, you really don't need most of the those drivers so I'm not surprised there were problems. You only need network drivers that your hardware absolutely cannot do without and possibly disk drivers. Drivers to see the disk and then the network. Since you're not going to boot with HD audio or bluetooth, you need to remove them. All they will do is slow your WinPE boot down and fatten the WIM file.

 

See this http://www.chrisnackers.com/category/webcast/ for more info.

 

Mike