Windows 10 ADK Timeline parity with SCCM Build Releases to Support 30 Month Fall Release Support Cycle
It would appear at a high level that adjustments were not made to coordinate support timelines across the architecture of components for SCCM, Example, while extending Windows 10 1709 Ent. support to 30 months, I would expect the ADK to be supported with the Configuration Manager release 1810, (1903, 1909, etc.) to maintain parity with bug fixes.
Thanks for your feedback.
For ADK support we always support N-1 i.e. current and previous version. This is the matrix we use for testing each release and forms this statement – https://docs.microsoft.com/en-us/configmgr/core/plan-design/configs/support-for-windows-10#windows-10-adk
Each ADK can be used to deploy current and earlier versions of Windows 10. Between releases (either SCCM or ADK) there’s no fundamental change with how we interface.
Can you elaborate some more on what your request is here, please?
Thanks and regards