Changes for page acmp Server
Last modified by Sabrina V. on 2026/10/06 10:47
From version 3.1
edited by Sabrina V.
on 2026/07/29 07:30
on 2026/07/29 07:30
Change comment:
There is no comment for this version
To version 5.1
edited by Sabrina V.
on 2026/10/06 10:47
on 2026/10/06 10:47
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 - ACMPServer1 +acmp Server - Content
-
... ... @@ -4,15 +4,15 @@ 4 4 5 5 {{aagon.floatingbox/}} 6 6 7 -= The ACMPServer =7 += The acmp Server = 8 8 9 -This section allows you to reduce the load on your ACMPServer.9 +This section allows you to reduce the load on your acmp Server. 10 10 11 11 {{figure}} 12 -[[image:68_System_Einstellungen_Allgemein_1560.png||alt="ACMP Server - Performance Einstellungen3.png" data-xwiki-image-style-alignment="center"]] 12 +[[image:68_System_Einstellungen_Allgemein_1560.png||alt="ACMP Server - Performance Einstellungen3.png" data-cmp-info="10" data-xwiki-image-style-alignment="center"]] 13 13 14 14 {{figureCaption}} 15 - ACMPServer - Performance Settings15 +acmp Server - Performance Settings 16 16 {{/figureCaption}} 17 17 {{/figure}} 18 18 ... ... @@ -32,19 +32,19 @@ 32 32 |Allocated threads for the console queue|If you have many consoles running at the same time, delays may occur when there are a large number of concurrent requests. This can happen, for example, when many consoles are using the Helpdesk. If delays occur in the console, you can increase the number of threads to alleviate the load. 33 33 |Allocated threads for the Web Interface queue|The Web Interface queue occurs when many browsers in your environment are accessing the Web Interface at the same time, causing delays. In this case, increasing the number of threads may help. 34 34 |Allocated threads for agent in rollout queue|The difference between the agent queue and the agent rollout queue is that the latter explicitly refers to the Clients that are assigned a Rollout. 35 -|Allocated threads for the ACMPKiosk queue|This queue is used, for example, when you want to install Client Commands, Job Collections, or Managed Software via your clients and theACMPKiosk.35 +|Allocated threads for the acmp Kiosk queue|This queue is used, for example, when you want to install Client Commands, Job Collections, or Managed Software via your clients and the acmp Kiosk. 36 36 37 37 38 38 39 39 === Checking Queues for Overload === 40 40 41 -You can use Performance Monitor to check whether the queues are overloaded. To do this, add a new performance counter using the //Performance Monitor// service and select the // ACMPServer// instance.41 +You can use Performance Monitor to check whether the queues are overloaded. To do this, add a new performance counter using the //Performance Monitor// service and select the //acmp Server// instance. 42 42 43 43 {{figure}} 44 -[[image:Performance Leistungen.png||data-xwiki-image-style-alignment="center"]] 44 +[[image:Performance Leistungen.png||data-cmp-info="10" data-xwiki-image-style-alignment="center"]] 45 45 46 46 {{figureCaption}} 47 -Add ACMPServer as a Performance Indicator47 +Add acmp Server as a Performance Indicator 48 48 {{/figureCaption}} 49 49 {{/figure}} 50 50 ... ... @@ -52,18 +52,18 @@ 52 52 53 53 === **Port Settings** === 54 54 55 -The port settings allow you to customize the port for server communication with the ACMP Console.55 +The port settings allow you to customize the port for server communication with the acmp Console. 56 56 57 57 To change the port, first enable the “Use alternative port” checkbox. Then enter the desired port number. 58 58 59 59 {{aagon.infobox}} 60 -Before you can block connections from the ACMP Console to theACMPServer via the default port, you must ensure that theACMP Console is connected to theACMPServer via the alternate port.60 +Before you can block connections from the acmp Console to the acmp Server via the default port, you must ensure that the acmp Console is connected to the acmp Server via the alternate port. 61 61 {{/aagon.infobox}} 62 62 63 63 If you've changed the port, save your settings. 64 64 65 65 {{aagon.infobox}} 66 -Access via the default port is possible at any time using the ACMP Console installed on theACMPServer.66 +Access via the default port is possible at any time using the acmp Console installed on the acmp Server. 67 67 {{/aagon.infobox}} 68 68 69 69 == Console Login Settings == ... ... @@ -73,10 +73,10 @@ 73 73 74 74 = Active Directory = 75 75 76 - ACMPcan read user and group information from Active Directory. To do this, you need a user account with read permissions in the domain.76 +acmp can read user and group information from Active Directory. To do this, you need a user account with read permissions in the domain. 77 77 78 78 {{figure}} 79 -[[image:69_System_Einstellungen_ActiveDirectory_1560.png||alt="68_System_Einstellungen_ActiveDirectory_1560.png" data-xwiki-image-style-alignment="center"]] 79 +[[image:69_System_Einstellungen_ActiveDirectory_1560.png||alt="68_System_Einstellungen_ActiveDirectory_1560.png" data-cmp-info="10" data-xwiki-image-style-alignment="center"]] 80 80 81 81 {{figureCaption}} 82 82 System Settings: Active Directory ... ... @@ -88,7 +88,7 @@ 88 88 Enter the required information under Active Directory. To do this, click the //Change// button and enter the domain, username, and password to be used. You can also choose whether to use encryption for Active Directory (SSL/TLS), which encrypts the data being transmitted. You can enter additional information in the “Description” field. If you want to use a static IP address to connect to a specific domain controller, you must enable the corresponding checkbox. It is advisable to use a static IP address (domain controller IP or global catalog IP) if, for example, the domain controller cannot be resolved using Windows’ built-in mechanisms. Otherwise, you can disable the field. 89 89 90 90 {{figure}} 91 -[[image:69_Einstellungen_Eigenschaften der Anmeldeinformationen_402.png||alt="63_Einstellungen_ActiveDirectory_EigenschaftenderAnmeldeinformationen_340.png" data-xwiki-image-style-alignment="center"]] 91 +[[image:69_Einstellungen_Eigenschaften der Anmeldeinformationen_402.png||alt="63_Einstellungen_ActiveDirectory_EigenschaftenderAnmeldeinformationen_340.png" data-cmp-info="10" data-xwiki-image-style-alignment="center"]] 92 92 93 93 {{figureCaption}} 94 94 Credential Properties ... ... @@ -102,14 +102,14 @@ 102 102 103 103 * Under “User Domain,” enter the FQDN (Fully Qualified Domain Name) and not “just” the NetBIOS name. In this example, it is the internal Windows domain (//aagon.local//). 104 104 * Use SSL/TLS as the encryption method to secure data transmission. 105 -* Ensure that the client executing the Query is a domain member (for example, in the case of this AD login, that would be the ACMPServer).106 -* Additional examples: For kiosk visibility, the client must be a domain member; for Client Commands, the executor itself must be a domain member (either the ACMP Console or the ACMP Agent).105 +* Ensure that the client executing the Query is a domain member (for example, in the case of this AD login, that would be the acmp Server). 106 +* Additional examples: For kiosk visibility, the client must be a domain member; for Client Commands, the executor itself must be a domain member (either the acmp Console or the acmp Agent). 107 107 108 108 Only by following the recommendations above can you ensure that Windows uses Kerberos for authentication and does not fall back on NTLM. 109 109 {{/box}} 110 110 111 111 {{aagon.infobox}} 112 -Please note that you can only use LDAPS in ACMPif both the server and the console are in the same domain; otherwise, the certificates will not be transferred. If you are in a workgroup, LDAP may work, but the encrypted version (LDAPS) will not, as a domain is required for this.112 +Please note that you can only use LDAPS in acmp if both the server and the console are in the same domain; otherwise, the certificates will not be transferred. If you are in a workgroup, LDAP may work, but the encrypted version (LDAPS) will not, as a domain is required for this. 113 113 {{/aagon.infobox}} 114 114 115 115 == Multiple Domains == ... ... @@ -119,9 +119,9 @@ 119 119 120 120 == Active Directory Login == 121 121 122 -You can import Active Directory users into the ACMP[[User Management>>doc:ACMP.610.ACMP-Solutions.System.Benutzerverwaltung.WebHome]] module. This means that user account management is configured entirely in Active Directory, but permissions are still managed in theACMPUser Management module.122 +You can import Active Directory users into the acmp [[User Management>>doc:ACMP.610.ACMP-Solutions.System.Benutzerverwaltung.WebHome]] module. This means that user account management is configured entirely in Active Directory, but permissions are still managed in the acmp User Management module. 123 123 124 -To enable ACMPlogin for AD users, enable the checkbox labeled //EnableACMPConsole Login for Active Directory Users//. Additionally, you must configure theACMPaccess group “AD Login” and assign to it the AD groups that are permitted to log in to ACMP. To do this, click the link displayed under the “Access Groups” heading and navigate to user management to customize the access group. Now assign the groups from your domains - which are permitted to log in to the ACMP Console - to the ACMP group “AD Login.”124 +To enable acmp login for AD users, enable the checkbox labeled //Enable acmp Console Login for Active Directory Users//. Additionally, you must configure the acmp access group “AD Login” and assign to it the AD groups that are permitted to log in to ACMP. To do this, click the link displayed under the “Access Groups” heading and navigate to user management to customize the access group. Now assign the groups from your domains - which are permitted to log in to the ACMP Console - to the ACMP group “AD Login.” 125 125 126 126 {{aagon.infobox}} 127 127 Please note that you can only select a domain after you have first created a user account with the appropriate read permissions under [[Active Directory>>doc:||anchor="HActiveDirectory"]]! ... ... @@ -129,15 +129,15 @@ 129 129 130 130 == LDAP Result Cache == 131 131 132 -The LDAP Result Cache allows you to specify how long the ACMPServer should cache the results of LDAP Queries. The default value is 15 minutes; you can enter up to 120 minutes as the maximum cache lifetime.132 +The LDAP Result Cache allows you to specify how long the acmp Server should cache the results of LDAP Queries. The default value is 15 minutes; you can enter up to 120 minutes as the maximum cache lifetime. 133 133 134 134 == Importing AD Users == 135 135 136 -To import an AD user, you must first add an AD account via //System > Settings > ACMPServer > Active Directory//. Then configure an [[AD-Login>>doc:||anchor="HActiveDirectoryLogin"]] and select an AD group. Next, in user management, import the desired AD users.136 +To import an AD user, you must first add an AD account via //System > Settings > acmp Server > Active Directory//. Then configure an [[AD-Login>>doc:||anchor="HActiveDirectoryLogin"]] and select an AD group. Next, in user management, import the desired AD users. 137 137 138 -== Convert Existing ACMPUsers to AD Users ==138 +== Convert Existing acmp Users to AD Users == 139 139 140 -If AD login is enabled at a later date, the existing ACMPusers can be converted to AD users. The conversion is performed using ADUserMigrate.exe, which is located in theACMPserver directory. Run the executable from the Command line. First specify theACMPUser, then the AD User (e.g., “C:\Program Files (x86)\Aagon\ACMP Server\ADUserMigrate.exe” tester [[tester@domain.local>>mailto:tester@domain.local]]). Once the execution has been completed, the users will be converted.140 +If AD login is enabled at a later date, the existing acmp users can be converted to AD users. The conversion is performed using ADUserMigrate.exe, which is located in the acmp server directory. Run the executable from the Command line. First specify the acmp User, then the AD User (e.g., “C:\Program Files (x86)\Aagon\ACMP Server\ADUserMigrate.exe” tester [[tester@domain.local>>mailto:tester@domain.local]]). Once the execution has been completed, the users will be converted. 141 141 142 142 == **Allowing Additional Users from a Trusted Domain** == 143 143 ... ... @@ -144,7 +144,7 @@ 144 144 If you want to allow additional users from a trusted domain - hat is, another trusted domain - you must grant the querying AD user read permissions on the //ForeignSecurityPrincipal// object and its child objects. 145 145 146 146 {{figure}} 147 -[[image:Erweiterte Sicherheitseinstellungen für „ForeignSecurityPrincipals“.png||data-xwiki-image-style-alignment="center" height="509" width="750"]] 147 +[[image:Erweiterte Sicherheitseinstellungen für „ForeignSecurityPrincipals“.png||data-cmp-info="10" data-xwiki-image-style-alignment="center" height="509" width="750"]] 148 148 149 149 {{figureCaption}} 150 150 Advanced Security Settings for “ForeignSecurityPrincipals” ... ... @@ -153,10 +153,10 @@ 153 153 154 154 To do this, enable the advanced features in your //Active Directory Users and Computers// MMC. On the //Security// tab of the //ForeignSecurityPrincipal// container, click //Advanced// to view all users and groups that already have access to this object. Using //Add//, you can then add the user who should have access to the Trusted Domain. Make sure that the user is granted Read permissions (these are usually already selected) and that the permissions are applied to //This object and all child objects//. 155 155 156 -This user must then also be added in ACMPunder //Settings// > //ACMPServer// > //Active Directory//.156 +This user must then also be added in acmp under //Settings// > //acmp Server// > //Active Directory//. 157 157 158 158 {{aagon.infobox}} 159 -Please note that the logon group you have defined in ACMPmust be a domain-local group. The users you add to the logon group from the Trusted Domain must be directly linked to this group. You cannot specify a group from the Trusted Domain here, because the LDAP search does not allow for nested objects from Trusted Domains at this point.159 +Please note that the logon group you have defined in acmp must be a domain-local group. The users you add to the logon group from the Trusted Domain must be directly linked to this group. You cannot specify a group from the Trusted Domain here, because the LDAP search does not allow for nested objects from Trusted Domains at this point. 160 160 {{/aagon.infobox}} 161 161 162 162 ... ... @@ -165,7 +165,7 @@ 165 165 On this page, you can enter the connection details for your email service and the server. This allows emails to be retrieved automatically and saved as tickets. Emails can also be sent automatically, for example, during automatic ticket generation or when a specific escalation level is reached (see [[Escalations>>doc:ACMP.610.ACMP-Solutions.System.Einstellungen.Helpdesk.WebHome||anchor="HEscalations"]] and [[Rules>>doc:ACMP.610.ACMP-Solutions.System.Einstellungen.Helpdesk.WebHome||anchor="HRules"]]). 166 166 167 167 {{figure}} 168 -[[image:68_Einstellungen_E-Mail Service Allgemein_1716.png||alt="33c_64_System_Einstellungen_E-MailService_1395.png" data-xwiki-image-style-alignment="center"]] 168 +[[image:68_Einstellungen_E-Mail Service Allgemein_1716.png||alt="33c_64_System_Einstellungen_E-MailService_1395.png" data-cmp-info="10" data-xwiki-image-style-alignment="center"]] 169 169 170 170 {{figureCaption}} 171 171 Settings: Email Service ... ... @@ -204,7 +204,7 @@ 204 204 ))) 205 205 206 206 {{aagon.infobox}} 207 -Read here to learn how to set up [[Setp Up OAuth2 for the ACMPServer's email service>>doc:.OAuth2 am ACMP Server einrichten.WebHome]].207 +Read here to learn how to set up [[Setp Up OAuth2 for the acmp Server's email service>>doc:.OAuth2 am ACMP Server einrichten.WebHome]]. 208 208 {{/aagon.infobox}} 209 209 210 210 Under “Inbox Folder,” you can enter a caption; the default is //INBOX//. If you want to delete emails after retrieving them from the Server, you can check the checkbox with the same name. ... ... @@ -234,9 +234,9 @@ 234 234 235 235 == End-to-End Encryption == 236 236 237 -In ACMP, you have the option to use S/MIME encryption technology for your email traffic. End-to-end encryption is established when both the sender and the recipients have received the other party’s public key via an S/MIME-encrypted email. The content of the communication can then only be read by the sender and recipients. Third-party access is prevented.237 +In acmp, you have the option to use S/MIME encryption technology for your email traffic. End-to-end encryption is established when both the sender and the recipients have received the other party’s public key via an S/MIME-encrypted email. The content of the communication can then only be read by the sender and recipients. Third-party access is prevented. 238 238 239 -Go to //System > Settings > ACMPServer > Email Service > End-to-End Encryption//. By default,ACMPdoes not use any email encryption technology. If you want to use S/MIME, you must first choose an encryption mode:239 +Go to //System > Settings > acmp Server > Email Service > End-to-End Encryption//. By default, acmp does not use any email encryption technology. If you want to use S/MIME, you must first choose an encryption mode: 240 240 241 241 |((( 242 242 **Encryption Mode** ... ... @@ -248,7 +248,7 @@ 248 248 249 249 **Manage Certificates** 250 250 251 -To ensure that your emails have an S/MIME certificate and are therefore encrypted, you must first specify your certificate in ACMP. You can obtain a certificate either by generating one yourself or by purchasing a CA certificate.251 +To ensure that your emails have an S/MIME certificate and are therefore encrypted, you must first specify your certificate in acmp. You can obtain a certificate either by generating one yourself or by purchasing a CA certificate. 252 252 253 253 Go to //Manage Certificates > Add Certificate//. 254 254 ... ... @@ -255,7 +255,7 @@ 255 255 Specify the //certificate file// and the //private key file//. 256 256 257 257 {{aagon.infobox}} 258 -The PKCS#12 or PFX/P12 format is commonly used. ACMPdoes not support this format in principle, since the certificates and keys are combined into a single file. However, you can use the OpenSSL commands `openssl pkcs12 -in path.p12 -out newfile.crt -clcerts –nokeys` for the certificate and `openssl pkcs12 -in path.p12 -out newfile.pem -nocerts –nodes` for the private key to generate two separate files from the original file.258 +The PKCS#12 or PFX/P12 format is commonly used. acmp does not support this format in principle, since the certificates and keys are combined into a single file. However, you can use the OpenSSL commands `openssl pkcs12 -in path.p12 -out newfile.crt -clcerts –nokeys` for the certificate and `openssl pkcs12 -in path.p12 -out newfile.pem -nocerts –nodes` for the private key to generate two separate files from the original file. 259 259 {{/aagon.infobox}} 260 260 261 261 For the private key file, enter the corresponding password under //Passphrase//. Click OK. The certificate's serial number and validity period will be automatically retrieved and filled in. ... ... @@ -271,7 +271,7 @@ 271 271 To do this, go to //Master Data > Contacts// on the ribbon bar. In the //Contact Details// of an existing contact or a new contact you are creating, click the icon in the //Email// field and enter the certificate there. 272 272 273 273 {{figure}} 274 -[[image:64_System_Stammdaten Kontakte_1504.png]] 274 +[[image:64_System_Stammdaten Kontakte_1504.png||data-cmp-info="10"]] 275 275 276 276 {{figureCaption}} 277 277 Add a Certificate for Contacts in Master Data ... ... @@ -283,7 +283,7 @@ 283 283 To manage server load, you can define predefined server tasks and their individual start conditions here. 284 284 285 285 {{figure}} 286 -[[Settings - Scheduled Server Tasks>>image:68_Einstellungen_GeplanteServeraufgaben_1918.png||alt="68_Einstellungen_GeplanteServeraufgaben_1611.png" data-xwiki-image-style-alignment="center"]] 286 +[[Settings - Scheduled Server Tasks>>image:68_Einstellungen_GeplanteServeraufgaben_1918.png||alt="68_Einstellungen_GeplanteServeraufgaben_1611.png" data-cmp-info="10" data-xwiki-image-style-alignment="center"]] 287 287 288 288 {{figureCaption}} 289 289 ... ... @@ -312,7 +312,7 @@ 312 312 |=General|= 313 313 |Checks for items with new Distribution Ring|Checks whether elements can be moved to the next distribution ring.{{aagon.infobox}}This option applies to both Managed Software and Windows Update Management (including Defender and Office 365 Updates).{{/aagon.infobox}} 314 314 |Client Tenant relation calculation|Dynamically links clients to clients based on the tenant filter. 315 -| ACMPGateway cleanup|Removes expired certificates from theACMPGateway.315 +|acmp Gateway cleanup|Removes expired certificates from the acmp Gateway. 316 316 |Server Monitor log cleanup|Removes server job executions that are older than 30 days (default). 317 317 |Assigns Clients to Containers dynamically|Calculates dynamic shortcuts from Clients to containers. 318 318 |Renew Client Certificates|Renew the Gateway certificates on the Clients. ... ... @@ -321,7 +321,7 @@ 321 321 Retrieves new license information from the Aagon license server. 322 322 323 323 {{aagon.infobox}} 324 -Disabling this server task will prevent license information from being retrieved from and updated on the license server. Do not disable this task, as doing so will interfere with ACMPoperations!324 +Disabling this server task will prevent license information from being retrieved from and updated on the license server. Do not disable this task, as doing so will interfere with acmp operations! 325 325 {{/aagon.infobox}} 326 326 ))) 327 327 |VMware vSphere Scanner|Scans VMware vSphere Server for guest systems. ... ... @@ -332,17 +332,17 @@ 332 332 Performs a cleanup of Client Command versions whose last date modified is older than 120 days (default). 333 333 334 334 {{aagon.versionierungsbox}} 335 -These scheduled server tasks are available only in ACMPversion 6.9.335 +These scheduled server tasks are available only in acmp version 6.9. 336 336 {{/aagon.versionierungsbox}} 337 337 338 338 {{aagon.infobox}} 339 -A new Client Command version is a complete copy of the previous version. As a result, the ACMPServer and theACMPDatabase can become cluttered with redundant data when many versions are created, which is why it makes sense to perform cleanup.339 +A new Client Command version is a complete copy of the previous version. As a result, the acmp Server and the acmp Database can become cluttered with redundant data when many versions are created, which is why it makes sense to perform cleanup. 340 340 By double-clicking the setting, you can specify cleanup options in the wizard. 341 341 A Client Command version is deleted if the following conditions are met: 342 342 1. The Client Command version has the status “Removed From Production.” 343 343 2. The date modified was at least 120 days ago (default value). 344 344 3. There is at least one other version with the status “Removed From Production” in the quantity identified so far. 345 -The number of deletion operations per server task per execution is also limited (default value: 50) to minimize the load on the ACMPServer and the deployed file repositories.345 +The number of deletion operations per server task per execution is also limited (default value: 50) to minimize the load on the acmp Server and the deployed file repositories. 346 346 {{/aagon.infobox}} 347 347 ))) 348 348 |Client Command log cleanup|((( ... ... @@ -370,7 +370,7 @@ 370 370 |**License Management**| 371 371 |Contract auto extension|Automatically renews the relevant contracts. 372 372 |Import Microsoft 365 license data|Importes Microsoft 365 license and product data for License Management. 373 -|DNA2 catalog update|Updates the DNA2 catalog, calculates new and unrecognized software to improve the detection rate, and reports this information to ACMP.373 +|DNA2 catalog update|Updates the DNA2 catalog, calculates new and unrecognized software to improve the detection rate, and reports this information to acmp. 374 374 |Recalculate License Management compliance view|Recalculates the compliance data. 375 375 |Clients without Primary User calculation|Calculates dynamically determined Clients that do not have a mapping to a primary user 376 376 | | ... ... @@ -387,7 +387,7 @@ 387 387 | | 388 388 |**Windows Update Management**| 389 389 |Windows Update log cleanup|Performs cleanup on logs that are older than 30 days (default). 390 -|Windows Update Managed Clients recalc|Calculates dynamic links for clients managed by ACMPWindows Update Management.390 +|Windows Update Managed Clients recalc|Calculates dynamic links for clients managed by acmp Windows Update Management. 391 391 |Windows Update Management cleanup|Frees up hard drive space occupied by unnecessary Windows Updates. 392 392 |Windows Update Management metadata download|Downloads metadata about Windows Updates. 393 393 |Windows Update setup download|Downloads setup files for Windows Updates. ... ... @@ -403,7 +403,7 @@ 403 403 To add a new user account, click the Add button. In the window that opens, enter the username and password. You must re-enter the password to perform passwort confirmation. After confirming with OK, the user account will appear in the overview. You can edit or delete it as needed. 404 404 405 405 {{figure}} 406 -[[image:68_System_Einstellungen_ACMPServer_GlobaleNutzerkonten_1918.png||data-xwiki-image-style-alignment="center"]] 406 +[[image:68_System_Einstellungen_ACMPServer_GlobaleNutzerkonten_1918.png||data-cmp-info="10" data-xwiki-image-style-alignment="center"]] 407 407 408 408 Global User Accounts 409 409 {{/figure}} ... ... @@ -417,7 +417,7 @@ 417 417 418 418 === **Delete a Global User Account** === 419 419 420 -To delete a global user account, select the account in the overview and click the Delete button on the right. The system will now check whether the global user account to be deleted is being used by other elements in ACMP. The result will be displayed in a dialog box.420 +To delete a global user account, select the account in the overview and click the Delete button on the right. The system will now check whether the global user account to be deleted is being used by other elements in acmp. The result will be displayed in a dialog box. 421 421 422 422 {{aagon.infobox}} 423 423 Please note that you will no longer be able to use elements if the registered global user account is deleted. It is not possible to access file repositories without a global user account. ... ... @@ -425,11 +425,11 @@ 425 425 426 426 = HTTP API = 427 427 428 -In this setting, you can specify the port used for file transfers in the ACMPapp or for the active SICS connection. TheACMPHTTP API port is responsible for uploading and downloading files. By default, the checkbox is enabled. To disable it, you must explicitly uncheck the box. Also, specify the port to be used for the connection.428 +In this setting, you can specify the port used for file transfers in the acmp app or for the active SICS connection. The acmp HTTP API port is responsible for uploading and downloading files. By default, the checkbox is enabled. To disable it, you must explicitly uncheck the box. Also, specify the port to be used for the connection. 429 429 Also, check the additional checkbox if you want to disable TLS Legacy. This will disable the versions available starting with Windows Server 2022. 430 430 431 431 {{figure}} 432 -[[ >>image:68_System_HTTP API_1007.png||alt="Einstellungen zu der HTTP API"]] 432 +[[ >>image:68_System_HTTP API_1007.png||alt="Einstellungen zu der HTTP API" data-cmp-info="10"]] 433 433 434 434 {{figureCaption}} 435 435 Settings for the HTTP API ... ... @@ -443,7 +443,7 @@ 443 443 Before you enable multi tenancy, you must have already assigned your Clients to the appropriate tenant groups and tenants. In addition, all existing conflicts should be resolved, and user permissions should be set up correctly. Only then can multi tenancy be enabled. 444 444 {{/aagon.infobox}} 445 445 446 -To enable general multi tenancy in ACMP, click //Enable// //Multi Tenancy//.446 +To enable general multi tenancy in acmp, click //Enable// //Multi Tenancy//. 447 447 448 448 ~1. Click “Enable Multi Tenancy.” A wizard will open. 449 449 ... ... @@ -457,7 +457,7 @@ 457 457 {{box}} 458 458 **Attention:** 459 459 460 -Any users who do not have permissions specified for individual tenants or the “Tenant Administrator” role will no longer be able to log in to the ACMP Console after multi tenancy is activated. If there are any such users, a warning will be displayed!460 +Any users who do not have permissions specified for individual tenants or the “Tenant Administrator” role will no longer be able to log in to the acmp Console after multi tenancy is activated. If there are any such users, a warning will be displayed! 461 461 {{/box}} 462 462 463 463 4. In the next step, you’ll configure two settings: ... ... @@ -468,7 +468,7 @@ 468 468 469 469 * Execution of the “SQL Query” Command 470 470 471 -You decide whether the “Execute on ACMPServer/Database” option should be enabled or disabled in SQL commands.471 +You decide whether the “Execute on acmp Server/Database” option should be enabled or disabled in SQL commands. 472 472 473 473 474 474 5. After configuration, click “Done” and save the settings via the ribbon bar to permanently enable multi tenancy. ... ... @@ -501,13 +501,13 @@ 501 501 Once you have made your selection, click the Add button to add a new network. Enter the IP address and the subnet mask. 502 502 503 503 (% style="text-align:center" %) 504 -[[image:XWiki.Images.WebHome@hmfile_hash_8b3f62ba.png||alt="9.4.4 - Netzwerkadresse Editieren" height="150" width="268"]] 504 +[[image:XWiki.Images.WebHome@hmfile_hash_8b3f62ba.png||alt="9.4.4 - Netzwerkadresse Editieren" data-cmp-info="10" height="150" width="268"]] 505 505 Edit Network Address 506 506 507 507 This information is saved by clicking the OK button and displayed in the overview. To edit the information, select the corresponding entry and click Edit. An input form with the default data will reappear. To delete an entry, select it and click Delete. 508 508 509 509 {{figure}} 510 -[[image:68_System_Einstellungen_Netzwerke_1678.png||data-xwiki-image-style-alignment="center"]] 510 +[[image:68_System_Einstellungen_Netzwerke_1678.png||data-cmp-info="10" data-xwiki-image-style-alignment="center"]] 511 511 512 512 {{figureCaption}} 513 513 System settings (Networks) ... ... @@ -514,14 +514,14 @@ 514 514 {{/figureCaption}} 515 515 {{/figure}} 516 516 517 -In the lower section, you can specify trusted web servers, as well as edit and delete existing items. Specifying a trusted web server is important if you have licensed the Helpdesk Web Interface and installed it on a server other than the ACMPServer. The IP address of theACMPServer is already entered during installation. You do not need to enter it again.517 +In the lower section, you can specify trusted web servers, as well as edit and delete existing items. Specifying a trusted web server is important if you have licensed the Helpdesk Web Interface and installed it on a server other than the acmp Server. The IP address of the acmp Server is already entered during installation. You do not need to enter it again. 518 518 519 519 520 520 521 521 = Server proxy configuration = 522 522 523 -The ACMPServer requires Internet access for some modules. If you are using a proxy to provide Internet access, you will need to make some configuration changes.524 -The [[Setup Checklist>>doc:ACMP.610.ACMP installieren.Checkliste zur Installation.WebHome||anchor="HRequiredURLs"]] section lists all the hosts you need for the connection between the ACMPServer and the respective modules..523 +The acmp Server requires Internet access for some modules. If you are using a proxy to provide Internet access, you will need to make some configuration changes. 524 +The [[Setup Checklist>>doc:ACMP.610.ACMP installieren.Checkliste zur Installation.WebHome||anchor="HRequiredURLs"]] section lists all the hosts you need for the connection between the acmp Server and the respective modules.. 525 525 526 526 {{aagon.infobox}} 527 527 All hosts listed there are accessed via HTTPS (port 443). ... ... @@ -532,10 +532,10 @@ 532 532 Enable the //Use proxy authentication// checkbox to enter a username and password there. Otherwise, these rows will remain grayed out. Save your changes by clicking the “Save” button in the ribbon bar. 533 533 534 534 {{figure}} 535 -[[image:68_Server Proxy Konfiguration_906.png||alt="68_System_Einstellungen_ServerProxy-Konfiguration_655.png" data-xwiki-image-style-alignment="center"]] 535 +[[image:68_Server Proxy Konfiguration_906.png||alt="68_System_Einstellungen_ServerProxy-Konfiguration_655.png" data-cmp-info="10" data-xwiki-image-style-alignment="center"]] 536 536 537 537 {{figureCaption}} 538 - ACMPServer proxy settings538 +acmp Server proxy settings 539 539 {{/figureCaption}} 540 540 {{/figure}} 541 541 ... ... @@ -543,10 +543,10 @@ 543 543 544 544 = SICS connection = 545 545 546 -After installing the AESB, you must enable the SICS (Smart Infrastructure Communication Service) connection. To do this, navigate to //System// > //Settings// > //ACMP////Server// > //SICS connection//.546 +After installing the aesb, you must enable the SICS (Smart Infrastructure Communication Service) connection. To do this, navigate to //System// > //Settings// > //acmp Server// > //SICS connection//. 547 547 548 548 {{figure}} 549 -[[image:68_System_Einstellungen_SICS-Verbindung_1172.png||data-xwiki-image-style-alignment="center"]] 549 +[[image:68_System_Einstellungen_SICS-Verbindung_1172.png||data-cmp-info="10" data-xwiki-image-style-alignment="center"]] 550 550 551 551 {{figureCaption}} 552 552 Establish a SICS connection ... ... @@ -553,21 +553,21 @@ 553 553 {{/figureCaption}} 554 554 {{/figure}} 555 555 556 -First, check the checkbox to enable the connection. Then enter the host and port, as well as the username and password for the operator. You specified the relevant operator during the AESBinstallation; you must enter that name here as well. Specify whether the system should attempt to establish an unencrypted connection if SSL/TLS fails. To verify your entries, you can test the connection while still in the server settings. Click the button with the same name, and the test will begin. A small window will display the result, indicating whether the connection was successful or not.556 +First, check the checkbox to enable the connection. Then enter the host and port, as well as the username and password for the operator. You specified the relevant operator during the aesb installation; you must enter that name here as well. Specify whether the system should attempt to establish an unencrypted connection if SSL/TLS fails. To verify your entries, you can test the connection while still in the server settings. Click the button with the same name, and the test will begin. A small window will display the result, indicating whether the connection was successful or not. 557 557 558 558 Additional connection information is listed below the SICS connection credentials. If you have not yet entered any connection details, the status will be //Disconnected//. Only after a successful connection is established will the status change, and the routing key and virtual router will be automatically populated. You cannot manually edit these last two fields. 559 559 560 560 === **Public API Access Rights** === 561 561 562 -You can specify whether you want to grant SICS users access to ACMP’s public API. By default, the checkbox //Grant Access// is not selected. However, if you wish to grant access, enable the corresponding checkbox.562 +You can specify whether you want to grant SICS users access to acmp’s public API. By default, the checkbox //Grant Access// is not selected. However, if you wish to grant access, enable the corresponding checkbox. 563 563 564 564 === **Public API Response** === 565 565 566 -Here, you can specify the maximum number of elements to be returned in a public API response. If you leave the value at 0, no limit is set. The maximum number of elements to be sent in a public API response is 1,000 by default when ACMPis delivered. Define your own range of values that best suits your needs.566 +Here, you can specify the maximum number of elements to be returned in a public API response. If you leave the value at 0, no limit is set. The maximum number of elements to be sent in a public API response is 1,000 by default when acmp is delivered. Define your own range of values that best suits your needs. 567 567 568 568 === **QR Code for App Login** === 569 569 570 -In this section, you can generate a QR code to simplify login for the ACMP Mobile App. If the SICS connection is activated, a corresponding [[menu item in the system menu>>doc:ACMP.610.Arbeiten mit der ACMP Console.Aufbau der Console.Ribbonleiste.WebHome]] is also available for this purpose. You can also specify alternative connection information. To do so, enable the checkbox and enter the alternative hostname and SICS port. The information you provide is required to start generating the QR code.570 +In this section, you can generate a QR code to simplify login for the acmp Mobile App. If the SICS connection is activated, a corresponding [[menu item in the system menu>>doc:ACMP.610.Arbeiten mit der ACMP Console.Aufbau der Console.Ribbonleiste.WebHome]] is also available for this purpose. You can also specify alternative connection information. To do so, enable the checkbox and enter the alternative hostname and SICS port. The information you provide is required to start generating the QR code. 571 571 572 572 573 573 ... ... @@ -599,10 +599,10 @@ 599 599 600 600 All clients entered into the database consume a license. 601 601 602 -=== ** ACMPvSphere scanner** ===602 +=== **acmp vSphere scanner** === 603 603 604 604 {{aagon.infobox}} 605 -Please note that the VMware vSphere PowerCLI tools must be installed on the ACMPServer in order to use the VMware vSphere Scanner. If you are unsure, you can use //Check PowerCLI// to verify availability.605 +Please note that the VMware vSphere PowerCLI tools must be installed on the acmp Server in order to use the VMware vSphere Scanner. If you are unsure, you can use //Check PowerCLI// to verify availability. 606 606 {{/aagon.infobox}} 607 607 608 608 If the PowerCLI tools are not installed on your system or are not installed in the system context, follow these steps: ... ... @@ -622,7 +622,7 @@ 622 622 {{/aagon.infobox}} 623 623 624 624 {{figure}} 625 -[[image:PowerCLI Tools CMD.png]] 625 +[[image:PowerCLI Tools CMD.png||data-cmp-info="10"]] 626 626 627 627 {{figureCaption}} 628 628 CMD with the appropriate Commands ... ... @@ -629,7 +629,7 @@ 629 629 {{/figureCaption}} 630 630 {{/figure}} 631 631 632 -Only after you have installed the tools can you specify the Server(s) and allow ACMPto scan the virtual Clients correctly. Additionally, you must ensure that the installed vSphere PowerCLI tools are compatible with the installed vSphere Server.632 +Only after you have installed the tools can you specify the Server(s) and allow acmp to scan the virtual Clients correctly. Additionally, you must ensure that the installed vSphere PowerCLI tools are compatible with the installed vSphere Server. 633 633 634 634 635 635 Next, create a vSphere server. Proceed as follows:

