As far as I am aware, there is no such capability at present, since this would require a complete re-write of how it works at present.
If you don't want to use multicast on your clients until you've resolved your issue, you could - rather than killing it off on the switch level - just disable the client-side targeted multicast service on your Windows clients...?
That would be easier, and won't kill off your OSD.
- Paul Hoffmann
LANDesk EMEA Technical Lead
1 of 1 people found this helpful
It is possible but not an intended feature.
- On the PXE Rep, go to the PXEConfig.exe utility and run it.
- Right click on the Boot Server and choose Configure Boot Server.
- Click on the MTFTP Options item and uncheck the Enable Multicase Transmit option.
- Restart the LANDesk PXE services.
This setting is also a registry key:
1 = Enabled
0 = Disabled
So if you want you could create a TRANSFORM file doing similar steps as document here:
Be careful because our PXE Representative Scripts have changed to use REMCOPY, so this document is a little outdated, but the idea is the same.
Because we use the old Intel PXE (which I hear rumors that LANDesk guys actually wrote while LANDesk was part of Intel), you can make configuration changes using that. Be we aren't maintaining the PXE interface configuraiton utility and have no intention that customers would make changes with that.
Thank you, I'll try the registry key change method. Will let you know if it doesn't work for us. Thanks again.
Well, it seems to work; thank you for your expertise! We no longer experience the PXE-E35 error and Multicast is still turned off. One last question; are there ramifications by leaving multicast disabled? Will we lose any OSD functionality?
I have never seen a problem leaving MTFTP turned off. TFTP works fine. In fact MTFTP is only used to download a couple small files and then TFTP kicks in for the big large WinPE image anyway. So the majority of the work has always been done by our TFTP server.
MTFTP or TFTP for the little files, it really doesn't matter.
In fact, no one here at LANDesk has ever been able to explain why we default to MTFTP over TFTP. So far, to me it seems to be just as stable to not use MTFTP.