Changes for page Einstellungen zum Windows Update Management

Summary

• Page properties (2 modified, 0 added, 0 removed)

Details

Page properties

Author

...	...	@@ -1,1 +1,1 @@
1		-XWiki.SF
	1	+XWiki.SV

Content

...	...	@@ -4,7 +4,7 @@
4	4
5	5	The settings were stored in the [[First Steps Wizard>>doc:ACMP.610.ACMP-Solutions.Patch Management.Windows Update Management.First Step Wizard des Windows Update Managements.WebHome]] for Windows Update Management during the initial setup.
6	6
7		-Navigate to the [[settings>>doc:ACMP.610.ACMP-Solutions.System.Einstellungen.Windows Update Management.WebHome]] (//System// > //Settings //> //Windows Update Management//) or alternatively open them via the plugin by clicking [[image:1733143232645-826.png||height="17" width="18"]]//Open //in the ribbon bar.
	7	+Navigate to the [[settings>>doc:ACMP.610.ACMP-Solutions.System.Einstellungen.Windows Update Management.WebHome]] (//System// > //Settings //> //Windows Update Management//) or alternatively open them via the plugin by clicking [[image:1733143232645-826.png||data-cmp-info="10" height="17" width="18"]]//Open //in the ribbon bar.
8	8
9	9	= Products =
10	10
...	...	@@ -14,13 +14,13 @@
14	14	* [[Classifications>>doc:ACMP.610.ACMP-Solutions.Patch Management.Windows Update Management.First Step Wizard des Windows Update Managements.WebHome||anchor="HClassifications"]]
15	15	* [[Languages>>doc:ACMP.610.ACMP-Solutions.Patch Management.Windows Update Management.First Step Wizard des Windows Update Managements.WebHome||anchor="HLanguages"]] (as well as Microsoft 365 app languages and additional correction tools)
16	16
17		-[[Settings for products, classifications and languages>>image:610_CAWUM_Einstellungen_Produkte_1658.png]]
	17	+[[Settings for products, classifications and languages>>image:610_CAWUM_Einstellungen_Produkte_1658.png||data-cmp-info="10"]]
18	18
19	19	{{aagon.versionierungsbox}}
20		-With ACMP version 6.10, you also have the option of displaying suggestions for product and language selection based on inventory data. This allows the user to view suggestions for products that are already installed on the client.
	20	+With acmp version 6.10, you also have the option of displaying suggestions for product and language selection based on inventory data. This allows the user to view suggestions for products that are already installed on the client.
21	21	{{/aagon.versionierungsbox}}
22	22
23		-If you need to add or deselect products, classifications or languages, you can make these changes conveniently on this page. To save, click// //[[image:1733144384832-822.png||height="18" width="18"]]// Save //in the ribbon bar.
	23	+If you need to add or deselect products, classifications or languages, you can make these changes conveniently on this page. To save, click// //[[image:1733144384832-822.png||data-cmp-info="10" height="18" width="18"]]// Save //in the ribbon bar.
24	24
25	25	= Options =
26	26
...	...	@@ -31,7 +31,7 @@
31	31	|**Download type**|**Description**|
32	32	|**On Demand – only download if at least one Client needs the Update**|This is the default setting, which is also recommended.
33	33	The download includes metadata containing all necessary information. However, the download of the setup files is only triggered when the client sends feedback. This means that only the setup files for updates that are required by at least one client are downloaded.{{aagon.infobox}}You can also use the option //Always download updates for these products and classifications// to specify an additional criterion for obtaining further updates that might not otherwise be included in the defined process. Read more about this in the section on [[Special feature: Always download updates for these products and classifications>>doc:||anchor="HSpecialfeature:Alwaysdownloadupdatesfortheseproductsandclassifications"]].{{/aagon.infobox}}|(((
34		-[[image:67_CAWUM_Option nur herunterladen_497.png||height="527" width="1705"]]
	34	+[[image:67_CAWUM_Option nur herunterladen_497.png||data-cmp-info="10" height="527" width="1705"]]
35	35	)))
36	36	|**Always - download all Updates**|(((
37	37	This setting downloads the setup files for **all** updates. This is also the case if they are not installed or required by any client.
...	...	@@ -39,18 +39,18 @@
39	39	{{aagon.warnungsbox}}
40	40	Please note that this download type requires the most storage space, as all setup files are downloaded to your file repository. The storage space required here can quickly run into several 100 GB.
41	41	{{/aagon.warnungsbox}}
42		-)))| [[image:67_CAWUM_Option immer herunterladen_578.png||height="75" width="545"]]
	42	+)))| [[image:67_CAWUM_Option immer herunterladen_578.png||data-cmp-info="10" height="75" width="545"]]
