[SSCM] Problem with PXE booting, new server.

[Operation_L]

Hi everyone,

 

I have a small problem with the boot of new windows 10 system image from new SCCM 1910

In our environment we have old sccm 2007 with DHPC, becouse it is used all the time,

so I decided to create a new server with SCCM 1910, but without DHCP, and now my problem appears: how can I boot dhcp scope for the new server which I created,

I tried to add options 66 and 67 and give the ip address and boot name there but it does not help in the SMSPXE logs: TFTP: 10.1.7.131 cannot open path to bootfile and on the computer monitor: TFTP: PXE-T00: Failed to open file. PXE-E36: Error received form TFTP server

 

 

[Davit2005]

I don't think you need 66 or 67 unless SCCM/PXE server is on same server as DHCP server, could be wrong.

 

Have you different vlans for clients at your site?

[Operation_L]

Ok I resolved it was ip helper for vlans on switches but now I have aborted but a small step forward

 

This is log from SMSPXE.log:

 

that's where the problem is because the new sccm is not where dhcp

 

 

 

[mavhc]

What IPs are you currently using for what?

[Davit2005]

Ok I resolved it was ip helper for vlans on switches but now I have aborted but a small step forward

 

This is log from SMSPXE.log:

[ATTACH=CONFIG]57018[/ATTACH]

 

that's where the problem is because the new sccm is not where dhcp

 

 

 

 

You should be able to just add the IP helper address to the vlan on the core switch where the clients are located, you will probably have an existing ip helper for your dhcp server.

 

Having both and even a netboot server IP address should not cause issues, the clients are intelligent enough to work out what they need

Edited March 4, 2020 by Davit2005

[Operation_L]

ipv4

[Operation_L]

You should be able to just add the IP helper address to the vlan on the core switch where the clients are located, you will probably have an existing ip helper for your dhcp server.

 

Having both and even a netboot server IP address should not cause issues, the clients are intelligent enough to work out what they need

 

 

Yea I solved it, adding ip helper-address for vlan, but now I have another problem, probably with image windows 10 or this: There are NO Task Sequence deployments for this client machine. Aborting the request.

Edited March 4, 2020 by Operation_L