Changes for page Einstellungen zum Windows Update Management

Summary

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

Details

Page properties

Content

...	...	@@ -1,18 +1,18 @@
1	1	{{aagon.floatingbox/}}
2	2
3		-Within the Windows Update Management settings, you can subsequently make changes to settings already set for [[products>>doc:||anchor="HProdukte"]] and [[classifications>>doc:||anchor="HProdukte"]] and configure the [[testing and approval processes>>doc:||anchor="HTestenundFreigeben"]]. This makes it possible to remove or add further products and classifications at a later date, as well as to take language adjustments into account. If your selection of hardware manufacturers is expanded, you can also include additional third-party providers at a later stage and select them via the settings and include them in the meta and setup data download.
	3	+Within the Windows Update Management settings, you can subsequently make changes to settings already set for [[products>>doc:||anchor="HProducts"]] and [[classifications>>doc:||anchor="HClassifications"]], as well as customize the automatic decline of updates and configure the [[testing and release processes>>doc:||anchor="HTestandRelease"]]. This makes it possible to remove or add further products and classifications at a later date, as well as to take language adjustments into account. If your selection of hardware manufacturers is expanded, you can also include additional third-party providers at a later stage and select them via the settings and include them in the meta and setup data download.
4	4
5		-The settings were stored in the [[First Steps Wizard>>doc:ACMP.68.ACMP-Solutions.Patch Management.Windows Update Management.First Step Wizard des Windows Update Managements.WebHome]] for Windows Update Management during the initial setup.
	5	+The settings were stored in the [[First Steps Wizard>>doc:ACMP.69.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.68.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.69.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.
8	8
9	9	= Products =
10	10
11		-The settings you have already made in the [[First Steps Wizard>>doc:ACMP.68.ACMP-Solutions.Patch Management.Windows Update Management.First Step Wizard des Windows Update Managements.WebHome]] are listed under Products. This allows you to adjust the configurations retrospectively and adapt them to updated conditions in your working environment. The listed products include:
	11	+The settings you have already made in the [[First Steps Wizard>>doc:ACMP.69.ACMP-Solutions.Patch Management.Windows Update Management.First Step Wizard des Windows Update Managements.WebHome]] are listed under Products. This allows you to adjust the configurations retrospectively and adapt them to updated conditions in your working environment. The listed products include:
12	12
13		-* [[Products>>doc:ACMP.68.ACMP-Solutions.Patch Management.Windows Update Management.First Step Wizard des Windows Update Managements.WebHome||anchor="HProdukte"]]
14		-* [[Classifications>>doc:ACMP.68.ACMP-Solutions.Patch Management.Windows Update Management.First Step Wizard des Windows Update Managements.WebHome||anchor="HKlassifizierungen"]]
15		-* [[Languages>>doc:ACMP.68.ACMP-Solutions.Patch Management.Windows Update Management.First Step Wizard des Windows Update Managements.WebHome||anchor="HSprachen"]] (as well as Microsoft 365 app languages and additional correction tools)
	13	+* [[Products>>doc:ACMP.69.ACMP-Solutions.Patch Management.Windows Update Management.First Step Wizard des Windows Update Managements.WebHome||anchor="HProducts"]]
	14	+* [[Classifications>>doc:ACMP.69.ACMP-Solutions.Patch Management.Windows Update Management.First Step Wizard des Windows Update Managements.WebHome||anchor="HClassifications"]]
	15	+* [[Languages>>doc:ACMP.69.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	17	[[Settings for products, classifications and languages>>image:68_CAWUM_Einstellungen_Produkte_1658.png]]
18	18
...	...	@@ -22,7 +22,7 @@
22	22
23	23	== Update download options ==
24	24
25		-Windows Update Management downloads the available updates to your [[File Repository>>doc:ACMP.68.ACMP-Solutions.System.Verteilte File Repositories.WebHome]] in the background. The download is divided into two parts, with the metadata being downloaded via a separate job. These download options mainly concern how the setup files are downloaded. You can use the button to select the download type for the installation files:
	25	+Windows Update Management downloads the available updates to your [[File Repository>>doc:ACMP.69.ACMP-Solutions.System.Verteilte File Repositories.WebHome]] in the background. The download is divided into two parts, with the metadata being downloaded via a separate job. These download options mainly concern how the setup files are downloaded. You can use the button to select the download type for the installation files:
26	26
27	27	|**Download type**|**Description**|
28	28	|**On Demand – only download if at least one Client needs the Update**|This is the default setting, which is also recommended.
...	...	@@ -37,11 +37,11 @@
37	37	{{/aagon.warnungsbox}}
38	38	)))| [[image:67_CAWUM_Option immer herunterladen_578.png||height="75" width="545"]]
39	39
40		-If your file repository cannot provide the required storage space, we recommend that you  [[move the ACMP Server to a file repository>>doc:ACMP.68.ACMP-Solutions.System.Verteilte File Repositories.WebHome||anchor="HACMPServerRepositorymithilfeeinesToolsauslagern"]].
	40	+If your file repository cannot provide the required storage space, we recommend that you [[move the ACMP Server to a file repository>>doc:ACMP.69.ACMP-Solutions.System.Verteilte File Repositories.WebHome||anchor="HACMPServerRepositorymithilfeeinesToolsauslagern"]].
41	41
42	42	{{aagon.infobox}}
43	43	Please note the free storage space on your distributed file repositories.
44		-If you activate the Windows Updates content type, the setup files will be copied to the [[distributed file repositories>>doc:ACMP.68.ACMP-Solutions.System.Verteilte File Repositories.WebHome]] depending on the [[sync profile>>doc:ACMP.68.ACMP-Solutions.System.Verteilte File Repositories.WebHome||anchor="HSync-Profile"]].
	44	+If you activate the Windows Updates content type, the setup files will be copied to the [[distributed file repositories>>doc:ACMP.69.ACMP-Solutions.System.Verteilte File Repositories.WebHome]] depending on the [[sync profile>>doc:ACMP.69.ACMP-Solutions.System.Verteilte File Repositories.WebHome||anchor="HSync-Profile"]].
45	45	{{/aagon.infobox}}
46	46
47	47	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.
...	...	@@ -77,17 +77,9 @@
77	77	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.
78	78
79	79	{{aagon.warnungsbox}}
80		-Be careful with the number of selected products and classifications for updates, as this can result in high storage space requirements and is equivalent to the option// Always – download all updates//.
	80	+Be careful with the number of selected products and classifications for updates, as this can result in high storage space requirements and is equivalent to the option// Always – download all updates//.
81	81	{{/aagon.warnungsbox}}
82	82
83		-== Automatic declination of Windows Updates ==
84		-
85		-This setting allows you to specify the number of days that must pass before an update that is no longer needed is automatically rejected. You defined the number entered here during the initial configuration in the [[First Steps Wizard>>doc:ACMP.68.ACMP-Solutions.Patch Management.Windows Update Management.First Step Wizard des Windows Update Managements.WebHome||anchor="HAutomatischesBereinigenvonWindowsUpdates"]]. If you no longer wish to use this automatic function, uncheck the //Automatically reject updates// checkbox.
86		-
87		-{{aagon.infobox}}
88		-Checking this option helps ACMP to start cleaning itself after the time you have specified. Outdated updates, patches, etc. are automatically sorted out by this option. If you have implemented a functioning update process, you can leave the option deactivated.
89		-{{/aagon.infobox}}
90		-
91	91	== Automatically accept Update EULAs ==
92	92
93	93	You can use this checkbox to automatically accept any update changes to the EULAs. The EULAs will then be automatically accepted as unread without you having to read the amended terms of use.
...	...	@@ -110,12 +110,78 @@
110	110	Tick the appropriate option as required. To save your changes, click [[image:1733143922810-452.png||height="18" width="18"]]// Save//.
111	111
112	112
113		-[[Windows Update Management settings>>image:67_CAWUM Einstellungen_Optionen2_1070.png]]
	105	+[[Windows Update Management settings>>image:69_CAWUM Einstellungen_Optionen2_1070.png||alt="67_CAWUM Einstellungen_Optionen2_1070.png"]]
114	114
	107	+== Automatic declination of Updates ==
	108	+
	109	+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.
	110	+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.
	111	+
	112	+{{aagon.infobox}}
	113	+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.
	114	+{{/aagon.infobox}}
	115	+
	116	+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.69.ACMP-Solutions.Client-Management.Container.Container verwalten.WebHome]].
	117	+
	118	+[[Filter for automatic decline of updates >>image:69_CAWUM_FIlter Konfiguration für das automatische Verweigern_965.png]]
	119	+
	120	+== Examples of filter configurations to decline updates ==
	121	+
	122	+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.
	123	+
	124	+{{box}}
	125	+**Tip**: For information on how to create a filter and the different filter modes and basic elements available for each filter, see [[//Working with filter types//>>doc:ACMP.69.ACMP-Solutions.Client-Management.Container.Container verwalten.Arbeiten mit den Filtertypen.WebHome]].
	126	+{{/box}}
	127	+
	128	+Examples:
	129	+
	130	+* "Decline all updates that contain the string %ARM64% in their name"
	131	+
	132	+* "All updates that have been revoked by Microsoft (expiry status IN Revoked)"
	133	+
	134	+* "All updates that have not been used for more than 180 days."
	135	+
	136	+In this configuration, updates that have a name similar to %ARM64%, have a status of "Revoked" and were last reported as needed more than 180 days ago (filter: Last used "not in the last x days") are automatically declined (condition: OR).
	137	+
	138	+[[image:69_CAWUM Filter 1.png||data-xwiki-image-style-alignment="center"]]
	139	+
	140	+**Example: "Decline Microsoft Defender Antivirus updates that have not been needed for more than X days"**
	141	+
	142	+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.
	143	+
	144	+[[image:69_CAWUM Filter 2.png||data-xwiki-image-style-alignment="center"]]
	145	+
	146	+**Example: "Decline Microsoft Edge updates that are in the Beta or Dev channel"**
	147	+
	148	+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.
	149	+
	150	+[[image:69_CAWUM Filter 3.png||data-xwiki-image-style-alignment="center"]]
	151	+
	152	+**Example: "Reject Windows 11 22H2 updates"**
	153	+
	154	+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.
	155	+
	156	+[[image:69_CAWUM Filter 4.png||data-xwiki-image-style-alignment="center"]]
	157	+
	158	+**Combination of all filter options**
	159	+
	160	+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.
	161	+
	162	+[[Filter combination>>image:69_CAWUM Automatisches Verweigern Updates Beispiele_1732.png]]
	163	+
	164	+The advanced filter allows you to focus on specific environments and provide exactly the updates that meet your criteria.
	165	+
	166	+In this example, we want to create a collection for a Windows 11 upgrade, so we select only the product //Windows 11// in the upper section and only //Upgrades// under Classifications. The filter mode selected here is ‘Standard filter’.
	167	+
	168	+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.
	169	+
	170	+[[Filter for automatic decline of updates >>image:69_CAWUM Automatische Verweigerung von Windows Updates Einstellungen_993.png]]
	171	+
	172	+
115	115	= Third Party Catalogues =
116	116
117	117	Third party catalogues can also be used to obtain updates from providers other than Microsoft.
118		-These currently include updates from //HP//, //Lenovo //and //Dell//. Read more about third party catalogues [[here>>doc:ACMP.68.ACMP-Solutions.Patch Management.Windows Update Management.Drittanbieterkataloge.WebHome]].
	176	+These currently include updates from //HP//, //Lenovo //and //Dell//. Read more about third party catalogues [[here>>doc:ACMP.69.ACMP-Solutions.Patch Management.Windows Update Management.Drittanbieterkataloge.WebHome]].
119	119
120	120	= Test and Release =
121	121
...	...	@@ -122,7 +122,7 @@
122	122	An important part of Windows Update Management is the automated distribution of selected updates. To do this, you need to define the test and release process that will be used for distribution. Here, you can assign the appropriate classifications to each product that is to be included, based on your own process. You can then define the transitions to the various test rings and the retention period that an update should adhere to. The latter option allows you to determine how quickly published updates and upgrades can be used and installed in your company.
123	123
124	124	{{box}}
125		-**Tip: **Read the excurses //[[How are products and classifications related in ACMP?>>doc:ACMP.68.ACMP-Solutions.Patch Management.Windows Update Management.Exkurse und FAQ.Exkurs\: Wie hängen Produkte und Klassifizierungen in ACMP zusammen?.WebHome]]// to find out how the two areas influence each other.
	183	+**Tip: **Read the excurses //[[How are products and classifications related in ACMP?>>doc:ACMP.69.ACMP-Solutions.Patch Management.Windows Update Management.Exkurse und FAQ.Exkurs\: Wie hängen Produkte und Klassifizierungen in ACMP zusammen?.WebHome]]// to find out how the two areas influence each other.
126	126	{{/box}}
127	127
128	128	With the delivery of ACMP, a default test and release process is defined, whereby updates are released directly.
...	...	@@ -133,7 +133,7 @@
133	133
134	134	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.
135	135
136		-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="HPrioritE4tenderTest-undFreigabeprozesseE4ndern"]].
	194	+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"]].
