Resolved clients not connecting to SCCM through PXE on a VM

Oh man! Ad-blocking software has been detected! :'(

This website is run by the community, for the community... and it needs advertisements in order to keep running. Blocking our ads means your killing our stats!
Please disable your ad-block, or become a premium member to hide all advertisements and this notice.

I am having an issue where no matter what I do, my vm client wont connect to SCCM through PXE. The weird part is that I can connect to WDS through PXE.

I've added the PXE service port on SCCM, I've also setup the vm drivers in SCCM...

Any ideas what it could be? let me know if you need more info.

Thanks.

 

Oh man! Ad-blocking software has been detected! :'(

This website is run by the community, for the community... and it needs advertisements in order to keep running. Blocking our ads means your killing our stats!
Please disable your ad-block, or become a premium member to hide all advertisements and this notice.

A couple of ideads to try

I am about to go to bed because I am v drunk. HAve you made sure traffic is allowed both ways when setting fw settings and port sttings for SCCM,

Can you send and receive from main router? would say loopback will test it.

 

Yeah that all seems to be good since I can connect to WDS...

I got further now actually... now I can connect to the server using PSP (PXE Service Port) from SCCM but I get an error tftp download: smsboot\x64\abortpxe.com

 

PSP is actually the PXE Service Point.

Now a couple of questions. Is the VM a VM Workstation, Server or ESX Guest or is it Hyper-V. Secondly if it's Hyper-V did you use the legacy adapter?

Next have you configured ports 66 and 67 on the DHCP scope? Port 66 should be set to the PXE Service Point server (FQDN), and port 67 should be set to \SMSBoot\x86\wdsnbp.com.

You may also just want to add the SLP (Server Locator Point) role to the Config Manager box.

Finally have a read of the PSP logs and see what it says there.

 

So it's all figured out!

1. I ended up removing the PXE Service point and recreating it with the option of enable unknown computer support.

2. When I tried to get my client to connect to PXE I was getting an error that sated no Advertisements were available on the PXE service point. I then recreated my Task Sequence and advertised it to the collection I created.

3. Added the Computer association using the MAC address and UUID. Although I know one or the other would work too.

4. Booted up with the client again and all is well, connected and now preparing the workstation.

I've attached SCCM at work ...

I must of spent practically the whole weekend figuring how to do this and learned quite a bit. After all I will need to implement this at work so I better know what I am doing!


Thanks for the help guys!

 

glad you sorted it.

 

For sure! This thing is a monster! but if you get it working right it's a very interesting application.