Windows Update Collection

A Windows Update Collection is a compilation of various updates consisting of selected products and classifications. The updates are stored dynamically and can be distributed via the [[containers>>doc:ACMP.68.ACMP-Solutions.Client-Management.Container.WebHome]], used to prepare new clients (via [[rollout>>doc:ACMP.68.ACMP-Solutions.OS Deployment.Rollout Templates.WebHome]]) and used during [[job execution>>doc:ACMP.68.ACMP-Solutions.Desktop Automation.Client Commands.Jobs ausführen.WebHome]] (collection is pushed). This allows you to perform regularly scheduled installations of Windows updates in a targeted manner. The log entry for the respective Windows Update Collection can be used to check the result.

4

5

You can create as many Windows Update Collections as you like, allowing you to control the distribution of updates individually. Different reboot options can be assigned to each collection, and it is also possible to manually link individual updates to an update collection.

6

7

[[Windows Update Collection overview>>image:68_CAWUM_Windows Update Collection Übersicht_1485.png||alt="67_CAWUM_Windows Update Collection Übersicht_1485.png"]]

8

9

= Managing Windows Update Collections =

10

11

The ribbon bar allows you to add ([[image:1745390046026-149.png]]), edit ([[image:1745390046027-106.png]]) or delete ([[image:1745390046027-972.png]]) Windows Update Collections. You can also duplicate existing collections ([[image:1745390046028-877.png]]) to store already compiled update collections in another folder or to customize them if necessary.

12

13