137	137
138	138	[[Übersicht der Test- und Freigabeprozesse>>image:67_CAWUM EInstellungen_Übersicht Test- und Freigabeprozess_1059.png]]
139	139
...	...	@@ -151,82 +151,80 @@
151	151	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.
152	152
153	153	{{aagon.infobox}}
154		-Please note that you can **ONLY **select products that you have checked in the [[First Steps Wizard>>doc:ACMP.68.ACMP-Solutions.Patch Management.Windows Update Management.First Step Wizard des Windows Update Managements.WebHome]] or later in the [[settings>>doc:]]. If you notice that essential entries are missing here, you must cancel the wizard and add them before you can continue.
	212	+Please note that you can **ONLY **select products that you have checked in the [[First Steps Wizard>>doc:ACMP.69.ACMP-Solutions.Patch Management.Windows Update Management.First Step Wizard des Windows Update Managements.WebHome]] or later in the [[settings>>doc:]]. If you notice that essential entries are missing here, you must cancel the wizard and add them before you can continue.
155	155	{{/aagon.infobox}}
156	156
157	157	{{box}}
158		-**Tipp:** Wie bereits erwähnt, ist es ratsam, für jedes Produkt/jede Produktgruppe einen eigenen Test- und Freigabeprozess zu erstellen. Mischen Sie nicht verschiedene Produkte, sollten unterschiedliche Klassifizierungen verschiedene Prozesse beinhalten. Legen Sie lieber für jedes Produkt mit der jeweiligen Klassifikation einen eigenen Prozess an, damit Sie den Verteilungsgrad individueller bestimmen können.
	216	+**Tip:** As already mentioned, it is advisable to create a separate testing and release process for each product/product group. Do not mix different products if different classifications involve different processes. It is better to create a separate process for each product with the respective classification so that you can determine the degree of distribution more individually.