43	43
44		-If your file repository cannot provide the required storage space, we recommend that you [[move the ACMP Server to a file repository>>doc:ACMP.610.ACMP-Solutions.System.Verteilte File Repositories.WebHome||anchor="HACMPServerRepositorymithilfeeinesToolsauslagern"]].
	44	+If your file repository cannot provide the required storage space, we recommend that you [[move the acmp Server to a file repository>>doc:ACMP.610.ACMP-Solutions.System.Verteilte File Repositories.WebHome||anchor="HMigratingtheACMPServerRepositoryUsingaTool"]].
45	45
46	46	{{aagon.infobox}}
47	47	Please note the free storage space on your distributed file repositories.
48		-If you activate the Windows Updates content type, the setup files will be copied to the [[distributed file repositories>>doc:ACMP.610.ACMP-Solutions.System.Verteilte File Repositories.WebHome]] depending on the [[sync profile>>doc:ACMP.610.ACMP-Solutions.System.Verteilte File Repositories.WebHome||anchor="HSync-Profile"]].
	48	+If you activate the Windows Updates content type, the setup files will be copied to the [[distributed file repositories>>doc:ACMP.610.ACMP-Solutions.System.Verteilte File Repositories.WebHome]] depending on the [[sync profile>>doc:ACMP.610.ACMP-Solutions.System.Verteilte File Repositories.WebHome||anchor="HSyncprofil"]].
49	49	{{/aagon.infobox}}
50	50
51	51	With the checkbox //Only download updates newer than//, you can specify a specific date for the downloads. To do this, activate the checkbox and select a date that sets the time limit.
52	52
53		-[[Update download Options>>image:610_CAWUM Einstellungen Update-Download-Optionen_1251.png||alt="610_CAWUM Einstellungen Update-Download-Optionen_1337.png"]]
	53	+[[Update download Options>>image:610_CAWUM Einstellungen Update-Download-Optionen_1251.png||alt="610_CAWUM Einstellungen Update-Download-Optionen_1337.png" data-cmp-info="10"]]
54	54
55	55	== Special feature: //Always download updates for these products and classifications// ==
56	56
...	...	@@ -58,7 +58,7 @@
58	58
59	59	With this setting, it is irrelevant that you have selected the //On Demand// type, as this is intended to ensure that all important updates (e.g. critical or security-related updates) can be made available promptly and distributed quickly to the clients.
60	60
61		-[[image:67_CAWUM_Ausnahme Option Grafik_809.png||data-xwiki-image-style-alignment="center"]]
	61	+[[image:67_CAWUM_Ausnahme Option Grafik_809.png||data-cmp-info="10" data-xwiki-image-style-alignment="center"]]
62	62
63	63	==== Procedure ====
64	64
...	...	@@ -70,13 +70,13 @@
70	70
71	71	Now select the entry from the products that you want to designate as an exception. In the following illustration, this is //Microsoft Defender Antivirus//. Now tick all the boxes under the classifications for the types of updates that you want to download. For Microsoft Defender, for example, only critical and security-related updates should always be downloaded.
72	72
73		-[[On-demand settings for downloading updates>>image:610_CAWUM Download-Typ On Demand_932.png]]
	73	+[[On-demand settings for downloading updates>>image:610_CAWUM Download-Typ On Demand_932.png||data-cmp-info="10"]]
