Wiki source code of Drittanbieterkataloge
Last modified by Sabrina V. on 2025/09/25 05:23
Show last authors
author | version | line-number | content |
---|---|---|---|
1 | {{aagon.floatingbox/}} | ||
2 | |||
3 | {{aagon.versionierungsbox}} | ||
4 | Third party catalogs are only supported in ACMP version 6.8. | ||
5 | In all prior versions, you can only purchase Microsoft products from the catalog. | ||
6 | {{/aagon.versionierungsbox}} | ||
7 | |||
8 | Third party catalogs enable you to provide updates from other providers within Windows Update Management. This includes the following manufacturers: | ||
9 | |||
10 | * HP | ||
11 | * Lenovo | ||
12 | * Dell | ||
13 | |||
14 | Thanks to the third-party extension, it is now possible to obtain updates and drivers from other providers directly via a single channel, without having to do so via a separate environment. | ||
15 | |||
16 | {{aagon.warnungsbox}} | ||
17 | Please note that in order to use third-party catalogs, you may need to allow certain URLs through your firewall. These URLs can be found in the [[Setup Checklist>>doc:ACMP.68.ACMP installieren.Checkliste zur Installation.WebHome||anchor="HErforderlicheURLs"]]. | ||
18 | {{/aagon.warnungsbox}} | ||
19 | |||
20 | |||
21 | = Integrate third party catalgues = | ||
22 | |||
23 | You can select which providers you want to include either in the //First Steps Wizard// or later in the //settings//. In both places, you can specify which catalog to integrate and which products can be distributed as updates. | ||
24 | |||
25 | {{aagon.infobox}} | ||
26 | Please observe the general notes for selecting [[products>>doc:ACMP.68.ACMP-Solutions.Patch Management.Windows Update Management.Konfigurationsmöglichkeiten im Windows Update Management.WebHome||anchor="HProdukte"]]. | ||
27 | {{/aagon.infobox}} | ||
28 | |||
29 | |(% style="width:350px" %)**Section**|(% style="width:1342px" %)**Description** | ||
30 | |(% style="width:350px" %)First Steps Wizard|(% style="width:1342px" %)If you want to include one or more third party catalogs during the initial configuration of the [[First Steps Wizards>>doc:ACMP.68.ACMP-Solutions.Patch Management.Windows Update Management.First Step Wizard des Windows Update Managements.WebHome]] (//Patch Management// > //Windows Update Management//) | ||
31 | you must open the //ManageThird Party Catalogs// button on the first page of the wizard, //Metadata download//. In the window, select the providers you want to include by checking the respective items. Click //OK// and continue with the regular steps in the First Steps Wizard. | ||
32 | |(% style="width:350px" %)Windows Update Management settings | ||
33 | (third party catalog)|(% style="width:1342px" %)To add or deselect providers retrospectively, navigate to the [[settings for the third party catalogs>>doc:ACMP.68.ACMP-Solutions.Patch Management.Windows Update Management.Einstellungen zum Windows Upodate Management.WebHome]]. Select the desired providers by pacing a tick in front of the respective entry. Save your changes and then start the [[Metadata download>>doc:ACMP.68.ACMP-Solutions.Patch Management.Windows Update Management.WebHome||anchor="HDownload-TypenimWindowsUpdateManagement"]] so that the newly added or deselected manufacturers are taken into account in the next server task. | ||
34 | |||
35 | [[Overview of third-party catalogs in the First Steps wizard and in the settings>>image:68_CAWUM_Drittanbieterkataloge Übersicht_1796.png||data-xwiki-image-style-alignment="center" height="544" width="1400"]] | ||
36 | |||
37 | |||
38 | |||
39 | = Special features of the individual provider catalogs = | ||
40 | |||
41 | Some of the third-party catalogs contain special features that you absolutely must be aware of for your work and take into account in order to ensure smooth operation. Please refer to the table below for the special features of each provider. | ||
42 | |||
43 | |(% style="width:133px" %)**Provider**|(% style="width:1559px" %)**Special feature** | ||
44 | |(% style="width:133px" %)Lenovo|(% style="width:1559px" %)((( | ||
45 | __Catalog agents__: | ||
46 | |||
47 | The manufacturer //Lenovo// has a catalog agent that you must install so that continuing updates are recognised correctly and are ready to use. | ||
48 | |||
49 | The agent is an update entry: After selecting the Lenovo catalog and products, you will find the agent in the update overview. It must then be installed on the devices by marking this entry as "Required". | ||
50 | |||
51 | |||
52 | __Installation behaviour__: | ||
53 | |||
54 | The installation status of the Lenovo agent is displayed as failed, even though it was completed successfully. This only affects the installation of the agent and the current version (Lenovo Updates Catalog Agent 1007). | ||
55 | |||
56 | We recommend that you place the Lenovo updates in a separate [[Windows Update Collection>>doc:ACMP.68.ACMP-Solutions.Patch Management.Windows Update Management.Windows Update Collection.WebHome]] so that they can be completed successfully separately. | ||
57 | ))) | ||
58 | |(% style="width:133px" %)HP|(% style="width:1559px" %)- | ||
59 | |(% style="width:133px" %)Dell|(% style="width:1559px" %)__Catalog agents__:((( | ||
60 | As with Lenovo, Dell also has its own catalog agent that you must install to ensure that updates are properly recognised and functional. | ||
61 | The agent is an update entry: after selecting the Dell catalog and products, you will find the agent in the update overview. It must then be installed on the devices by marking this entry as "Required". | ||
62 | \\__Installation behaviour__: | ||
63 | Although the update will generally not require a reboot after the initial installation, it is strongly recommended. This will ensure that the updates are recognised correctly. Please reboot after installing the agent update. | ||
64 | ))) | ||
65 | |||
66 | {{aagon.warnungsbox}} | ||
67 | When using third-party catalogs, only the //products// are currently taken into account, not the //classifications// and //languages//. | ||
68 | {{/aagon.warnungsbox}} | ||
69 | |||
70 | |||
71 | |||
72 | = Third party catalog settings = | ||
73 | |||
74 | In the settings section, select the third-party providers you want to include for the distribution of updates. Enable the respective checkboxes and then save the changes. Your updated selection will only be taken into account with the next Metadata download (manually via the dashboard in Windows Update Management or via a scheduled server task). | ||
75 | |||
76 | |||
77 | [[Settings of third party catalogs>>image:68_CAWUM_Drittanbieterkataloge_Übersicht_778.png]] | ||
78 | |||
79 | Then switch to //Products// (//Windows Update Management// > //Products//) and select the desired products to receive the corresponding updates. | ||
80 | |||
81 | |||
82 | |||
83 | = Setup signing = | ||
84 | |||
85 | If you want to use one or more third-party catalogs, you must sign these setups after downloading them. Signing is necessary for validating the loaded CAB files that are stored on the ACMP Server. A distinction is made between //self-signed //and //manual certificates//. Select the desired option and click on the respective radio button. | ||
86 | |||
87 | |**Option**|**Description** | ||
88 | |Self-signed certificate|The self-signed certificate is automatically generated and renewed by the server. It is also renewed and reissued upon expiry. The regular term of the certificate is one year. | ||
89 | |Manual certificate|((( | ||
90 | The certificate is provided and must be stored in the ACMP certificate store (//Manage computer certificates //> //Certificates – Local computer //> //ACMP //> //Certificates//). Please insert the certificate fingerprint (open certificate > //Details //tab > Fingerprint). | ||
91 | |||
92 | The certificate is not renewed manually, which means that the administrator must renew or replace it in good time. The term of validity is specified by the administrator when the certificate is created. | ||
93 | |||
94 | The validity of the fingerprint can be verified using the //Check //button. You can see the validity and serial number of the manual certificate. | ||
95 | ))) | ||
96 | |||
97 | {{aagon.warnungsbox}} | ||
98 | If you wish to use your own certificate, it must be inserted beforehand (see manual certificate), otherwise the server will automatically use the first option. | ||
99 | {{/aagon.warnungsbox}} | ||
100 | |||
101 | == Optional: Store certificate in ACMP folder == | ||
102 | |||
103 | {{aagon.infobox}} | ||
104 | The following section is an optional verification of the certificate and does not require any changes. ACMP stores the following certificate itself in the storage location. | ||
105 | {{/aagon.infobox}} | ||
106 | |||
107 | After successfully downloading the setup data, the ACMP folder appears for the first time under the //Manage Computer Certificates// storage location (//Manage Computer Certificates// > //Certificates - Local Computer//). | ||
108 | |||
109 | [[Certificate information>>image:68_CAWUM_ACMP Zertifikate verwalten_961.png]] | ||
110 | |||
111 | In this example, the certificate (ACMP WUM SelfSigned) contains all the usual certificate information you need to use it for Windows Update Management. It is important to note that it contains a private key. You can find this information either by looking at the icon or on the General page of the certificate once you open it. | ||
112 | \\The Details tab provides more info about the certificate (e.g. validity period, serial number and fingerprint). |