You can also easily move existing Windows Update Collections to other folders using the drag-and-drop function. If you use multiple collections, we recommend storing the collections you have created in folders and naming them according to the relevant areas (e.g. //Update Collection – Windows 11 Upgrades//). Folder management is identical here to all other areas of the ACMP Console; a clear structure in the organisation and naming of folders will support you in your daily work with Windows Update Collections.

14

15

The Windows Update Collections workspace is divided into two parts: on the left-hand side, you will find a list of already created collections as well as a search bar where you can search for specific items. The collections are sorted alphabetically in the folder structure. On the right-hand side is the detailed view of the respective open entry. Here you can choose between the areas //General fnformation//, //Filters//, and //Updates// to read the information you need.

16

17

18

We recommend that you pack the operating system upgrades into individual update collections. This gives you better control over when feature upgrades or in-place upgrades are performed. When linking the collection to a container, we also recommend that you offer the user a job delay so that they can help determine the timing of the upgrade.

19

20

21

== Add Windows Update Collection ==

22

23

To create a new Windows Update Collection, click //Add //[[image:1745390057699-607.png]] in the ribbon bar. EA multi-page wizard will open to guide you through the individual steps. On the first page (//General//), enter a name for the collection and an optional description. Check that the output directory is correct or customize it ([[image:1745390057699-386.png]]) and select the correct one. Set the reboot options in the lower section. Here you can choose between the following options:

24

25

* Do not restart, but inform the logged-in user that a restart is required.

26

* Do not restart and do not notify the logged-in user that a restart is required.

27

* Restart the computer if necessary.

28

29

30

With the first option ("Do not restart, but inform the logged-in user that a restart is required"), the user on the client is displayed a restart dialogue box, which you can customize to match your corporate identity. Read [[here>>doc:ACMP.68.ACMP-Solutions.Patch Management.Windows Update Management.Konfigurationsmöglichkeiten im Windows Update Management.WebHome||anchor="HWindowsUpdateManagementCIAnpassungen28Neustart-Dialog29"]] to find out how to make these changes.

31

32

33

[[Add a new Windows Update Collection (General)>>image:67_CAWUM_Windows Update Collection hinzufügen Allgemein_832.png]]

34

35

On the next page, define a filter that includes the products and classifications that should apply to this update collection. Only the products and classifications that you previously selected using the First Steps Wizard or subsequently in the settings are displayed here. In other words, you can only assign products and classifications to a collection that you have obtained as metadata. In this example, a collection is to be created for a Windows 11 upgrade, so only the product //Windows 11// is selected in the upper part and only //Upgrades// under the classifications.

36

37

38

**Tip**: For a better overview, you can tick the //Display selected entries only// checkbox under the products.

39

40

41

Continue and click //Next >//.

42

43

[[Add Windows Update Collection (filter)>>image:67_CAWUM_Windows Update Collection hinzufügen Filter_832.png]]

44

45

Under //Update Links//, you can statically link selected updates to this collection. To do this, click on [[image:1745390129619-868.png]]// Add //and the Windows Updates element selection will open. In this view, the available updates are displayed in the same way as in the //Updates// tab (including detailed view). To store an update statically, select the desired number and mark the entries. To remove all entries, you can select the //deselect all// button below the detailed view. Otherwise, click //OK// once you have checked all the required updates.

46

47

[[Selecting Windows Updates items for static linking>>image:67_CAWUM_Windows Update Collection hinzufügen Elementauswahl_1026.png]]

48

49

You will now be brought back to the wizard page where the selected update was stored.

50

51

[[Link updates statically to a collection>>image:67_CAWUM_Windows Update Collection hinzufügen Update Links_832.png]]

52

53

If you wish to remove a static link, select the relevant update and click on [[image:1745390173414-325.png]] Remove. To exit the wizard, click on //Finish//. The newly created Windows Update Collection will now be displayed in the overview.

54

55

56

== Edit, delete or duplicate Windows Update Collections ==

57

58

In addition to creating a new Windows Update Collection, you can also work with existing collections. All actions can be started either via the context menu or from the ribbon bar. To do this, click on the corresponding button for the action and follow the continuing instructions.

59

60

To edit a Windows Update Collection, open it with a double-click or select the entry in the list and navigate to the //Edit //button ([[image:1745390182984-680.png]]). Change or add the desired information or customize the product selector or classification retrospectively, for example, by adding or deselecting items. You can also use this option to select a different restart option if the conditions for the selected update collection have changed. Confirm your changes with the Save button.

61

62

If you want to delete a collection, select the corresponding entry, click //Delete //([[image:1745390182984-300.png]]) and confirm the process.

63

64

To duplicate an existing collection, select the desired entry from the list and click on //Duplicate //([[image:1745390182984-426.png]]) via the ribbon bar or the context menu. Change all relevant information and assign a new name to the copied Windows Update Collection. Confirm your changes here as well with the //Save //button.

Wiki source code of Windows Update Collection

Navigation

author	version	line-number	content
		1	{{aagon.floatingbox/}}
		2
		3	A Windows Update Collection is a compilation of various updates consisting of selected products and classifications. The updates are stored dynamically and can be distributed via the [[containers>>doc:ACMP.68.ACMP-Solutions.Client-Management.Container.WebHome]], used to prepare new clients (via [[rollout>>doc:ACMP.68.ACMP-Solutions.OS Deployment.Rollout Templates.WebHome]]) and used during [[job execution>>doc:ACMP.68.ACMP-Solutions.Desktop Automation.Client Commands.Jobs ausführen.WebHome]] (collection is pushed). This allows you to perform regularly scheduled installations of Windows updates in a targeted manner. The log entry for the respective Windows Update Collection can be used to check the result.
		4
		5	You can create as many Windows Update Collections as you like, allowing you to control the distribution of updates individually. Different reboot options can be assigned to each collection, and it is also possible to manually link individual updates to an update collection.
		6
		7	[[Windows Update Collection overview>>image:68_CAWUM_Windows Update Collection Übersicht_1485.png\|\|alt="67_CAWUM_Windows Update Collection Übersicht_1485.png"]]
		8
		9	= Managing Windows Update Collections =
		10
		11	The ribbon bar allows you to add ([[image:1745390046026-149.png]]), edit ([[image:1745390046027-106.png]]) or delete ([[image:1745390046027-972.png]]) Windows Update Collections. You can also duplicate existing collections ([[image:1745390046028-877.png]]) to store already compiled update collections in another folder or to customize them if necessary.
		12
		13	You can also easily move existing Windows Update Collections to other folders using the drag-and-drop function. If you use multiple collections, we recommend storing the collections you have created in folders and naming them according to the relevant areas (e.g. //Update Collection – Windows 11 Upgrades//). Folder management is identical here to all other areas of the ACMP Console; a clear structure in the organisation and naming of folders will support you in your daily work with Windows Update Collections.
		14
		15	The Windows Update Collections workspace is divided into two parts: on the left-hand side, you will find a list of already created collections as well as a search bar where you can search for specific items. The collections are sorted alphabetically in the folder structure. On the right-hand side is the detailed view of the respective open entry. Here you can choose between the areas //General fnformation//, //Filters//, and //Updates// to read the information you need.
		16
		17	{{aagon.infobox}}
		18	We recommend that you pack the operating system upgrades into individual update collections. This gives you better control over when feature upgrades or in-place upgrades are performed. When linking the collection to a container, we also recommend that you offer the user a job delay so that they can help determine the timing of the upgrade.
		19	{{/aagon.infobox}}
		20
		21	== Add Windows Update Collection ==
		22
		23	To create a new Windows Update Collection, click //Add //[[image:1745390057699-607.png]] in the ribbon bar. EA multi-page wizard will open to guide you through the individual steps. On the first page (//General//), enter a name for the collection and an optional description. Check that the output directory is correct or customize it ([[image:1745390057699-386.png]]) and select the correct one. Set the reboot options in the lower section. Here you can choose between the following options:
		24
		25	* Do not restart, but inform the logged-in user that a restart is required.
		26	* Do not restart and do not notify the logged-in user that a restart is required.
		27	* Restart the computer if necessary.
		28
		29	{{aagon.infobox}}
		30	With the first option ("Do not restart, but inform the logged-in user that a restart is required"), the user on the client is displayed a restart dialogue box, which you can customize to match your corporate identity. Read [[here>>doc:ACMP.68.ACMP-Solutions.Patch Management.Windows Update Management.Konfigurationsmöglichkeiten im Windows Update Management.WebHome\|\|anchor="HWindowsUpdateManagementCIAnpassungen28Neustart-Dialog29"]] to find out how to make these changes.
		31	{{/aagon.infobox}}
		32
		33	[[Add a new Windows Update Collection (General)>>image:67_CAWUM_Windows Update Collection hinzufügen Allgemein_832.png]]
		34
		35	On the next page, define a filter that includes the products and classifications that should apply to this update collection. Only the products and classifications that you previously selected using the First Steps Wizard or subsequently in the settings are displayed here. In other words, you can only assign products and classifications to a collection that you have obtained as metadata. In this example, a collection is to be created for a Windows 11 upgrade, so only the product //Windows 11// is selected in the upper part and only //Upgrades// under the classifications.
		36
		37	{{box}}
		38	Tip: For a better overview, you can tick the //Display selected entries only// checkbox under the products.
		39	{{/box}}
		40
		41	Continue and click //Next >//.
		42
		43	[[Add Windows Update Collection (filter)>>image:67_CAWUM_Windows Update Collection hinzufügen Filter_832.png]]
		44
		45	Under //Update Links//, you can statically link selected updates to this collection. To do this, click on [[image:1745390129619-868.png]]// Add //and the Windows Updates element selection will open. In this view, the available updates are displayed in the same way as in the //Updates// tab (including detailed view). To store an update statically, select the desired number and mark the entries. To remove all entries, you can select the //deselect all// button below the detailed view. Otherwise, click //OK// once you have checked all the required updates.
		46
		47	[[Selecting Windows Updates items for static linking>>image:67_CAWUM_Windows Update Collection hinzufügen Elementauswahl_1026.png]]
		48
		49	You will now be brought back to the wizard page where the selected update was stored.
		50
		51	[[Link updates statically to a collection>>image:67_CAWUM_Windows Update Collection hinzufügen Update Links_832.png]]
		52
		53	If you wish to remove a static link, select the relevant update and click on [[image:1745390173414-325.png]] Remove. To exit the wizard, click on //Finish//. The newly created Windows Update Collection will now be displayed in the overview.
		54
		55
		56	== Edit, delete or duplicate Windows Update Collections ==
		57
		58	In addition to creating a new Windows Update Collection, you can also work with existing collections. All actions can be started either via the context menu or from the ribbon bar. To do this, click on the corresponding button for the action and follow the continuing instructions.
		59
		60	To edit a Windows Update Collection, open it with a double-click or select the entry in the list and navigate to the //Edit //button ([[image:1745390182984-680.png]]). Change or add the desired information or customize the product selector or classification retrospectively, for example, by adding or deselecting items. You can also use this option to select a different restart option if the conditions for the selected update collection have changed. Confirm your changes with the Save button.
		61
		62	If you want to delete a collection, select the corresponding entry, click //Delete //([[image:1745390182984-300.png]]) and confirm the process.
		63
		64	To duplicate an existing collection, select the desired entry from the list and click on //Duplicate //([[image:1745390182984-426.png]]) via the ribbon bar or the context menu. Change all relevant information and assign a new name to the copied Windows Update Collection. Confirm your changes here as well with the //Save //button.