74	74
75	75	{{aagon.infobox}}
76	76	You can specify a time frame in which updates may be downloaded. To do this, enter the number of months to be included in the download. The default value is 24 months.
77	77	{{/aagon.infobox}}
78	78
79		-Click on [[image:1733143743698-898.png||height="18" width="18"]]// Save //in the ribbon bar to save your changes. The adjustments will also download any updates that may not (yet) have been requested by the clients but which you have classified as important. This process is triggered in the background by the setup download, which is executed shortly afterwards.
	79	+Click on [[image:1733143743698-898.png||data-cmp-info="10" height="18" width="18"]]// Save //in the ribbon bar to save your changes. The adjustments will also download any updates that may not (yet) have been requested by the clients but which you have classified as important. This process is triggered in the background by the setup download, which is executed shortly afterwards.
80	80
81	81	This procedure ensures that critical security updates, for example, are downloaded in good time and are available as setup files when the updates are needed.
82	82
...	...	@@ -97,30 +97,34 @@
97	97	The //options for client synchronisation //allow you to synchronise either rejected or withdrawn updates. If the Windows Update Scanner detects that a client requires a rejected or withdrawn update, this situation could be circumvented.
98	98
99	99	|**Option**|**Description**
100		-|**Synchronize declined Updates**|Rejected updates are additionally queried from the ACMP server. This allows a client to report installed or required rejected updates. For example, if it is suspected that a client urgently needs a rejected update to remain functional, this option could be selected.
	100	+|**Synchronize declined Updates**|Rejected updates are additionally queried from the acmp server. This allows a client to report installed or required rejected updates. For example, if it is suspected that a client urgently needs a rejected update to remain functional, this option could be selected.
101	101	Activating this option affects performance and data traffic, as a large number of additional updates are loaded into the system.
102		-|**Synchronize revoked Updates**|Withdrawn updates are also queried from the ACMP server. Updates may be withdrawn by Microsoft for various reasons, e.g. if they cause problems or are outdated.
103		-By activating this option, the withdrawn updates are reported to the ACMP server and can only be uninstalled via the console.
	102	+|**Synchronize revoked Updates**|Withdrawn updates are also queried from the acmp server. Updates may be withdrawn by Microsoft for various reasons, e.g. if they cause problems or are outdated.
	103	+By activating this option, the withdrawn updates are reported to the acmp server and can only be uninstalled via the console.
104	104
105	105	The reason for this is that certain updates are not synchronised with the clients by default, as this is intended to avoid problems and improve performance.
106		-Tick the appropriate option as required. To save your changes, click [[image:1733143922810-452.png||height="18" width="18"]]// Save//.
	106	+Tick the appropriate option as required. To save your changes, click [[image:1733143922810-452.png||data-cmp-info="10" height="18" width="18"]]// Save//.
107	107
108	108
109		-[[Windows Update Management settings>>image:69_CAWUM Einstellungen_Optionen2_1070.png||alt="67_CAWUM Einstellungen_Optionen2_1070.png"]]
	109	+[[Windows Update Management settings>>image:69_CAWUM Einstellungen_Optionen2_1070.png||alt="67_CAWUM Einstellungen_Optionen2_1070.png" data-cmp-info="10"]]
110	110
111	111	= Automatic declination of Updates =
112	112
113		-This setting allows you to create a filter that automatically denies updates based on the applicable criteria. The declined updates that fall under the filter are then deleted from the hard drive by the clean-up job. By default, the ‘Last used on’ field is suggested when the filter is opened for the first time, as this corresponded to the behaviour up to ACMP version 6.9: All updates that are recognised as no longer needed after the defined number of days are automatically denied and removed by the server task.
	113	+This setting allows you to create a filter that automatically denies updates based on the applicable criteria. The declined updates that fall under the filter are then deleted from the hard drive by the clean-up job. By default, the ‘Last used on’ field is suggested when the filter is opened for the first time, as this corresponded to the behaviour up to acmp version 6.9: All updates that are recognised as no longer needed after the defined number of days are automatically denied and removed by the server task.
