Jump to content


  • 0
Smytty

Unable to get any machine to PXE Boot

Question

Hi folks. I have been having some on going issues with my SCCM setup. This is most likely due to my inexperience with SCCM.

 

So the major problem that I am having at this point is that I can not get any machine to PXE boot properly. If I use a boot disk I can get the machine to connect to the SCCM server and find the advertised sequence and install the OS that way but PXE just does not want to work.

 

Here is the background info on how I have my environment setup:

 

SCCM 2007 version 4.00.6487.2000 with R3 Installed on a 2K8 R2 Virtual Machine on an ESXi host

DHCP is NOT running on this server but the SCCM server is within the same subnet as the DHCP server

There is only 1 SCCM server as of right now (The Primary) so I can have everything up and working before adding other DP's

 

Ok now down the the root of the problem. I have spent the last several weeks reading this site as well as many others trying to diagnose my issues. I have tried with WDS not configured at all on the SCCM server as well as having it configured. Also I have tried with different DCHP options added to my DHCP server(Options 060, 066, 067). **(I have manually added option 060 onto the DHCP server as it was not there)

 

As of right now I have removed my PXE Role from my SCCM server, un-installed WDS. Re-installed WDS (but have NOT configured it at all), re-installed the PXE role in SCCM, seen that the install has been successful in the PXeSetup.log file

 

I have copied my x86 boot image to the SCCMSERVER\SMSPXEImages$ Distribution Share and ran "Update DP's".

 

On my DHCP server I have added option 066 with the IP of my SCCM server.

 

Ok booted my test machine and not even getting an IP when I PXE boot. I went back to my DHCP server and added option 067 to the Scope options and then I get an IP on the PXE Boot but now I get PXE-T04 and PXE-E36 errors. ( I have seen these errors before in my previous setups and attempts)

 

I apologize for the long rant(ish) post but this has consumed allot of my time and I have not made any progress. I have seen what SCCM can do and I want to get it up and working for our environment.

If anyone has any ideas or can see that I am doing something blatantly wrong please let me know

 

Thanks

A very frustrated but hopeful,

Shaun Smytaniuk

Share this post


Link to post
Share on other sites

3 answers to this question

Recommended Posts

  • 0

Hi there,

 

My WDS service is up and running and I do have my task sequence advertised to the computer I am trying to boot. I manually added the MAC address of the machine and put it into a collectiong which I then advertised the task sequence to. During some earlier testing to see if my task sequence was the problem I created a bootable CD was able to see my task sequence and start the OS deploy through that way.

Share this post


Link to post
Share on other sites

  • 0

Ok I made a mistake in my original post. My DHCP server is on a different subnet then my SCCM server. I have read that there are a couple ways of making it work this way.

 

One way I have seen is configuring DHCP options 066 with the IP or FQDN of my SCCM and option 067 with this path in "\\SCCMSERVER\REMINST\SMSBoot\x86\pxeboot.com"

 

The other way I saw was using IP Helpers on your switches to direct traffic.

 

I have configured the first way with options 066 and 067 but now I am getting TFTP errors PXE-E36: Access Violation and PXE-T04:Error Recived from TFTP Server

 

Shaun

Share this post


Link to post
Share on other sites

Join the conversation

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

Guest
Answer this question...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...


×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.