forums.wsusoffline.net

Da ich aktuell nicht dazu komme:
Könnte jemand von euch Tests mit Windows Server 2022 durchführen?
Da das System auf Build 20348 (und damit >= 20231 ist), weiß ich nicht, ob die Updates als reine CAB-Datei erscheinen oder ob auch hier eine Trickserei mit CAB+PSF erforderlich wird...

Für den Fall, dass es nur CABs sind, wäre es klasse, wenn jemand wsusou testen könnte (dazu muss der Versions-Check ein wenig modifiziert oder komplett rausgepatcht werden).

Viele Grüße

Ich muss korrigieren: Das neue Update-Format kam erst mit einem späteren Build (21382 laut abbodi1406).
Ich habe den master von wsusou einmal entsprechend angepasst.
Update-Filter habe ich noch keine, da ich dazu erst ein Update bräuchte, welches offiziell für Windows Server 2022 erschienen ist.

Viele Grüße

I have access to the retail version of 2022 if you need something tested. 20348.169 is the current version.
It contains the following patches: kb5004330, kb5005039, kb5005552.
The servicing stack version is 10.0.20348.169.

You can get the 180 day eval version here: https://www.microsoft.com/de-de/evalcen ... ows-server

Within the catalog, 2022 isn't a valid search key, but 21H2 is: https://www.catalog.update.microsoft.co ... -08%2021h2
The August rollup KB5005039 and .Net patches are there, so maybe you can make use of those?

Not sure if these can be uninstalled though - they definitely can't from Programs and Features. I expect not.

I believe that wsusscn2.cab does now contain server 2022 content. The standalone scan script works correctly using the August version.

Hope this helps.

Robert

I saw the updates preinstalled in the ISO an tried to find out the ProductId required to create a XSL for dynamically determining the updates. But yesterday the Catalog listed both updates only for the ProductId „Windows Insider Pre-Release“. That‘s a filter I don‘t want to use for a good reason.
(EDIT: I just rechecked and now and „kb5005039“ is now listed as update for „Microsoft Server operating system-21H2“.)
wsusscn2.cab (dated 2021-08–11) contains a reference to one of the updates and as soon as I know, which ProductId I have to use (EDIT: If it was „ kb5005039“, I can create the filter now.) I‘ll create a new commit adding support for „Windows Server 2022“ or „Microsoft Server operating system-21H2“.
But due to lack of time I‘ll need someone to test it.

Tell me the detail of what needs to be tested and I'll do my best to make it happen.
regards
Robert

As soon as new updates for Windows Server 2022 (and a commit adding support for it) are out, wsusou needs to be tested.
Means:
- the download has to work (get all the updates)
- the core installation has to work (servicing stack, static and dynamic updates)
- the additional stuff has to work (Edge Chromium, dotNet 5, c++, …)

This night I pushed two commits sorting /improving some internal stuff and the next step will be adding support for Server 2022.
The initial commit will just allow Server 2022 and add it to the list of supported products, specific adjustments will be done later…

The commit adding support for Windows Server 2022 is online.
Except for short test verifying, that the download works, nothing has been tested yet.

https://gitlab.com/wsusoffline/wsusoffline/-/commit/54c18bf8a6e421ae532ea027e89b0bb2c0705d1a