[1803, au] Windows 1803 image upgrade

[nicholab]

What is the best way of update the 1703 image to 1803. Should I be using SCCM for the whole process or should I be using MDT to build the image? I have tried running the updated to 1803 after installing 1703 but this seems to leave the machine in deafultuser0?

[mavhc]

Depends on your clients and servers, SSDs vs HDDs? fast or slow network links? multicast? How many clients? All identical?

 

If HDDs, or you want multicast, or have 100s of computers to image at once, script the creation of a fat image.

 

If SSDs, not multicast, 10s of computers at once, just lightly script the wim to remove ads, and then deploy the software on top after it's installed, easier to update during the year then too

[nicholab]

What I mean is should I build and image in MDT to move into SCCM or just use the standard OS and put that down on the machines? I currently put all apps on with SCCM during deployment or afterwards.

[Arthur]

What I mean is should I build and image in MDT to move into SCCM or just use the standard OS and put that down on the machines?

Since it's not possible to use a captured WIM in a Windows 10 in-place upgrade task sequence that makes the decision much easier.

 

If your current Windows 10 v1703 PCs have the .NET Framework 3.5 installed you will probably want to integrate it into the install.wim to avoid the issue detailed below when upgrading to v1803.

 

https://miketerrill.net/2018/06/23/optimizing-win10-os-upgrade-wim-sizes

 

I have read some other blogs recently that follow a very similar procedure as below, but they all are missing one critical step – adding in .NET. Now you are wondering ‘why add .NET?’. The ultimate goal is to NOT have to apply the CU after the OS Upgrade. If you upgrade a system running 1607 that has .NET installed with a 1709 WIM with the latest CU but without .NET, guess what happens? On the first scan the system will want to download the latest CU and apply it turning our 60 – 120 minute upgrade into a 120 – 240 minute upgrade. Props to my colleague Jeff Carreon for discovering this last summer (2017). So we have been adding .NET as a base standard to all of our WIMs since then to prevent this from happening.

[nicholab]

I got two thinks going on I need to in place upgrade some machines and I need to freshly image some others. Not sure if is easier to image then upgrade.