
In the next step (Choose Classifications), you can select the desired classification type.
You can then select which types of updates you want to provide via WSUS, and you can also provide upgrades for subsequent versions of Windows (e.g., upgrade to Windows 10 v22H2, v21H2, v21H1, etc.).

To limit the amount of data downloaded (including for storing updates), we have chosen to download only the updates (Windows and Windows Server) that improve the security of our servers and client workstations.
To do this, select these updates:

For synchronization from the "Microsoft Update" server, you can choose to initiate the synchronization manually or automatically.
In our case, since this is a lab environment, we selected "Synchronize manually".

To have your WSUS server directly download the complete list of updates you want to access, check the "Begin initial synchronization" box and click Next.
Warning : this initial synchronization may take more than an hour depending on your server's performance, the products and other options you have selected, and your internet connection.
Note: in our case, you can see that this synchronization took 2 hours (and we have fiber optic internet, which is very fast).

Next, click Finish.

The "Update services" console appears.

By selecting your WSUS server (in the left column), you will be able to see the status of the initial synchronization that was started automatically (if you checked the "Begin initial synchronization" box).

The status of this synchronization performed in the background by WSUS is also visible in the "Synchronizations" section.

If synchronization has not started, you can start it by right-clicking "Start Synchronization" on this "Synchronizations" section.

In the "Updates" section, you will be able to see the number of updates downloaded, installed, ... by update category.

Please wait while your WSUS server synchronizes from the "Microsoft Update" server.

Once the synchronization is complete, the result will be "Succeeded".
As you can see below, in our case, this synchronization took approximately 2 hours and retrieved a list of 1354 updates.

Now, in the "Updates" section, you can see:

If you open Windows File Explorer, you'll notice that no update files have been downloaded (despite the very long synchronization time).
Indeed, Windows Server 2022 still indicates that there are 499 GB of free space remaining on our 499 GB "WSUS data (D:)" drive.

The folder "D:\WSUS\UpdateServicesPackages" is still empty.

The "WsusContent" folder still only contains the empty file "anonymousCheckFile.txt".

In the "Updates" section of this WSUS console, you can see a preview of:
You can also see the overall status of these updates:

To view the updates referenced on your WSUS server, go to the "Updates -> All Updates" section.
By default, you will see that the list is empty, but Windows Server indicates that 0 out of more than 1000 updates are displayed.

To see them all, select the "Any" status, then click "Refresh".

Now, the complete list of updates for the products and classifications selected previously (in the initial setup wizard) is displayed.
As you can see, in our case, we can therefore see numerous updates for:



In the "Computers -> All computers" section, you can see all the servers and computers that have already contacted your WSUS server at least once.
For now, the list is empty because you will need to provide them with your WSUS server address using Group Policy Objects (GPOs), which you will see later.

In the "Downstream Servers" section, you can see all the WSUS servers that depend on this master WSUS server.
By default, there are none. However, in a large enterprise or multinational corporation, you might see replica or standalone servers that depend on this master WSUS server.

As you have already seen, in the "Synchronizations" section, you will be able to see the progress and status of the synchronizations performed by your WSUS server.

In the "Reports" section, you can generate reports on updates, as well as on computers updated via your WSUS server and WSUS server synchronizations.
Note: to generate these reports, you will need the "Microsoft Report Viewer 2012 Runtime" component (which will be offered for download automatically by WSUS). If needed, the file to download is "ReportViewer.msi".
This component itself requires the other component, "Microsoft System CLR Types for SQL Server 2012", available on the "Microsoft® SQL Server® 2012 SP4 Feature Pack" page of the Microsoft website. There, you will need to download the "SQLSysClrTypes.msi" file, which is 2.40 MB in size (not the 2.10 MB version for the x86 version).
Windows Server 2022 is necessarily 64-bit (x64), so install the x64 version (the 2.30 MB file) and not the x86 version (the 2 MB file).

Finally, in the "Options" section, you will be able to:
Source : [DOC] WSUS30SP2DeployGuide.doc - Download Center - Microsoft (page 13 for "Reporting Rollup").

Pinned content
Contact
® InformatiWeb-Pro.net - InformatiWeb.net 2008-2022 - © Lionel Eppe - All rights reserved.
Total or partial reproduction of this site is prohibited and constitutes an infringement punishable by articles L.335-2 and following of the intellectual property Code.
No comment