Skip to content

PXE boot

Featured Replies

Hi,

 

I need to setup PXE boot on my vlan for SCCM 2012.

We have setup the IP Helper to point to the IP address of the SCCM Site/DP.

Where is the file located which I will need for DHCP to give out to the clients to boot from?

I'm new to PXE booting in general so I'm a little confused about all this.

 

Here is the location of the file that I'm currently having it boot to

\\SCCM\SMS_STK\osd\boot\x64\boot.wim

Acutally the other admin did say that when he sets it up he wont be needing the unc path, just the filename of the boot file.

 

I've gone through and enabled PXE boot in SCCM.

Currently when my machine tries to boot it gets the following error.

 

PXE-T04: Access Violation

PXE-E36: Error received from TFTP server

PXE-M0F: Exiting PXE ROM

post-11630-0-23554800-1319663225_thumb.png

  • Author

I uninstalled WDS, removed the PXE boot check box. Restarted my server.

Installed WDS (didnt configure it), enabled PXE boot in the DP.

Went through SCCM guides 6 ,7 and 8 again.

When I boot my test VM client I get the following error.

My clients are on separate vlan then my SCCM server, so I have IP Helper enabled and dhcp handing out the boot file.

I think at this point this is my problem.

What boot file should I be telling DHCP to hand out to my clients?

post-11630-0-59796600-1319825597_thumb.png

  • 6 months later...

Johan Arwidmark affirms my approach to configuring WDS from within Server Manager as opposed to leaving it unconfigured as so many would advocate; more specifically designating where to install the remoteinstall folder and whether accept known and unknown computers.

 

I had issues with SCCM 2012 OSD/WDS/PXE as described above as I was a little trigger happy instead of troubleshooting Boot Image distribution. What I ended up doing to get it to work was:

  1. Ensuring the SCCM Admin account I'm logging in with has domain admin rights (This is important for WDS reinstall)
  2. Backup or rename folder x:\remoteinstall or whichever drive it is located.
  3. Uninstall WDS service
  4. Remove Distribution Point role from the respective PXE server
  5. Reboot
  6. Reinstall WDS
  7. Configure WDS in Server Manager (include destination of remoteinstall folder, accept PXE requests from known and/or unknown computers, and uncheck add image)
  8. Add Distribution Role back to the site server and configure for PXE
  9. Redistribute all required software back to this DP.
  10. Make sure you WinPE boot disks (both x86, and x64 configured for PXE within their properties tab under sources)
  11. Distribute both Boot disk to the distribution/pxe point.
  12. Make sure the remoteinstall folder has smsboot (option 67 of DHCP will point to smsboot\x86\wdsnbp.com so make sure that file is there) and other sms related folders that are automatically re-created

If you do receive abortpxe.com after it's another series of troubleshooting steps but not as severe as this one.

 

Jeff

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.