Updating to 20H2

[caffrey]

It should clean itself up after 30 days

[altecsole]

I can share the script if it is required by anyone.

 

Yes, please.

[techy32]

Create a powershell script in config Mgr (SCCM), see the picture attached

 

$dir = 'C:\packages'

mkdir $dir

$webClient = New-Object System.Net.WebClient

$url = 'https://go.microsoft.com/fwlink/?LinkID=799445'

$file = "$($dir)\Windows10Upgrade9252.exe"

$webClient.DownloadFile($url,$file)

Start-Process -FilePath $file -ArgumentList '/quietinstall /skipeula /auto upgrade /copylogs $dir'

[RLR]

This prompted me to check ADMX files. Looks like they released a version 2 of 20H2 ADMX a few days ago!

https://www.microsoft.com/en-us/download/details.aspx?id=103060

[Steve21]

Create a powershell script in config Mgr (SCCM), see the picture attached

 

$dir = 'C:\packages'

mkdir $dir

$webClient = New-Object System.Net.WebClient

$url = 'https://go.microsoft.com/fwlink/?LinkID=799445'

$file = "$($dir)\Windows10Upgrade9252.exe"

$webClient.DownloadFile($url,$file)

Start-Process -FilePath $file -ArgumentList '/quietinstall /skipeula /auto upgrade /copylogs $dir'

[ATTACH=CONFIG]61763[/ATTACH]

 

That's pretty cool idea using it via SCCM that way.

 

Don't suppose by any chance you have a 1909 copy of the update exe still?

 

Steve

[techy32]

That's pretty cool idea using it via SCCM that way.

 

Don't suppose by any chance you have a 1909 copy of the update exe still?

 

Steve

We upgraded PCs from 1903 and 1909 to 20H2. This script will upgrade PCs from any version (at least from 1903 and 1909). The good thing is that no user interaction required. Simply select the PCs and run the script from SCCM. It will upgrade in the background and restart the PC.

One thing to note that the PC should have 30 GB space available for Windows.old folder which will automatically be deleted after 10 days.

Edited May 11, 2021 by techy32

[Steve21]

We upgraded PCs from 1903 and 1909 to 20H2. This script will upgrade PCs from any version (at least from 1903 and 1909). The good thing is that no user interaction required. Simply select the PCs and run the script from SCCM. It will upgrade in the background and restart the PC.

One thing to note that the PC should have 30 GB space available for Windows.old folder which will automatically be deleted after 10 days.

 

Aye, it was more that we have some old old old laptops that the old IT company bodged majorly that I'd prefer not to jump to 20H2, so if they're on 1909 they're updated, but at least I know which ones I need to manually rebuild later, as then any 20H2 are clean as such.

 

I had an old version of the exe you use that says it'll do them to 2004, so it seems to be exe dependant to what version it upgrades too thus the wonder if you had any old ones lying around

 

Steve

[techy32]

Aye, it was more that we have some old old old laptops that the old IT company bodged majorly that I'd prefer not to jump to 20H2, so if they're on 1909 they're updated, but at least I know which ones I need to manually rebuild later, as then any 20H2 are clean as such.

 

I had an old version of the exe you use that says it'll do them to 2004, so it seems to be exe dependant to what version it upgrades too thus the wonder if you had any old ones lying around [emoji14]

 

Steve

Ohh Sorry got it... No we have just discovered this method so don't have any older exe... Google should find those if there are any...

[ITGuyNW]

Anyone got the 21H1 update yet?

[DJ-1701]

Anyone got the 21H1 update yet?

 

Installed on Home PC last night, installing on a couple of work PCs at the moment.

[supportman]

How to get the Windows 10 May 2021 Update

 

https://support.microsoft.com/en-us/windows/get-the-windows-10-may-2021-update-7d20e88c-0568-483a-37bc-c3885390d212

Edited May 19, 2021 by supportman

[3s-gtech]

Bear in mind that 21H1 reaches EOL well before 20H2 does, if you plan your deployments over a longer timeframe. The lifetime of H1 versions is pretty short! Edited May 19, 2021 by 3s-gtech

[ITGuyNW]

Bear in mind that 21H1 reaches OEL well before 20H2 does, if you plan your deployments over a longer timeframe. The lifetime of H1 versions is pretty short!

 

Yeah I was just looking into that. Only 18 months? Crazy. Might as well wait for 21H2