159	159	{{/box}}
160	160
161		-In diesem Beispiel soll der Freigabeprozess für das Produkt //Office// > //Microsoft 365 Apps/Office 2019/Office LTSC// bestimmt werden. Haken Sie also diesen Eintrag an und wählen Sie die Klassifizierungen aus, die dadurch abgedeckt werden sollen. Lesen Sie [[hier>>doc:ACMP.68.ACMP-Solutions.Patch Management.Windows Update Management.Konfigurationsmöglichkeiten im Windows Update Management.WebHome||anchor="HKlassifizierungen"]] nochmal ggf. nach, welche Art von Update was abdeckt. Hier sollen alle Arten von „Updates“ berücksichtigt werden (//Critical-//,// Definition-//,// Security Updates//, //Update Rollups// und //Updates//). Klicken Sie erneut auf //Weiter >//, nachdem Sie alle relevanten Checkboxen aktiviert haben.
	219	+In this example, the release process for the product //Office// > //Microsoft 365 Apps/Office 2019/Office LTSC// is to be determined. Therefore, tick this entry and select the classifications that are to be covered by it. If necessary, read [[here>>doc:ACMP.69.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.
162	162
163		-[[Inhalte für Test und Freigabe definieren>>image:67_Einstellungen_Inhalte für Test und Freigabe_966.png]]
	221	+[[Define content for testing and release>>image:67_Einstellungen_Inhalte für Test und Freigabe_966.png]]
