Skip to Content

Wiki source code of Abonnierte Software verwalten

Last modified by Sabrina V. on 2026/09/24 12:44
Show last authors
1 {{aagon.priorisierung}}
2 1
3 {{/aagon.priorisierung}}
4
5 {{aagon.floatingbox/}}
6
7 = Subscription List and Detailed View of Subscribed Packages =
8
9 Software packages can be subscribed to either in the First Steps Wizard or later in Managed Software (the tab of the same name). These are grouped into a list and can be selected and opened individually. The list of subscriptions represents the root level - that is, the products you have subscribed to or the available software. The level below the software displays the individual versions with their revisions. On the right-hand side, you’ll find the detailed view of the selected software.
10
11
12 [[Left-hand view of the subscribed product list>>image:69_Managed Software_Abonnierte Produktliste_1037.png||alt="69_Managed Software Produktebene MSW_1026.png"]]
13
14 The detail view is divided into three tabs:
15
16 |**Tab name**|**Detailed Information**
17 |General Information|Contains manufacturer information about the software package, the version and publish dates, as well as a description of the software's functions and, if applicable, optional files.
18 |Parameter|Contains software-specific parameters that can be configured individually. The parameter values can be changed directly within the view (see also “Configuring Parameters of a Software Package”).
19 |Affected Clients|Contains a list of all clients on which the Managed Software Scanner has detected an installation. This information is provided and retrieved based on the definition files and can therefore indicate when, for example, an update is needed on a client. Using the icons in the window, you can execute jobs on selected or all Clients, or rescan the Clients. If there are multiple versions of the software and you have subscribed to more than one, you can also find a specific version (“Visible Versions”).
20
21 The info in the detailed view is only visible at the root level. Once you navigate to a specific software version (e.g., //7-Zip 64-bit 26.03.00.0//), you will find more info about the software version and the revision (see also the section //Configuring Software Versions//). The following picture shows the 7-Zip 64-bit version as an example.
22
23 [[Detailed view of the root level>>image:69_Managed Software_Versionsebene 2_1109.png||alt="69_Managed Software_Versionsebene 1035.png"]]
24
25 (% class="wikigeneratedid" %)
26 From this view, you can view general information about the software and its version, and download optional files. Learn more about how to [[configure software versions>>||anchor="HConfigureSoftwareVersions"]].
27
28 == Configuring Software Package Parameters ==
29
30 Each software package has its own parameters that you can customize as needed. These parameters apply only to the selected package and are valid for all available versions of that software.
31
32 {{box}}
33 **What are parameters?**
34 In the context of Managed Software, parameters are properties and configuration values used to individually control and customize software packages before installation or execution. They allow you to define default settings such as actions (e.g., installing or uninstalling new software), language settings, or even Shortcuts without changing the software package itself.
35 Parameters can also include acmp-specific actions (e.g., executing a specific scanner) or general user actions (e.g., creating a Shortcut on the desktop or in the Start menu).
36 Additional parameter examples:
37
38 * Enter license key (the administrator enters the license key for the software during the preparation phase for software distribution)
39 * Disable automatic updates
40 * Have the user close any open software or windows
41 * Language (which language options should the user be able to select after the software is deployed in order to install it?)
42 * Installation path (where should the software be saved?)
43 {{/box}}
44
45 [[Sample view of the parameters for the “7-Zip 64-bit” software>>image:69_Managed Software Beispiel Parameter 7-Zip_930.png]]
46
47 The parameter view is organized in a table and includes, among other things, info on the version starting with which these parameters are valid, their status, and whether an acmp Kiosk option is available. To change a parameter, click on the entry. A dialog box will open where you can change the various parameter values.
48
49 |**Parameter Name**|**Parameter Value**
50 |Value|(((
51 The values specified here are used as default values for all jobs created from this point forward. Changes to the default values do not affect the parameter values of existing jobs.
52
53 A parameter value may include, among other things, the activation of a checkbox, the selection of a predefined value from a drop-down menu, or the specification of an installation path.
54 )))
55 |(((
56
57
58 acmp Kiosk Option
59 )))|(((
60 This setting determines the visibility and editability of the parameter for the end user in the acmp Kiosk.
61
62 |Invisible (Default)|The parameter is not displayed to the user in the acmp Kiosk.
63 |Read-only|The parameter is displayed to the user in the acmp Kiosk, but cannot be customized.
64 |Editable|The parameter is displayed to clients in the acmp Kiosk and can be customized.
65 )))
66
67 [[Change the value for the “Create a shortcut in the Start menu” parameter>>image:69_Managed Software Parameterwerte ändern_553.png]]
68
69 To reset any changes to the default settings, use the //Reset to Default// button. Click //Save// to provide confirmation of the parameter changes.
70
71 = Configure Software Versions =
72
73 In Managed Software, you'll find both the current and older software versions for each subscribed software package. To do this, select a subscribed software package from the list and click the arrow to the left of the software icon to expand the list of versions. This allows you to view all available versions of the software package, sorted by recency and revision number.
74
75 {{box}}
76 **What does the revision number of a software package mean?**
77 A revision indicates that there is an updated Managed Software Package available for the selected software version. If a package is available for subscription for the first time, a (1) appears in parentheses. A higher number indicates that the acmp Package Factory has, for example, attached a document to the package where you can find more information (e.g., a virus report or a checklist). If something changes in the manufacturer’s (functional/content) version, a new version is created. The revision number refers only to the change made by aagon.
78 {{/box}}
79
80 Now find the version you want to configure. The details of the selected version are displayed in the right-hand window next to the subscription list. You can switch between two tabs: //General// and //Tests//.
81
82 |(% style="width:143px" %)**Tab name**|(% style="width:1549px" %)**Detail information**
83 |(% style="width:143px" %)General|(% style="width:1549px" %)(((
84 Contains the manufacturer's information regarding the software version, as well as a description of the software's functionality, any release notes, general distribution information, and optional files for that version.
85
86 |(((
87 **What are optional files?**
88
89 If an optional file has been attached to a specific software version, you can download that file. If necessary, the aagon Package Factory attaches a file to a specific package. This file may contain, for example, a short documentation, a test report, or a virus report.
90 )))
91 )))
92 |(% style="width:143px" %)Tests|(% style="width:1549px" %)(((
93 Contains the results of Managed Software jobs that have already been run. For more information, see the section [[Tracking Managed Software Jobs in the Monitors>>doc:ACMP.610.ACMP-Solutions.Patch Management.Managed Software.Konfigurationsmöglichkeiten für Managed Software.WebHome||anchor="HTrackManagedSoftwareJobsintheMonitors"]].
94 )))
95
96
97
98 = Manually Specifying a Distribution Ring for a Version =
99
100 Distribution rings allow you to specify the ring in which a particular version of a software package should be initially deployed. This can be useful, for example, if you first want to make a new software version available to a small group of Clients to check whether it is fully functional. If problems arise, only a manageable number of Clients would be affected, and you, as the administrator, could roll back to an older version. However, if the software package works as expected, another group of Clients (consisting of more employees) could receive the next distribution ring.
101
102 Deployment rings help you identify incompatibilities and resolve them early on. This allows you to deploy specific versions of a software package to your Clients one ring at a time.
103
104 [[image:1790146129566-176.png||data-xwiki-image-style-alignment="center"]]
105
106 You can tell which distribution ring a version is currently in by looking at the icon.
107
108 |=(% style="width: 155px;" %)Icon|=(% style="width: 921px;" %)Meaning
109 |(% style="width:155px" %)[[image:TestRing_NoRing.svg||height="24" width="24"]] No Ring|(% style="width:921px" %)The software version has not yet been assigned to a ring and is therefore not being deployed.
110 |(% style="width:155px" %)[[image:TestRing_One.svg||width="24"]] Test Ring 1|(% style="width:921px" %)The software version is in Test Ring 1 and can be used via appropriately configured containers.
111 |(% style="width:155px" %)[[image:TestRing_Two.svg||height="24" width="24"]] Test Ring 2|(% style="width:921px" %)The software version is in Test Ring 2 and can be used via appropriately configured containers.
112 |(% style="width:155px" %)[[image:TestRing_Release.svg||height="24" width="24"]] Approved|(% style="width:921px" %)The software version has been released and can be deployed to all Clients via appropriately configured containers.
113 |(% style="width:155px" %)[[image:ClientCommandProperties_Condition.ico||height="24" width="24"]] Denied|(% style="width:921px" %)The software version has been denied and must be approved again before it can be used.
114
115 {{aagon.infobox}}
116 You can also [[deny versions full or re-approve rejected versions>>||anchor="HApprovingandDenyingSoftwareVersions"]].
117 {{/aagon.infobox}}
118
119 = Manage Subscription Software =
120
121 You can view the software you have subscribed to on the “Managed Software” tab and manage it using the ribbon bar. Here, you can add new software to your subscription ([[image:1790146253339-584.png]]) or cancel existing packages ([[image:1790146253340-434.png]]).
122
123 == Subscribe to and Unsubscribe from Software Packages ==
124
125 Click the button on the ribbon bar [[image:1790146274772-816.png]] //Subscribe// to subscribe to additional packages. A dialog box will open to display the available software packages. Using the top bar, you can navigate the catalog ([[image:1790146274773-516.png]]) or, if necessary, just refresh the view ([[image:1790146274773-582.png]]). Otherwise, use the search function to find a specific entry, or refine your filters by specifying the category and/or license type. If you check the //Show Subscriptions// checkbox, the packages already selected will be displayed as subscribed in the list below.
126
127 Now find the desired managed software packages from the catalog and click //Subscribe// at the bottom.
128
129 {{box}}
130 **Tip**: If you want to select multiple packages at once, you can do so by selecting multiple items (Ctrl + left-click).
131 {{/box}}
132
133 {{aagon.infobox}}
134 Please note that some Managed Software programs have prerequisites that must be met for successful installation. Any prerequisites are listed individually for each software program under the //General Information// > //Description// tab.
135 {{/aagon.infobox}}
136
137 [[Subscribe to new packages in Managed Software>>image:69_Managed Software Neue Softwarepakete abonnieren_1026.png]]
138
139 To cancel a subscription to a Managed Software package, simply select the desired entry from the list and click// //[[image:1790146392046-742.png]] //Cancel Subscription //on the ribbon bar. Confirm the security prompt, and the subscription will be canceled.
140
141 {{aagon.warnungsbox}}
142 Please note that unsubscribing from a software package will delete all job links to that Managed Software in containers, in the acmp Kiosk, and in the Job Collections.
143 {{/aagon.warnungsbox}}
144
145
146 = Sync Profiles in Managed Software =
147
148 Just as in Windows Update Management - the second solution for patch management - Sync Profiles are also available in Managed Software. These can be accessed via the //Managed Software// tab on the ribbon bar ([[image:1790146475559-166.png]]).
149
150 Sync profiles are filter and control configurations that specify which software packages are to be synchronized from the Server to the deployed file repositories.
151
152 {{box}}
153 **What are sync profiles used for?**
154
155 Sync profiles are filter and control configurations that determine which software packages should be synchronized from the Server to the deployed file repositories.
156 It is important that at least one sync profile is linked (either one you created yourself or the default profile), because otherwise the Managed Software cannot be synchronized to the respective location.
157 {{/box}}
158
159 == Add Sync Profile ==
160
161 To create a new sync profile for Managed Software, click [[image:1790146511066-422.png]] //Add//.
162
163 A three-page wizard will open; on the first page, you’ll need to enter a name. Name the sync profile and click //Next >//. On the next page, you must specify which Managed Software to include and synchronize. You can choose between two options: include all subscribed Managed Software or only selected ones. Use the radio button to select the desired option.​
164
165 |Include all subscribed Managed Software|This filter links all items in your subscribed packages to the sync profile.
166 |Include only selected Managed Software|(((
167 With this option, you must explicitly select the packages from your list of subscribed software that you want to link to the new sync profile you are creating. To do this, use the [[image:1790146511066-958.png]] //Link Element Statically //button and select the appropriate software from your subscriptions. To remove an element click [[image:1790146511066-658.png]].
168 )))
169
170 Continue by clicking //Next > //again.
171
172 [[Filters for linking managed software packages to the sync profile>>image:69_Managed Software Sync-Profil hinzufügen_735.png]]
173
174 On the last page, you can now specify the file repositories that should use this sync profile. To do so, click [[image:1790147100082-830.png]]// Add Lnk to File Repository,// select the repository from the list of existing repositories and then click //OK//. To delete a link, select the entry from the list and click [[image:1790147100083-481.png]] //Delete Link to File Repository//.
175
176 {{box}}
177 **Tip**: If necessary, refer to the chapter „[[Distributed File Repositories>>doc:ACMP.610.ACMP-Solutions.System.Verteilte File Repositories.WebHome]]“ for more details - for example, if you want to create a new file repository for Managed Software.
178 {{/box}}
179
180 Exit editing the sync profile and click //Done//. The new entry will appear in the list. Using the top bar, you can add additional profiles, make changes to existing ones if needed ([[image:1790147160174-397.png]]) or delete them entirely ([[image:1790147160175-120.png]]).
181
182 Each sync profile consists of three tabs where you can view the filter (whether all or only selected managed software has been included), as well as the linked file repository and the respective items for the subscriptions to be distributed.
183
184 [[Added sync profiles>>image:69_Managed Software Sync-Profil Liste_734.png]]
185
186 = Approving and Denying Software Versions =
187
188 From time to time, it may be necessary or appropriate to deny a software version as part of your daily work (see also the box below for possible reasons). To do this, go to the //Managed Software// tab and select the software you want to deny from the list of subscriptions on the left.Click the arrow next to the software ([[image:1790147226501-124.png]]) to open the versions, and then click [[image:1790147226504-126.png]] //Deny// on the ribbon bar.
189
190 [[Deny Software Version>>image:69_Managed Software Software verweigern_1280.png]]
191
192 A window will open where you can enter a comment explaining why this software version should be denied.
193
194 {{aagon.infobox}}
195 A denied software version is neither deployed to the Clients nor installed on them.
196 {{/aagon.infobox}}
197
198 [[Comment on a software version that has been denied>>image:69_Managed Software_Version verweigern Fenster_476.png]]
199
200 Specify the reason, confirm the action, and click //OK//. The icon next to the software version will be updated (in this case, it changes from [[image:1790147476105-710.png]] //No Ring// to [[image:1790147476106-529.png]] //Denied//).
201
202 {{box}}
203 **When does it make sense to deny a software version?**
204
205 For example, it may make sense to deny a software version if a current version is no longer compatible with your system, meaning that a program would no longer be usable if you were to update it (the environment and software are no longer compatible). However, this should be checked and determined on a case-by-case basis within your own environment.
206 {{/box}}
207
208 To re-release or re-approve a software version, select the entry from the subscription list again and click [[image:1790147509922-889.png]] //Approve// on the ribbonbar. Confirm the dialog box that appears, and the version will be re-released.
209
210
211 = Changing the Manual Distribution Ring for Software Packages =
212
213 The distribution ring indicates the current transition phase a software package is in and how far the automatic deployment has progressed. There are a total of four rings that a Managed Software package can go through: //No Distribution Ring//, //Test Ring 1//, //Test Ring 2//, and //Released.//
214
215
216 Software packages that are already in the release process and have been assigned a distribution ring (Test Ring 1 or Test Ring 2) can have their distribution ring manually changed via the ribbon bar or the context menu. This may be necessary, for example, if a software package or a specific software version needs to be moved to a different ring so that it can be deployed more quickly. First, select the software for which you want to manually change the ring from the subscription list, and then click [[image:1790147550876-849.png]] //Change Distribution Ring//. The distribution ring editor opens, where you can now select the new distribution ring for the software package. Also, make sure the //Automatically move items to the next distribution ring// checkbox is enabled so that this automatic process takes effect and the software package is moved to the next ring at a later time. Exit your changes by clicking //Change//.
217
218 {{box}}
219 **Tip**: You can only manually change a distribution ring once the software has been downloaded or the status shows as “Synchronized.”
220 {{/box}}
© Aagon GmbH 2026
Besuchen Sie unsere aagon-Community