114	114	An update is considered no longer needed if, for example, it has not been requested by clients within the configured period (filter option: Last used on) or if certain types of updates are generally irrelevant (preview updates from a specific third-party provider, etc.). With the help of the filter, you can define the automatic decline of Windows Updates and individually determine what should and should not be declined according to your criteria.
115	115
116	116	{{aagon.infobox}}
117		-The “Last used on” field helps you to ensure that ACMP automatically starts cleaning up after the time you have specified, based on this fulfilled criterion and any continuing filter options. Outdated updates, patches, etc. are automatically sorted out using this option. If you have implemented a functioning update process, you can leave this option disabled.
	117	+The “Last used on” field helps you to ensure that acmp automatically starts cleaning up after the time you have specified, based on this fulfilled criterion and any continuing filter options. Outdated updates, patches, etc. are automatically sorted out using this option. If you have implemented a functioning update process, you can leave this option disabled.
118	118	{{/aagon.infobox}}
119	119
120		-To use the filter, you must first tick the box under //Automatic reject updates//. Then click on the button [[image:1765269883037-206.png]]//Filter for automatic reject updates//. A new wizard will open, in which you can now configure an individual filter according to which updates should be rejected in future. Helpful tips and explanations for the various filter options can be found [[here>>doc:ACMP.610.ACMP-Solutions.Client-Management.Container.Container verwalten.WebHome]].
	120	+To use the filter, you must first tick the box under //Automatic reject updates//. Then click on the button [[image:1765269883037-206.png||data-cmp-info="10"]]//Filter for automatic reject updates//. A new wizard will open, in which you can now configure an individual filter according to which updates should be rejected in future. Helpful tips and explanations for the various filter options can be found [[here>>doc:ACMP.610.ACMP-Solutions.Client-Management.Container.Container verwalten.WebHome]].
121	121
122		-[[Filter for automatic decline of updates >>image:69_CAWUM_FIlter Konfiguration für das automatische Verweigern_965.png]]
	122	+{{box}}
	123	+**Tip: **Be sure to also read the “[[Automatic Rejection of Third-Party Updates>>doc:ACMP.610.ACMP-Solutions.Patch Management.Windows Update Management.Use Cases für WUM.Automatische Verweigerung von Drittanbieter Updates.WebHome]]” use case to learn more about how you can use a filter to decline specific Updates.
	124	+{{/box}}
123	123
	126	+[[Filter for automatic decline of updates >>image:69_CAWUM_FIlter Konfiguration für das automatische Verweigern_965.png||data-cmp-info="10"]]
	127	+
124	124	== Examples of filter configurations to decline updates ==
125	125
126	126	The following examples illustrate some filter configurations that are designed to automatically deny these updates. Please note that the level at which you are located or set the filter option is crucial. This can significantly determine whether an update should be explicitly declined if one or more conditions apply.
...	...	@@ -139,31 +139,31 @@
139	139
140	140	In this configuration, updates that have a name similar to %ARM64%, have a status of "Revoked" or were last reported as needed more than 180 days ago (filter: Last used "not in the last x days") are automatically declined (condition: OR).
141	141
142		-[[image:69_CAWUM Filter 1.png||data-xwiki-image-style-alignment="center"]]
	146	+[[image:69_CAWUM Filter 1.png||data-cmp-info="10" data-xwiki-image-style-alignment="center"]]
143	143
144	144	**Example: "Decline Microsoft Defender Antivirus updates that have not been needed for more than X days"**
145	145
146	146	Since Defender updates tend to be short-lived, you may want to deny them a little faster so that they do not take up unnecessary hard drive space. This can be achieved as follows, for example: Updates with the update product name "Microsoft Defender Antivirus" (filter: In) and the field "Last used on" (filter value: not in the last) in 14 days are automatically rejected.
147	147
148		-[[image:69_CAWUM Filter 2.png||data-xwiki-image-style-alignment="center"]]
	152	+[[image:69_CAWUM Filter 2.png||data-cmp-info="10" data-xwiki-image-style-alignment="center"]]