[Jamoire]

Yeah I was just looking into that. Only 18 months? Crazy. Might as well wait for 21H2

 

Worth bearing in mind that you have been able to update to the last few H2 updates via an enablement package which is a very quick update over SCCM/WSUS etc. So very quick and easy to move on to the longer support version when its available.

[kennysarmy]

Ah, you run it from within Windows. \\MDT-Sharename\Scripts\LiteTouch.vbs

 

Hi, seems to be working here too - but should it be running all the inject driver part again?

 

[caffrey]

Yes it does, well for me too - I think it's a step that can be disabled though

[kennysarmy]

Well it failed on my first test PC

 

[kennysarmy]

Thought the issue might be the answer file :/

 

But I can't even create the catalog to create a new one.

 

 

ADK update?

Edited May 25, 2021 by kennysarmy

[ITGuyNW]

I ran the 21H1 update from MDT (after converting the esd to a wim and importing it straight to MDT) through an upgrade task and it seems to have done the trick easily.

[kennysarmy]

I've updated to latest ADK.

 

I open my unattend answer file for the Upgrade Task Sequence to check if that's causing the failure in the task sequence on the client.

 

Pointed at the Deployment Share - then pick the image.wim so it can create the catalog and I still get this:

 

[kennysarmy]

In the task sequence (OS Info tab) for the in-place upgrade do you have anything specific in your unattend.xml?

[kennysarmy]

I've updated to latest ADK.

 

I open my unattend answer file for the Upgrade Task Sequence to check if that's causing the failure in the task sequence on the client.

 

Pointed at the Deployment Share - then pick the image.wim so it can create the catalog and I still get this:

 

[ATTACH=CONFIG]61935[/ATTACH]

 

The log file states:

 

13:25 : This application requires version 10.0.19041.1 of the Windows ADK.

Install this version to correct the problem

13:26 :

13:26 : Windows SIM was unable to generate a catalog. For troubleshooting assistance, see the topic: 'Windows System Image Manager Technical Reference' in the Windows ADK User's Guide.

13:26 :

13:26 : System.ComponentModel.Win32Exception (0x80004005): Unknown error (0xc1420127)

 

Server stack trace:

at Microsoft.ComponentStudio.ComponentPlatformInterface.WimImageInfo.PreCreateCatalog()

at Microsoft.ComponentStudio.ComponentPlatformInterface.OfflineImageInfo.CreateCatalog()

at Microsoft.ComponentStudio.ComponentPlatformInterface.CatalogCreatorImpl.CreateCatalog(OfflineImageInfo offlineImageInfo)

at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Object[]& outArgs)

at System.Runtime.Remoting.Messaging.StackBuilderSink.SyncProcessMessage(IMessage msg)

 

Exception rethrown at [0]:

at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)

at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)

at Microsoft.ComponentStudio.ComponentPlatformInterface.ICatalogCreator.CreateCatalog(OfflineImageInfo offlineImageInfo)

at Microsoft.ComponentStudio.CatalogGenerator.CreateCat(ProgressDialog pd, Object o)

 

Why does it require an older version of the ADK to update 1909 to 20H2 ?

[robyholmes]

Have you tried restarting your MDT server? I think I had this issue but it went away after a restart.

[kennysarmy]

Have you tried restarting your MDT server? I think I had this issue but it went away after a restart.

 

Tried a restart and was the same.

 

Ended up using a different workstation to edit the Unattend.xml - reason being we change the local Administrator account name to something else so I believe the original fails was due to it trying to logon with an account that did n't exist.

 

One I had everything updated on the Server I then coudn't update the deployment share, but had to install Windows ADK WinPE (adkwinpesetup.exe)

 

So MDT updated.

ADK updated.

ADK WinPE updated.

 

And just done a test and freshly imaged PC appears to update OK.

 

Will further test tomorrow.

[kennysarmy]

So back on this this morning and I seem to have "cracked" it.

 

Updated some files using this patch : https://support.microsoft.com/en-us/help/4564442/windows-10-deployments-fail-with-microsoft-deployment-toolkit

 

Still had errors post image reboot.

 

Found a very similar issue posted here : https://community.spiceworks.com/topic/1295139-mdt-2012-failure-5627?page=1

 

The problem was "The apply patches under the preinstall was set to apply all packages." - this was trying to install patches which we not applicable to this version of Windows 10!