VLANs and SCCM

[lmrogers]

Good afternoon,

 

So I have just had VLANs setup on my network and it seems to have broken my SCCM. No clients are able to pick up the SCCM server when PXE booting and I'm getting no bootfile received error.

 

If anyone can point in the right direction on how to fix this that would be great.

 

Thanks,

[Steve21]

Do you have the helpers for each VLAN assigned in DHCP scope? e.g. Option 66 etc

 

Steve

[lmrogers]

I don't have option 66 configured in DHCP. If I configure that should it just be the server host name which SCCM is sat on?

[Steve21]

On the VLANs that the server isn't on, you need 66 to be the IP of the server, and 67 to be the bootfile

 

 

That's ours for example, but might want to check if that's same path for you as might be different etc depending on your version/setup (or x64 etc etc)

 

Steve

Edited August 27, 2017 by Steve21

[lmrogers]

Hi Steve,

 

Looks like that has worked like a charm! Thank you.

[Norphy]

Option 66 and 67 should only be set if the WDS server is located on the same installation of Windows as a DHCP server. What you need to do is set IP helpers on the switch that hosts the VLANs. The people who set up VLANs would have done this for you already for DHCP, you will need to ask them to do the same for your PXE enabled DPs as well.

[Steve21]

Option 66 and 67 should only be set if the WDS server is located on the same installation of Windows as a DHCP server. What you need to do is set IP helpers on the switch that hosts the VLANs. The people who set up VLANs would have done this for you already for DHCP, you will need to ask them to do the same for your PXE enabled DPs as well.

 

That's only the case for a flat network normally as you need to instruct the DC not to take over replies for 67 etc. There's no reason not to use 66/67 with VLANs as an alternative to switch settings. (Unless you're talking a huge huge network with load balancing PXE/DPs etc etc) Yes both work fine though, just means less configuration rather than modifying hundreds of switches depending on the setup

 

It's just a network boot referral:

 

You might want to consider a network boot referrals in the following scenarios:

To direct a client to download a NBP that is located on a different computer or network location. This may be especially helpful when using DHCP options 66 and 67, because the client is typically answered directly by the DHCP server and is redirected to the Windows Deployment Services server.

etc etc

 

But either way works fine

 

Steve

Edited August 27, 2017 by Steve21

[Arthur]

There's no reason not to use 66/67 with VLANs as an alternative to switch settings.

How do you deal with PXE booting BIOS and UEFI-based PCs since they require different boot files (x86\wdsnbp.com, x64\wdsnbp.com, x86\wdmgfw.efi or x64\wdmgfw.efi)? Do you use the method described here?

 

Setting up IP helpers was really easy on our HP ProCurve switches...

 

ProCurve# config
ProCurve(config)# vlan 10
ProCurve(vlan-10)# ip helper-address 192.168.0.10
ProCurve(vlan-10)# ip helper-address 192.168.0.15
ProCurve(vlan-10)# write mem

 

.10 = DHCP server and .15 = SCCM server.

[Steve21]

Not saying it's hard to do, just saying there's no real benefit for a "small network". To change an entire network setting via DHCP takes seconds, whether that's for testing or setting a new server up etc. That's before you consider some schools with LA networks etc can't actually modify core switches etc to setup the helpers therefore nulling that option for a quick change.

 

Not arguing that IP Helpers shouldn't be used, if you check MS sites it'll normally say it's not "recommended" to use the DHCP options, unless certain setups want things for NBPs, due to things like load balancing etc not working on them but I said that above is for bigger sites etc. Which then leads onto other things like multiple Layer3 routes for sites that need individual helpers per subnet rather than a single "option" overbranching.

 

In terms of the EFI/Leg "currently" we don't have split OSs on the site I did that pic from. I wouldn't bother with the hassle of the classes though unless I really had to. Even with the options if it's a large setup with lots of VLANs it's likely you'd have the same models/computers in a room e.g. one VLAN per IT suite. If it's fewer VLANs e.g. Computer/Wireless etc it's unlikely you'd need all the options on each VLAN. But that's digressing a bit as that's only the larger networks (As a bit of a more OT example, if you're using a VOIP setup that requests 66/150 as a DHCP option etc you'd need it hard set etc)

 

Steve

[lmrogers]

I have just changed and added an IP helped on my HP Procurve core switch and that seems to be working as well after removing the DHCP options. Thanks to you both