149	149
150	150	**Example: "Decline Microsoft Edge updates that are in the Beta or Dev channel"**
151	151
152	152	In this configuration, two filter options are combined: Only updates that have the product name "Microsoft Edge" (filter: In) __AND__ the designation %Microsoft Edge Beta Channel% (filter: similar) OR %Microsoft Edge Dev Channel% are automatically declined. This combination therefore declines all updates that are assigned to the beta or dev channel. The wildcards allow any number of characters to be taken into account.
153	153
154		-[[image:69_CAWUM Filter 3.png||data-xwiki-image-style-alignment="center"]]
	158	+[[image:69_CAWUM Filter 3.png||data-cmp-info="10" data-xwiki-image-style-alignment="center"]]
155	155
156	156	**Example: "Reject Windows 11 22H2 updates"**
157	157
158	158	Updates with the update product name "Windows 11" (filter: In) __AND__ a designation (filter: similar) of "22H2%" are automatically rejected. The percent signs represent a wildcard. This means that similar-sounding version updates of Windows 11 are also denied with this filter configuration.
159	159
160		-[[image:69_CAWUM Filter 4.png||data-xwiki-image-style-alignment="center"]]
	164	+[[image:69_CAWUM Filter 4.png||data-cmp-info="10" data-xwiki-image-style-alignment="center"]]
161	161
162	162	**Combination of all filter options**
163	163
164	164	You can also create a more complex filter combination within the filter by establishing a connection between the individual filter operators. However, please note that the top operator also applies to the conditions below and that there is an AND/OR correlation between the individual filters. The following illustration shows how to use the above.
165	165
166		-[[Filter combination>>image:69_CAWUM Automatisches Verweigern Updates Beispiele_1732.png]]
	170	+[[Filter combination>>image:69_CAWUM Automatisches Verweigern Updates Beispiele_1732.png||data-cmp-info="10"]]
167	167
168	168	The advanced filter allows you to focus on specific environments and provide exactly the updates that meet your criteria.
169	169
...	...	@@ -171,7 +171,7 @@
171	171
172	172	Continue your work by displaying a preview on the second page of which Windows Updates will be automatically denied by the filter. Exit the configurations and click //Done//. Save your changes in the ribbon bar and save them.
173	173
174		-[[Filter for automatic decline of updates >>image:69_CAWUM Automatische Verweigerung von Windows Updates Einstellungen_993.png]]
	178	+[[Filter for automatic decline of updates >>image:69_CAWUM Automatische Verweigerung von Windows Updates Einstellungen_993.png||data-cmp-info="10"]]
