Re: Release Cadence Changes to Microsoft Configuration Manager
Any word on 2409?
Any word on 2409?
It’s always been challenging to automate patching, and distribute the schedules across the month because the months all start on different weekdays which causes the nth weekday of the month to vary a bit around patch Tuesday, with patch Tues always being the 2nd. For example, the month (Oct 2024), the Monday following patch Tues…
So, how is the 2409 release coming along?
DHCP option 60 is only required when DHCP and WDS are on the same server. It’s not needed in any other circumstance. If you only got it working by adding DHCP option 60, then there is something else wrong or misconfigured in the environment. A network trace might help reveal where the problem is.
To get it working I had to configure DHCP option 60 with the value “PXEClient” on the DHCP server. I’m using an IP helper to forward UDP 4011 to the Configuration Manager (with WDS) server which is located on another subnet.
Thanks for the update @Bala_Delli 👍
fixed PXEClient (UEFI ARM64) PXEClient:Arch:00011 https://www.iana.org/assignments/dhcpv6-parameters/dhcpv6-parameters.xhtml#processor-architecture
You need to use the WDS less ConfigMgr PXE responder.
im wondering how to add support for the new arm64 devices? using wds or wds less pxe from sccm…
We are fixing in 2409. All the X64 machines will work and DP or pull DP on Arm64 will not work and cannot be configured.