SCCM PXE not booting up

[nectormjr]

Let me know if you need any logs that you can check.

[Rocket Man]

Firstly have you created a new VM and tried PXE booting it?

You haven't made any changes in the DHCP options?

Have you tried removing the PXE service from the DP and reinstalling it?

 

I have never had to reinstall PXE/WDS so correct me if I am wrong when doing this procedure.

• If you uncheck all from the PXE tab on the DP properties and apply.
• Wait for some time.....open up the wds console(If it still exists after the last step) and make sure that there is a yellow exclamation mark on the server node of the console. If this is correct then manually remove the wds role via server management.
• Restart your server.......check the drive and if Remote Install folder exists then manually delete it.

 

Now this is the way I always set up PXE and have never had any problems.

 

I manually add the WDS role from server manager first on the site system DP. Do not configure it or do anything in relation to manually configuring it in any way. Restart the server. Now enable the PXE options again on the DP. This will configure WDS for you and should pre-populate the extra directories and extra files automatically as you already have the boot images configured to deploy from PXE server.

 

 

Give it a go and see what happens.

[hyodoh]

WHenever i've had that problem its either cuz of

 

1) Drivers in boot image that the boot image hates ( Take them out, redistribute and try again)

2) Boundary/Boundary Groups

3) Uncheck and recheck pxe option on DP

[Edenost]

Okay, firstly, the group with 2 unknown computers is fine, from what I understand, (which could be wrong, I'm sure anyweb will correct me if needed ), is required for the two boot images (x86 and x64).

Secondly, in the All Systems group, I would presume you have two clients, and the two "unknown" computers, correct?

 

So, in your VM, make sure the network card is "Legacy", other wise it won't boot.

Within SCCM, you need to "Import" the computers MAC address which you want to image, and give it a name (the name is partly important, as I've since found out, the name you give it during the import process can be used during the "Renaming" process of deploying the image.

 

So make a note of the MAC of the VM (shown in your Screen cap of it), click on "Devices", in the left part of the screen, then at the top, one of the options on the left is to import computers. Just add the MAC and computer name, then click through the rest until it's imported (takes less than 2 seconds). (You can add the device to another device group during the process, but that's up to you, as you don't really have many).

Once that is done, make sure your Task sequence is deployed to the group where this imported PC is (I hope that makes sence?).

 

By doing this, SCCM knows to look for a PC with that MAC address and allow it to PXE boot. The task sequence then takes over and will do what you tell it too, assuming that the data is all deployed and ready for use.

 

I hope I haven't missed anything out. I'm actually at home at the moment, and I usually post from work, as I can take screen shots of SCCM when posting.

I will double check it all tomorrow and update this post if needed (might do anyway just to make it clearer).

 

So, to finalise:

 

1. Make sure VM has "Legacy" Network Card

2. Make sure you have imported the MAC Address of VM in to SCCM

3. Make sure the Task Sequence is deployed to the group containing the imported PC

4. Make sure the OS media is deployed as well to the distribution point

 

Also, one last thing, if SCCM already has the PC in its inventory under Devices, delete it, then import it. It will show up as what ever name you give it, but it should say "No" under the "Client" colum or something like that. I can't remember off the top of my head right now . I have found that when booting a PC to PXE which is already online and managed by SCCM, it ignores it for some reason. Removing it and importing it via MAC and Name, seems to fix that for me.

When you import it, if you have deployed your Task Sequence to a specific group/Device Collection other than All Systems or something, make sure to add the imported PC to the group/Device Collection.

 

When you add the PC to the group/Device Collection, give it say 3-5 mins to update the group/Device Collection, even when forcing it to update the membership. Seems to take a while when I do it sometimes...but other times, it can be fine .

 

Anyway, sorry for rambling, I hope this helps. Let me know if you don't understand anything .

[Rocket Man]

 

2. Make sure you have imported the MAC Address of VM in to SCCM

 

Considering the DP is enabled for unknown computers then there is absolutely no need to import the computer info into SCCM....any unknown computer that SCCM has no info on should automatically boot to a DP that is enabled for unknown computer support!

 

Some organisations opt out of this configuration for security purposes and do have to use the import method but as mentioned if the DP is enabled for unknown computer support then no need duplicating work for yourself!!

 

 

nectormjr any update on this issue?

[nectormjr]

Hi Edenost/Rocket Man,

 

Thanks for your all help, due to my frustrations of enabling and disabling PXE on DP and boot images, I decided to backup all my application packages and then uninstall my SCCM using thirdparty software. After which, delete all the entry on System Management container on ADSI edit. Reboot my VM server, created and installed SCCM and do it from scratch again. To make the story short, I created and configured all the settings again and boom PXE work. I was able to boot the VM to my SCCM. Glad it works! I can now move on to my next chapter of reviewing on SCCM certification.

 

Yes, you don't need to register the MAC address on the device collections since DP is enabled to boot on unknown computers.

 

 

Again, thanks for all the help!