SCCM. Do I need to update the ADK?

[Gongalong]

Hi folks,

 

I'm currently on the Summer rebuild and findind that things are a bit more glitchy than last year e.g. some machines failing to PXE boot. I spotted mention that the ADK on the SCCM server should be updated to keep step with the version of Win 10 being deployed https://www.systemcenterdudes.com/how-to-update-windows-adk-on-a-sccm-server/#comments

 

Just double checking that's correct still? I'm using SCCM v1902.

 

This makes me wonder if there are other things that need to be manually updated on the SCCM server?

 

Thanks

[Arthur]

Just double checking that's correct still? I'm using SCCM v1902.

That's correct. For SCCM v1902 you would need to install the 1809 or 1903 ADK + Windows PE. The latter would be best if you are deploying Windows 10 v1903.

 

Also, if you update the ADK and Windows PE prior to updating SCCM, the SCCM installer will then update your boot image(s) as part of the upgrade process.

 

https://docs.microsoft.com/en-us/sccm/core/plan-design/configs/support-for-windows-10#windows-10-adk

 

Edited August 6, 2019 by Arthur

[Gongalong]

... you would need to install the 1809 or 1903 ADK + Windows PE....

 

Is the latter bit the "Windows PE add-on"? Just checking I need to download and install both bits https://docs.microsoft.com/en-us/windows-hardware/get-started/adk-install

 

Also, if you update the ADK and Windows PE prior to updating SCCM, the SCCM installer will then update your boot image(s) as part of the upgrade process.

 

I'm already on SCCM 1902, so do I need to follow the process here to update the boot images? https://www.systemcenterdudes.com/how-to-update-windows-adk-1809-on-a-sccm-server/

[Gongalong]

Ah just noticed this guide, which looks to be more comprehensive https://www.prajwaldesai.com/update-windows-adk-sccm-server/

[Arthur]

Ah just noticed this guide, which looks to be more comprehensive https://www.prajwaldesai.com/update-windows-adk-sccm-server/

Yeah. That's a much better guide.

 

I follow the same process when updating the ADK/WinPE and SCCM.

[Gongalong]

Hmm, well I seem to have made things worse. Now when I PXE boot the latest classroom of machines it starts Win PE for a minute or two, then reboots back to the previously installed OS. Googling suggests this is lack of NIC driver, but this particular NIC (Intel 82579) on the machines that imaged successfully yesterday seem to use a 2018 Microsoft driver. Anyway, I've downloaded the ProWin64 drivers from Intel and added the Gigabit section of drivers to the x64 image, and will leave it to try again overnight.

 

Is there a recommended approach to troubleshoot why PE is rebooting? I've seen a suggestion of enabling F8 in the boot image to check if it gets a network driver correctly...

[free780]

It should still boot into WINPE even if there is not a network driver. Though I haven't had to inject a network driver in a long time the built in drivers seem to work for OSD. I'd check SMSPXE. Log file. Are you booting UEFI or Bios? Do press F12 or Enter to trigger the TFTP download. There was a Windows Update that impacted PXE using WDS. If you don't need multicast you can now use PXE boot without WDS when using SCCM.

 

Also make sure you have distributed the x86 and x64 boot images.

[Gongalong]

It should still boot into WINPE even if there is not a network driver.

The good news is this morning that it's working again - I seem to be able to PXE boot and also deploy via the Windows CM client. Perhaps there were still things sorting themselves out, although I did a server reboot, and another reboot this morning.

 

Thanks all for the help. I've got a whole mix of desktops and laptops of various vintages that need to be reinstalled in the next 2 and a bit weeks, so any interruption to that is stressful!