164	164
165		-Auf der letzten Seite müssen Sie nun die Testringkonfiguration festlegen. Der Aufbau, der hier hinterlegten Ringe, verhält sich ähnlich und durchläuft immer wieder den gleichen Ablauf: Die Updates lassen sich entweder manuell oder automatisch (nach einer von Ihnen festgelegten Anzahl an Tagen) von //Kein Ring //in den //Testring 1 //und //Testring 2 //verschieben, bis sie den Freigabering erreicht haben, wo sie auf allen Clients verteilt und installiert werden, die die Anforderungen der Updates erfüllen.
166		-Den jeweiligen Verteilungsprozess und -ring können Sie dann über das Grid im Windows Update Management unter dem Tab //Updates //einsehen. Die beiden Einträge beziehen sich auf die von Ihnen hier getroffenen Konfigurationen und werden als Tabelleneinträge mit gelistet.
	223	+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.
167	167
168		-Alle heruntergeladenen Updates befinden sich zunächst in //Kein Ring//. Über die Radiobutton haben Sie die folgenden Möglichkeiten:
	225	+You can then view the respective distribution process and ring via the grid in Windows Update Management under the //Updates //tab. The two entries refer to the configurations you have made here and are listed as table entries.
169	169
170		-**Kein Ring**
	227	+All downloaded updates are initially located in //No Ring//. The radio buttons give you the following options:
171	171
172		-|(% style="width:399px" %)Updates manuell in den nächsten Ring verschieben.|(% style="width:1293px" %)Es erfolgt nur eine Verschiebung des Updates, wenn Sie es manuell in den nächsten Ring verschieben.
	229	+**No Ring**
	230	+
	231	+|(% style="width:399px" %)Manually move updates to the next ring.|(% style="width:1293px" %)The update will only be postponed if you manually move it to the next ring.
	232	+|(% style="width:399px" %)Automatically move updates to test ring 1.|(% style="width:1293px" %)Here, you can specify the waiting period in days, i.e. how long an update must have been in this ring before it is automatically moved to test ring 1.
173	173	|(% style="width:399px" %)(((
174		-Updates automatisch in Testring 1 verschieben.
175		-)))|(% style="width:1293px" %)Legen Sie hier die Wartezeit in Tagen fest, wie lange ein Update mindestens in diesem Ring gewesen sein muss, ehe er automatisch in den Testring 1 verschoben wird.
176		-|(% style="width:399px" %)Überspringe diesen Ring und verschiebe Updates direkt in den nächsten Ring, nach Erreichen des Verteilungsstatus //Synchronisation //oder //Synchronisiert//|(% style="width:1293px" %)(((
177		-Hier ist der Stand der heruntergeladenen Dateien im File Repository entscheidend. Wenn die Dateien auf den zuständigen File Repositories bereits verteilt sind, lautet der Verteilungsstatus //Synchronisiert//, da sie abrufbar sind.
	234	+Skip this ring and move updates directly to the next ring after reaching the distribution status //Synchronisation //or //Synchronised//.
	235	+)))|(% style="width:1293px" %)(((
	236	+The status of the downloaded files in the file repository is decisive here. If the files have already been distributed to the relevant file repositories, the distribution status is //Synchronised//, as they are available for retrieval.
178	178
179		-//Synchronisation //bedeutet, dass der Prozess noch läuft oder derzeit stattfindet, weil die Dateien eingereiht werden und noch nicht vollständig vorhanden sind.
	238	+//Synchronisation //means that the process is still running or currently taking place because the files are being queued and are not yet fully available.
180	180
181	181	{{aagon.infobox}}
182		-Sollte das File Repository sich noch synchronisieren, kann es sein, dass die Dateien dann nicht übermittelt werden, weil es die Daten noch nicht erhalten hat, die angefordert wurden. In diesem Fall sollten Sie ein bisschen warten, ehe der Status sich verändert hat.
	241	+If the file repository is still synchronising, it may be that the files are not transferred because it has not yet received the requested data. In this case, you should wait a little while before the status changes.
183	183	{{/aagon.infobox}}
184	184	)))
185	185
186		-Nachdem die Updates von //Kein Ring //in den //Testring 1 //verschoben wurden, müssen Sie den weiteren Verlauf definieren:
	245	+After the updates from //No Ring //have been moved to //Test Ring 1//, you must define the further course of action:
187	187
188		-**Testring 1**
	247	+**Test ring 1**
189	189
190		-|(% style="width:398px" %)Updates manuell in den nächsten Ring verschieben.|(% style="width:1294px" %)Es erfolgt nur eine Verschiebung des Updates, wenn Sie es manuell in den nächsten Ring verschieben.
191		-|(% style="width:398px" %)(((
192		-Updates automatisch in Testring 2 verschieben.
193		-)))|(% style="width:1294px" %)Geben Sie hier an, nach wie vielen Tagen die Updates automatisch in den Testring 2 verschoben werden sollen. Die Wartezeit muss in Tagen eingetragen werden.
194		-|(% style="width:398px" %)Sobald die Installationsdateien verfügbar sind diesen Ring überspringen und Updates direkt in den nächsten Ring verschieben.|(% style="width:1294px" %)Hierbei wird dieser Ring übersprungen und Updates werden in den nächsten Ring verschoben.
	249	+|(% style="width:398px" %)Manually move updates to the next ring.|(% style="width:1294px" %)The update will only be postponed if you manually move it to the next ring.
	250	+|(% style="width:398px" %)Automatically move updates to test ring 2.|(% style="width:1294px" %)Specify here after how many days the updates should be automatically moved to test ring 2. The waiting time must be entered in days.
	251	+|(% style="width:398px" %)Once the installation files are available, skip this ring and move updates directly to the next ring.|(% style="width:1294px" %)In this case, this ring is skipped and updates are moved to the next ring.
195	195
196		-**Testring 2**
	253	+**Test ring 2**
197	197
198		-|(% style="width:396px" %)Updates manuell in den nächsten Ring verschieben.|(% style="width:1296px" %)Es erfolgt nur eine Verschiebung des Updates, wenn Sie es manuell in den nächsten Ring verschieben.
199		-|(% style="width:396px" %)(((
200		-Updates automatisch in Freigabering verschieben.
201		-)))|(% style="width:1296px" %)Hierbei geben Sie an, nach wie vielen Tagen die Updates in den Freigabering verschoben werden sollen.
202		-|(% style="width:396px" %)Sobald die Installationsdateien verfügbar sind diesen Ring überspringen und Updates direkt in den nächsten Ring verschieben.|(% style="width:1296px" %)Hierbei wird dieser Ring übersprungen und Updates werden in den nächsten Ring verschoben.
	255	+|(% style="width:396px" %)Manually move updates to the next ring.|(% style="width:1296px" %)The update will only be postponed if you manually move it to the next ring.
	256	+|(% style="width:396px" %)Automatically move updates to the release ring.|(% style="width:1296px" %)Here, you specify after how many days the updates should be moved to the release ring.
	257	+|(% style="width:396px" %)Once the installation files are available, skip this ring and move updates directly to the next ring.|(% style="width:1296px" %)In this case, this ring is skipped and updates are moved to the next ring.
203	203
204		-Alle Updates, die nun die Verteilungsringe durchlaufen haben, befinden sich jetzt im Freigabering. Der Freigabering stellt die letzte Stufe vor der Verteilung und Installation der Updates auf den Clients dar.
	259	+All updates that have now passed through the distribution rings are now in the release ring. The release ring is the final stage before the updates are distributed and installed on the clients.
205	205
206	206	{{aagon.infobox}}
207		-Es werden nur Updates auf einen Client verteilt und installiert, wenn dieser auch alle Anforderungen (z.B. das passende Betriebssystem, Client meldet das Update als benötigt oder die EULA muss aktiviert werden) des Updates erfüllt.
	262	+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).
