Changes for page Einstellungen zum Windows Update Management

Last modified by Sabrina V. on 2026/06/09 11:39

From 7.1 to 8.1

From version 8.1

edited by Sabrina V.
on 2025/12/09 09:04

Change comment: There is no comment for this version

To version 16.1

edited by Sabrina V.
on 2026/06/09 11:39

Change comment: There is no comment for this version

Raw
Rendered

Summary

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

Details

Page properties

Content

@@ -2,20 +2,24 @@
  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.
--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.
++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.
--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.
++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.
  = Products =
--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:
++The settings you have already made in the [[First Steps Wizard>>doc:ACMP.610.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:
--* [[Products>>doc:ACMP.69.ACMP-Solutions.Patch Management.Windows Update Management.First Step Wizard des Windows Update Managements.WebHome||anchor="HProducts"]]
--* [[Classifications>>doc:ACMP.69.ACMP-Solutions.Patch Management.Windows Update Management.First Step Wizard des Windows Update Managements.WebHome||anchor="HClassifications"]]
--* [[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)
++* [[Products>>doc:ACMP.610.ACMP-Solutions.Patch Management.Windows Update Management.First Step Wizard des Windows Update Managements.WebHome||anchor="HProducts"]]
++* [[Classifications>>doc:ACMP.610.ACMP-Solutions.Patch Management.Windows Update Management.First Step Wizard des Windows Update Managements.WebHome||anchor="HClassifications"]]
++* [[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)
--[[Settings for products, classifications and languages>>image:68_CAWUM_Einstellungen_Produkte_1658.png]]
++[[Settings for products, classifications and languages>>image:610_CAWUM_Einstellungen_Produkte_1658.png]]
++{{aagon.versionierungsbox}}
++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.
++{{/aagon.versionierungsbox}}
++
  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.
  = Options =
@@ -22,7 +22,7 @@
  == Update download options ==
--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:
++Windows Update Management downloads the available updates to your [[File Repository>>doc:ACMP.610.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:
  |**Download type**|**Description**|
  |**On Demand – only download if at least one Client needs the Update**|This is the default setting, which is also recommended.
@@ -37,16 +37,16 @@
  {{/aagon.warnungsbox}}
  )))| [[image:67_CAWUM_Option immer herunterladen_578.png||height="75" width="545"]]
--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"]].
++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"]].
  {{aagon.infobox}}
  Please note the free storage space on your distributed file repositories.
--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"]].
++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"]].
  {{/aagon.infobox}}
  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.
--[[Update download Options>>image:68_CAWUM Einstellungen Update-Download-Optionen_1337.png||alt="67_CAWUM Einstellungen Update-Download-Optionen_1337.png"]]
++[[Update download Options>>image:610_CAWUM Einstellungen Update-Download-Optionen_1251.png||alt="610_CAWUM Einstellungen Update-Download-Optionen_1337.png"]]
  == Special feature: //Always download updates for these products and classifications// ==
@@ -66,7 +66,7 @@
  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.
--[[On-demand settings for downloading updates>>image:67_CAWUM Download-Typ On Demand_932.png]]
++[[On-demand settings for downloading updates>>image:610_CAWUM Download-Typ On Demand_932.png]]
  {{aagon.infobox}}
  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.
@@ -104,7 +104,7 @@
  [[Windows Update Management settings>>image:69_CAWUM Einstellungen_Optionen2_1070.png||alt="67_CAWUM Einstellungen_Optionen2_1070.png"]]
--== Automatic declination of Updates ==
++= Automatic declination of Updates =
  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.
  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.
@@ -113,7 +113,7 @@
  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.
  {{/aagon.infobox}}
--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]].
++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]].
  [[Filter for automatic decline of updates >>image:69_CAWUM_FIlter Konfiguration für das automatische Verweigern_965.png]]
@@ -122,7 +122,7 @@
  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.
  {{box}}
--**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]].
++**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.610.ACMP-Solutions.Client-Management.Container.Container verwalten.Arbeiten mit den Filtertypen.WebHome]].
  {{/box}}
  Examples:
@@ -151,7 +151,7 @@
  **Example: "Reject Windows 11 22H2 updates"**
--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.
++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.
  [[image:69_CAWUM Filter 4.png||data-xwiki-image-style-alignment="center"]]
@@ -173,7 +173,7 @@
  = Third Party Catalogues =
  Third party catalogues can also be used to obtain updates from providers other than Microsoft.
--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]].
++These currently include updates from //HP//, //Lenovo //and //Dell//. Read more about third party catalogues [[here>>doc:ACMP.610.ACMP-Solutions.Patch Management.Windows Update Management.Drittanbieterkataloge.WebHome]].
  = Test and Release =
@@ -180,7 +180,7 @@
  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.
  {{box}}
--**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.
++**Tip: **Read the excurses //[[How are products and classifications related in ACMP?>>doc:ACMP.610.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.
  {{/box}}
  With the delivery of ACMP, a default test and release process is defined, whereby updates are released directly.
@@ -209,7 +209,7 @@
  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.
  {{aagon.infobox}}
--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.
++Please note that you can **ONLY **select products that you have checked in the [[First Steps Wizard>>doc:ACMP.610.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.
  {{/aagon.infobox}}
  {{box}}
@@ -216,10 +216,22 @@
  **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.
  {{/box}}
--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.
++In this example, the release process for the product //Office// > //Microsoft 365 Apps/Office 2019/Office LTSC// is to be determined. You can use the [[filter mode>>doc:ACMP.610.ACMP-Solutions.Patch Management.Windows Update Management.Windows Update Collection.WebHome||anchor="HAddWindowsUpdateCollection"]] (standard filter or advanced filter) to define the content.
--[[Define content for testing and release>>image:67_Einstellungen_Inhalte für Test und Freigabe_966.png]]
++{{box}}
++**Info**: When using the advanced filter, you can create a filter for the content directly by using the SingleValue or MultiValue fields.
++{{/box}}
++Using the filter at the bottom, you can select whether you want to display all checked or suggested products.
++
++{{box}}
++**Info**: Using the “Suggested” column, you can see directly from the product list whether a product is suggested for the filter or not.
++{{/box}}
++
++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.
++
++[[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"]]
++
  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.
  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.
@@ -272,7 +272,7 @@
  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.
  {{aagon.infobox}}
--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.
++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.
  {{/aagon.infobox}}
  == Changing the priorities of test and release processes ==