175	175
176	176
177	177	= Third Party Catalogues =
...	...	@@ -193,15 +193,15 @@
193	193	Please note that this is a standard testing and release process for Windows updates. Any Windows update that has not been explicitly assigned to a custom testing and release process will always be assigned to this process. For this reason, no filter settings are available for the default testing and release process.
194	194	{{/aagon.infobox}}
195	195
196		-To edit ([[image:1733144849912-156.png]]) (//CTRL + E//) or delete ([[image:1733144849912-908.png]]) (//Del//) an existing test and release process, click on the corresponding entry in the list and press the button for the respective action. When editing, a new window opens where you can edit the general information and content (products and classifications) or adjust the configuration again.
	200	+To edit ([[image:1733144849912-156.png||data-cmp-info="10"]]) (//CTRL + E//) or delete ([[image:1733144849912-908.png||data-cmp-info="10"]]) (//Del//) an existing test and release process, click on the corresponding entry in the list and press the button for the respective action. When editing, a new window opens where you can edit the general information and content (products and classifications) or adjust the configuration again.
197	197
198	198	You can use the arrows on the side to move the priorities of the respective processes. Read more about this in the section [[Changing the priorities of test and release processes>>doc:||anchor="HChangingtheprioritiesoftestandreleaseprocesses"]].
199	199
200		-[[Übersicht der Test- und Freigabeprozesse>>image:67_CAWUM EInstellungen_Übersicht Test- und Freigabeprozess_1059.png]]
	204	+[[Übersicht der Test- und Freigabeprozesse>>image:67_CAWUM EInstellungen_Übersicht Test- und Freigabeprozess_1059.png||data-cmp-info="10"]]
201	201
202	202	== Add test and release process ==
203	203
204		-To add a new test and release process, click on the button ([[image:1733144928460-805.png]]) in the top bar or press the key combination //CTRL + N //in the open console. A wizard will open, where you can enter a name and description on the first page.
	208	+To add a new test and release process, click on the button ([[image:1733144928460-805.png||data-cmp-info="10"]]) in the top bar or press the key combination //CTRL + N //in the open console. A wizard will open, where you can enter a name and description on the first page.
205	205
206	206	{{box}}
207	207	**Tip:** Give the test and release process a unique name so that you can assign the correct process later on. It may be helpful to name the product, e.g. "Defender Test and Release Process" or "Office Test and Release Process", and create a separate process for each product/product collection.
...	...	@@ -208,7 +208,7 @@
208	208	{{/box}}
209	209
210	210
211		-[[Add general information about the testing and release process>>image:67_Einstellungen_Test- und Freigabeprozess hinzufügen_966.png]]
	215	+[[Add general information about the testing and release process>>image:67_Einstellungen_Test- und Freigabeprozess hinzufügen_966.png||data-cmp-info="10"]]
212	212
213	213	Then click //Next >// to define the content of this testing and release process. On the next page, the selectable products and classifications are divided into two areas.
214	214
...	...	@@ -232,9 +232,9 @@
232	232	**Info**: Using the “Suggested” column, you can see directly from the product list whether a product is suggested for the filter or not.
233	233	{{/box}}
234	234
235		-Therefore, tick this entry and select the classifications that are to be covered by it. If necessary, read [[here>>doc:ACMP.610.ACMP-Solutions.Patch Management.Windows Update Management.Konfigurationsmöglichkeiten im Windows Update Management.WebHome||anchor="HKlassifizierungen"]] again to find out what type of update covers what. All types of "Updates" should be taken into account here (//critical//, //definition//, //security updates//, //update rollups// and //updates//). Click //Next >// again after you have activated all relevant checkboxes.
	239	+Therefore, tick this entry and select the classifications that are to be covered by it. If necessary, read [[here>>doc:ACMP.610.ACMP-Solutions.Patch Management.Windows Update Management.Konfigurationsmöglichkeiten im Windows Update Management.WebHome||anchor="HClassifications"]] again to find out what type of update covers what. All types of "Updates" should be taken into account here (//critical//, //definition//, //security updates//, //update rollups// and //updates//). Click //Next >// again after you have activated all relevant checkboxes.
236	236
237		-[[Define content for testing and release>>image:610_CAWUM Test und Freigabering Inhalte_966.png||alt="610_Einstellungen_Inhalte für Test und Freigabe_966.png"]]
	241	+[[Define content for testing and release>>image:610_CAWUM Test und Freigabering Inhalte_966.png||alt="610_Einstellungen_Inhalte für Test und Freigabe_966.png" data-cmp-info="10"]]
238	238
239	239	On the last page, you must now define the test ring configuration. The structure of the rings stored here is similar and always follows the same sequence: The updates can be moved either manually or automatically (after a number of days specified by you) from //No ring //to //Test ring 1 //and //Test ring 2 //until they reach the release ring, where they are distributed and installed on all clients that meet the update requirements.
240	240
...	...	@@ -278,7 +278,7 @@
278	278	Updates are only distributed to and installed on a client if it meets all the requirements (e.g. the appropriate operating system, the client reports the update as required, or the EULA must be activated).
279	279	{{/aagon.infobox}}
280	280
281		-[[Example configuration of a test and release ring>>image:67_Einstellungen_Test- und Freigabeprozess Konfiguration_966.png]]
	285	+[[Example configuration of a test and release ring>>image:67_Einstellungen_Test- und Freigabeprozess Konfiguration_966.png||data-cmp-info="10"]]
282	282
283	283
284	284	Finish the configurations and click //Done//. The newly added process is now listed in the overview and can be distributed.
...	...	@@ -288,7 +288,7 @@
288	288	All updates released by Microsoft for the product //Microsoft 365 Apps/Office 2019/Office LTSC //with the classifications //Critical//, //Definition//, //Security Updates//, //Update Rollups// and //Updates// would first be placed in Test Ring 1 after you downloaded them. They would remain there for seven days until they were transferred to Test Ring 2 and finally released after another seven days.
289	289
290	290	{{aagon.infobox}}
291		-Microsoft has a fixed update cycle according to which new releases are made available. Read the section „[[Update cycle: How does the update from Microsoft get to the ACMP Client?>>doc:ACMP.610.ACMP-Solutions.Patch Management.Windows Update Management.Exkurse und FAQ.Exkurs\: Update Zyklus\: Wie kommt das Update von Microsoft auf den ACMP Client?.WebHome]]“ to find out which steps are taken in each case and how the testing and release processes affect this.
	295	+Microsoft has a fixed update cycle according to which new releases are made available. Read the section „[[Update cycle: How does the update from Microsoft get to the acmp Client?>>doc:ACMP.610.ACMP-Solutions.Patch Management.Windows Update Management.Exkurse und FAQ.Exkurs\: Update Zyklus\: Wie kommt das Update von Microsoft auf den ACMP Client?.WebHome]]“ to find out which steps are taken in each case and how the testing and release processes affect this.
292	292	{{/aagon.infobox}}
293	293
294	294	== Changing the priorities of test and release processes ==
...	...	@@ -295,10 +295,10 @@
295	295
296	296	You can change the priorities of test and release processes if the same products appear in different processes. The priority determines which updates can be distributed first.
297	297
298		-You can see the priority of each process in the table on the left. The numbers below the asterisk column indicate the type of priority. Prioritisation works as follows: **the smaller the number, the higher the priority. **Change the order by using the arrows ([[image:1733145433176-476.png]] ,[[image:1733145433176-745.png]] ,[[image:1733145433176-934.png]] ,[[image:1733145433177-660.png]] ) to move the processes to the appropriate position.
	302	+You can see the priority of each process in the table on the left. The numbers below the asterisk column indicate the type of priority. Prioritisation works as follows: **the smaller the number, the higher the priority. **Change the order by using the arrows ([[image:1733145433176-476.png||data-cmp-info="10"]] ,[[image:1733145433176-745.png||data-cmp-info="10"]] ,[[image:1733145433176-934.png||data-cmp-info="10"]] ,[[image:1733145433177-660.png||data-cmp-info="10"]] ) to move the processes to the appropriate position.
299	299
300	300	{{box}}
301	301	**Example:** The product Microsoft Defender Antivirus (Windows > Microsoft Defender Antivirus) is selected/used in both the "Microsoft Security Updates" and "Defender Testing and Release Process" processes. "Microsoft Security Updates" has priority 1, while the "Defender Test and Release Process" has priority 6. Since there is only one assignment within the test and release process, the one with the highest priority is selected. The updates are therefore distributed via the "Microsoft Security Updates" process.
302	302	{{/box}}
303	303
304		-[[Change priorities of testing and release processes>>image:67_CAWUM Priorität Test- und Freigabeprozess_461.png]]
	308	+[[Change priorities of testing and release processes>>image:67_CAWUM Priorität Test- und Freigabeprozess_461.png||data-cmp-info="10"]]