208	208	{{/aagon.infobox}}
209	209
210		-[[Beispiel Konfiguration eines Test- und Freigaberings>>image:67_Einstellungen_Test- und Freigabeprozess Konfiguration_966.png]]
	265	+[[Example configuration of a test and release ring>>image:67_Einstellungen_Test- und Freigabeprozess Konfiguration_966.png]]
211	211
212	212
213		-Beenden Sie die Konfigurationen und klicken Sie auf //Fertig//. Der neu hinzugefügte Prozess wird nun in der Übersicht gelistet und kann verteilt werden.
	268	+Finish the configurations and click //Done//. The newly added process is now listed in the overview and can be distributed.
214	214
215		-Nach dieser Konfiguration würde das Ergebnis wie folgt lauten:
216		-Alle von Microsoft erschienenen Updates zum Produkt //Microsoft 365 Apps/Office 2019/Office LTSC //mit den Klassifizierungen //Critical-//,// Definition-//,// Security Updates//, //Update Rollups// und //Updates// würden, nachdem sie von Ihnen heruntergeladen wurden, erstmal in den Testring 1 gelegt. Dort bleiben sie sieben Tage liegen, bis sie in den Testring 2 übergeben und nach weiteren sieben Tagen, schlussendlich freigegeben werden würden.
	270	+After this configuration, the result would be as follows:
217	217
	272	+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.
	273	+
218	218	{{aagon.infobox}}
219		-Microsoft hat einen festgelegten Updatezyklus, nach dem es neue Releases gibt. Lesen Sie in dem Exkurs „[[//Update Zyklus: Wie kommt das Update von Microsoft auf den ACMP Client?//>>doc:ACMP.68.ACMP-Solutions.Patch Management.Windows Update Management.Exkurse und FAQ.Exkurs\: Update Zyklus\: Wie kommt das Update von Microsoft auf den ACMP Client?.WebHome]]“ nach, welche Schritte jeweils durchlaufen werden und wie die Test- und Freigabeprozesse dort einwirken.
	275	+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.69.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.
220	220	{{/aagon.infobox}}
221	221
222		-== Prioritäten der Test- und Freigabeprozesse ändern ==
	278	+== Changing the priorities of test and release processes ==
223	223
224		-Prioritäten von Test- und Freigabeprozesse können Sie ändern, sollten die gleichen Produkte in verschiedenen Prozessen vorkommen. Durch die Priorität wird geregelt, welche Updates zuerst verteilt werden können.
	280	+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.
225	225
226		-Die Priorität des jeweiligen Prozesses erkennen Sie innerhalb der Tabelle auf der linken Seite. Unterhalb der Sternchenspalte stehen die Zahlen für die Art der Priorität. Die Priorisierung funktioniert wie folgt: **Je kleiner die Zahl ist, desto höher ist die Priorität. **Verändern Sie die Reihenfolge, indem Sie die Pfeile ([[image:1733145433176-476.png]] ,[[image:1733145433176-745.png]] ,[[image:1733145433176-934.png]] ,[[image:1733145433177-660.png]] ) nutzen und die Prozesse an die jeweilige Stelle verschieben.
	282	+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.
227	227
228	228	{{box}}
229		-**Beispiel:** Das Produkt Microsoft Defender Antivirus (Windows > Microsoft Defender Antivirus) wird sowohl im Prozess „Microsoft Sicherheitsupdates“ als auch „Defender Test- und Freigabeprozess“ ausgewählt/verwendet. „Microsoft Sicherheitsupdates“ hat die Priorität 1, der „Defender Test- und Freigabeprozess“ die Priorität 6. Da es nur eine Zuordnung innerhalb des Test- und Freigabeprozess gibt, wird die mit der höchsten Priorität ausgewählt. Die Verteilung für die Updates erfolgt demnach über den „Microsoft Sicherheitsupdates“-Prozess.
	285	+**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.
230	230	{{/box}}
231	231
232		-[[Prioritäten der Test- und Freigabeprozesse ändern>>image:67_CAWUM Priorität Test- und Freigabeprozess_461.png]]
	288	+[[Change priorities of testing and release processes>>image:67_CAWUM Priorität Test- und Freigabeprozess_461.png]]