Wiki source code of Verteilte File Repositories

Last modified by Sabrina V. on 2026/07/29 06:19

version	line-number	content
1.1	1	{{aagon.priorisierung}}
	2	20
	3	{{/aagon.priorisierung}}
	4
	5	{{aagon.floatingbox/}}
	6
66.1	7	= General =
1.1	8
66.1	9	A file repository serves as a central storage location for ACMP Updates and other files that can be assigned to the respective repository. By using file repositories, data can be made available closer to the clients’ locations. This reduces the load on the ACMP Server, since not all data transfers have to go through it directly. If no file repositories are set up or used, data downloads occur exclusively via the ACMP Server. In this case, one slot is occupied for the duration of each download to execute a server command.
	10	It is possible to create multiple file repositories. The ACMP Server synchronizes the relevant data with the respective file repositories, from which the ACMP Agents download the required files. By default, the ACMP Server itself serves as the first file repository, so the ACMP Agents retrieve their files directly from the ACMP Server’s file repository.
1.1	11
55.1	12	{{aagon.infobox}}
67.1	13	By default, you can create up to two file repositories. If you want to create more, you must increase or configure the corresponding number in the Config.xml file. The value to edit is called “NumberOfSyncProcessors.” Please note, however, that you should not enter a value that is too high (such as 100), as this may cause an overflow.
	14	The Config.xml file is only viewable when the ACMP server service exits. Read more about this in the [[Settings>>doc:ACMP.610.ACMP-Solutions.System.Einstellungen.WebHome]].
55.1	15	{{/aagon.infobox}}
	16
67.1	17	= Manage File Repositories =
1.1	18
67.1	19	The list of file repositories displayed includes their names, availability, current status, and content.
1.1	20
67.1	21	Availability is displayed as a ratio. This ratio represents the number of successful connection attempts relative to the number of Clients (assigned to the file repository) (see [[Container>>doc:ACMP.610.ACMP-Solutions.Client-Management.Container.WebHome]]).
1.1	22
67.1	23	The content indicates the type of content stored in the file repository. There are three possible icons. A puzzle icon means that the file repository can accept Client Commands. A hard drive icon indicates that the file repository relates to client updates, and a client icon next to the file repository means that it contains OS Deployment files. A combination of two or three different content types is possible.
1.1	24
	25	{{figure}}
43.1	26	[[image:68_System_VerteilteFileRepositories_1661.png\|\|alt="63_System_VerteilteFileRepositories_1661.png" data-xwiki-image-style-alignment="center"]]
1.1	27
	28	{{figureCaption}}
67.1	29	Manage File Repositories
1.1	30	{{/figureCaption}}
	31	{{/figure}}
	32
	33
	34
67.1	35	=== Create a New File Repository ===
1.1	36
67.1	37	Add a new file repository by clicking //Add// on the ribbon bar. Enter a name for the file repository and, if desired, a description. Then specify the items to be used for the file repository.
	38
1.1	39	{{figure}}
6.1	40	[[image:63_System_VerteilteFileRepositories_803.png\|\|alt="Schritt 1 Allgemein.png" data-xwiki-image-style-alignment="center"]]
1.1	41
	42	{{figureCaption}}
67.1	43	Step 1: General
1.1	44	{{/figureCaption}}
	45	{{/figure}}
	46
67.1	47	You can choose from:
1.1	48
67.1	49	* Client Command files
1.1	50	* ACMP Updates
67.1	51	* OS Deployment files
1.1	52
	53	{{aagon.infobox}}
67.1	54	For OS Deployment files, the only connection type available - due to technical limitations - is //network share//, which you will select in the next step.
1.1	55	{{/aagon.infobox}}
	56
67.1	57	* Vulnerability Definition Files
1.1	58	* Windows Updates
	59	* Managed Software
	60
67.1	61	When the //Automatic Synchronization// option is selected, the ACMP Server automatically synchronizes the file repositories. If you disable this option, you will need to perform the synchronization manually as needed.
1.1	62
	63	{{aagon.infobox}}
67.1	64	Please review the information on the file repository size before configuring the following settings! Also note that the file repository size specified here is merely a snapshot. Every new item added to ACMP also affects the amount of storage space required by the file repository.
1.1	65	{{/aagon.infobox}}
	66
67.1	67	Click //Next//.
1.1	68
67.1	69	To allow the ACMP Server to transfer data to the file repository, enter the session data in the next step.
1.1	70
67.1	71	To do this, select one of the following connection types:
1.1	72
67.1	73	== Network Share ==
1.1	74
	75	\|(((
67.1	76	You can distribute your files to the file repository via a network or Samba share.
1.1	77
54.1	78	{{aagon.infobox}}
67.1	79	Please note that umlauts are not permitted in network shares and may prevent the connection to the file repositories from being established.
54.1	80	{{/aagon.infobox}}
	81
67.1	82	To do this, enter a UNC path that must be structured as follows:
1.1	83
67.1	84	{{{\\Server name\Share name}}}
1.1	85
67.1	86	Then, for authentication, select either a global account or a specific account - that is, a specific user account
1.1	87
65.1	88	{{aagon.infobox}}
67.1	89	When using the “Network Share” connection type, the ACMP Server establishes an SMB connection to the file repository. To reduce the risk of NTLM relay attacks, it is recommended that you enable client-side SMB signing on the ACMP Server.
65.1	90	{{/aagon.infobox}}
	91
67.1	92	You can then run a connection test from the Server to the file repository.
1.1	93
67.1	94	Click //Next//.
1.1	95	)))\|(((
6.1	96	[[image:File Repo_Freigabe.png\|\|data-xwiki-image-style-alignment="center" height="654" width="700"]]
1.1	97
	98
	99	)))
	100
	101	== FTP ==
	102
	103	\|(% style="width:1111px" %)(((
67.1	104	You can distribute your files to the file repositories using FTP (File Transfer Protocol), an unencrypted file transfer method.
1.1	105
	106	{{aagon.infobox}}
67.1	107	Please note that using FTP as the connection type poses security risks, as data is transmitted in plain text without encryption. In this case, we recommend using FTPS.
1.1	108	{{/aagon.infobox}}
	109
67.1	110	To do this, enter an FTP path that must be structured as follows:
1.1	111
	112	{{{ftp://Servername}}}
	113
67.1	114	Also specify the port; the default is port 21.
1.1	115
67.1	116	Then, for authentication, select either anonymous, global, or a specific account - that is, a specific user account.
1.1	117
67.1	118	You can then perform a connection test from the server to the file repository.
1.1	119
67.1	120	Click //Next//.
1.1	121	)))\|(% style="width:901px" %)(((
6.1	122	[[image:File Repo_FTP.png\|\|data-xwiki-image-style-alignment="center" height="654" width="700"]]
1.1	123	)))
	124
	125	== FTPS ==
	126
	127	\|(% style="width:1114px" %)(((
67.1	128	You can distribute your files to the file repositories using FTPS (File Transfer Protocol over SSL), an FTP-based file transfer method with SSL/TLS encryption.
1.1	129
67.1	130	To do this, specify an FTPS path that must be structured as follows:
1.1	131
67.1	132	{{{ftps://servername}}}
1.1	133
67.1	134	Also specify the port; the default is port 21.
1.1	135
67.1	136	Then specify whether the FTPS connection should be encrypted implicitly or explicitly via SSL/TLS.
1.1	137
	138	(% style="width:1066.48px" %)
67.1	139	\|(% style="width:269px" %)Implicity\|(% style="width:795px" %)In this mode, the client must explicitly request a secure connection from the server. If a client does not send such a request to the server in this mode, the server may decide whether to allow the insecure connection to continue, dismiss it, or restrict it. Encryption is permitted but not required.
	140	\|(% style="width:269px" %)Explicitly\|(% style="width:795px" %)In this mode, the client is expected to report to the server immediately. If it fails to do so, the server terminates the connection. Encryption is required.
1.1	141
67.1	142	Also select the minimum version of the TLS protocol.
1.1	143
67.1	144	Then, for authentication, select either an anonymous, global, or specific account - that is, a specific user account.
1.1	145
67.1	146	You can then run a connection test from the Server to the file repository.
1.1	147
67.1	148	Click //Next//.
1.1	149	)))\|(% style="width:898px" %)(((
6.1	150	[[image:File Repo_FTPS.png\|\|data-xwiki-image-style-alignment="center" height="654" width="699"]]
1.1	151	)))
	152
	153	== WebDAV ==
	154
	155	\|(% style="width:1114px" %)(((
67.1	156	WebDAV is used to deploy the files to the file repository via an HTTP/HTTPS-based transfer.
	157	To do this, enter the specific WebDAV URL, which can be structured as follows:
1.1	158
52.1	159	{{{
	160	}}}
1.1	161
67.1	162	Please note that the WebDAV URL depends on the WebDAV configuration and may differ from the example.
1.1	163
	164	{{aagon.infobox}}
67.1	165	Please note that files transferred via WebDAV must not exceed a certain size. However, this limit depends on the WebDAV provider and the WebDAV Server and should be verified in advance, as these may vary.
1.1	166	{{/aagon.infobox}}
	167
67.1	168	The //Accept untrusted certificates// checkbox allows you to use self-signed certificates.
1.1	169
67.1	170	Then, for authentication, specify either an anonymous, global, or specific account - that is, a specific user account.
1.1	171
67.1	172	You can then perform a connection test from the Server to the file repository.
1.1	173
67.1	174	Click //Next//.
1.1	175	)))\|(% style="width:898px" %)(((
6.1	176	[[image:File Repo_Webdav_http.png\|\|data-xwiki-image-style-alignment="center" height="655" width="702"]]
1.1	177	)))
	178
	179	== SFTP ==
	180
	181	\|(% style="width:1113px" %)(((
67.1	182	SFTP is used to deploy the files to the file repositories via an SSH-based, encrypted transfer.
1.1	183
	184	{{aagon.infobox}}
67.1	185	To determine which storage locations are in use and which are available, the SFTP server must support protocol version 6. Please note that one of the most widely used SFTP servers, OpenSSH, does not support this!
1.1	186	{{/aagon.infobox}}
	187
67.1	188	To do this, enter the URL or IP address of the SFTP server, which must be formatted as follows:
1.1	189
	190	{{{sftp://Servername}}}
	191
67.1	192	Then enter the port; the default is port 22.
1.1	193
67.1	194	If necessary, enter the home directory.
1.1	195
	196	{{aagon.infobox}}
67.1	197	The achievable transfer speed of an SFTP connection is heavily influenced by the latency between the server and the client. For example, with an average latency of 30 ms, speeds rarely exceed 2 MB/s.
1.1	198	{{/aagon.infobox}}
	199
67.1	200	Next, specify either an anonymous, global, or specific account - that is, a specific user account - for authentication.
1.1	201
67.1	202	You can then run a connection test from the Server to the file repository.
1.1	203
67.1	204	Click //Next //>.
1.1	205	)))\|(% style="width:898px" %)(((
6.1	206	[[image:File Repo_SFTP.png\|\|data-xwiki-image-style-alignment="center" height="654" width="701"]]
1.1	207
	208
	209	)))
	210
67.1	211	Regardless of which connection types you have selected, in the next step you can specify the times during which the ACMP Server is allowed to transfer data to the file repository. To do this, you will see an overview of the days of the week in 24-hour mode.
	212	Use drag-and-drop to move the light- or dark-blue rectangle below the overview into the overview itself. The dark blue area allows data transfer at the highest possible speed, while the light blue area limits the bandwidth. You can specify this limit globally for all light blue areas on the right-hand side; in other words, the bandwidth limit cannot be set separately for each dark blue area.
1.1	213
67.1	214	[[Configuring the Server's synchronization time frames with the file repositories>>image:69_Verteilte Repos Wizard 3.png]]
1.1	215
67.1	216	After dragging one of the two areas into the overview, you can extend it over a specific time period by dragging it with the mouse to the desired duration. Alternatively, you can execute a double-click on a time window or on the overview itself. This opens a dialog box where you can set the time period and enable or disable the bandwidth limit.
1.1	217
67.1	218	[[Client Connection Properties>>image:69_File Repo Wizard 4.png]]
1.1	219
67.1	220	To enable the ACMP agents to communicate with the file repository, enter the client session data. These are identical to the Server connection types. The same notes apply here as for the session data between the ACMP Server and the deployed file repositories.
1.1	221
67.1	222	[[Configuring the connection type from the file repository to the Client>>image:69_File Repo Wizard 5.png]]
1.1	223
67.1	224	You can then limit the bandwidth that Clients use for their connection to the file repository. This setting applies to each Client individually.
1.1	225
67.1	226	On the last page, you can specify a [[sync profil>>doc:\|\|anchor="HSyncprofil"]] before a summary of the file repository to be created is displayed. Close the wizard by clicking //Finish//.
1.1	227
	228	{{aagon.infobox}}
67.1	229	To allow your clients to access the new file repository, you must add it either to the default file repositories or to a container.
1.1	230	{{/aagon.infobox}}
	231
	232
	233
67.1	234	=== Duplicate a deployed File Repository ===
1.1	235
67.1	236	You can duplicate a previously selected file repository using the button on the “Manage File Repositories” tab. This opens a wizard as described on the previous pages, but the data for the selected file repository is already pre-filled.
1.1	237
67.1	238	=== Sync Monitor ===
1.1	239
67.1	240	Click the Sync Monitor button in the Quick Access Toolbar to open an overview. This overview lists all file repositories along with their type (Client Commands/Client Update/OS Deployment), and the data for each type is displayed below it along with its status. The status indicates how far along the synchronization process is.
1.1	241
67.1	242	[[File Repository: Synchronization Monitor>>image:69_Syncmonitor.png]]
1.1	243
67.1	244	You can use the Refresh button to update the displayed data immediately.
1.1	245
67.1	246	You can use the Start Synchronization or Stop Synchronization buttons to pause or continue synchronization of the selected file repositories. If you continue a paused synchronization, a dialog box will appear where you can specify whether only the new dates or all dates should be transferred during the first synchronization.
	247
1.1	248	{{aagon.infobox}}
67.1	249	You can force an immediate synchronization by selecting “Start Synchronization.” If the synchronization of a file repository is stopped manually, the “Automatic Synchronization” option is also disabled.
1.1	250	{{/aagon.infobox}}
	251
	252
	253
67.1	254	=== Statistics ===
1.1	255
67.1	256	Click the Statistics button on the Quick Access Toolbar to open the statistics view. It displays all file repositories along with their names and availability.
1.1	257
67.1	258	[[File Repository Statistics>>image:69_Sync Statistiken.png]]
1.1	259
	260
	261
67.1	262	=== Standard File Repositories ===
1.1	263
67.1	264	On this tab, you can define file repositories that Clients will automatically use at the top level when inheritance is activated. The file repositories listed here are processed in order of priority until a connection to one of them is established.
1.1	265
67.1	266	Click the Add Default File Repository button to open a dialog where you can select existing file repositories. These file repositories are then inserted into this list. Use the arrow buttons on the right-hand side to set the order in which Clients will try the file repositories if a connection cannot be established. Click the “Remove Default File Repository” button to remove a selected file repository from this list.
1.1	267
67.1	268	=== Special Notes ===
1.1	269
67.1	270	When you create a new file repository in an existing ACMP environment, all Client Commands that were previously shared are reset to the “Synchronize/Share” status. This occurs because the data on the new file repository has not yet been synchronized. The Client Commands that were synchronized with the previous file repositories can, of course, still be used. Nevertheless, you should synchronize the data to the new file repository as soon as possible.
1.1	271
67.1	272	= Sync profil =
	273
	274	Sync profiles allow you to specify which Updates from [[Windows Update Management>>doc:ACMP.610.ACMP-Solutions.Patch Management.Windows Update Management.WebHome]] should be synchronized to which file repositories.
	275
1.1	276	{{aagon.infobox}}
67.1	277	Please note that the filters specified in the sync profile for “Update Products,” “Update Classification,” and “Update Languages” are linked with an “OR.” As a result, if, for example, only “English” is specified, all updates will be synchronized.
1.1	278	{{/aagon.infobox}}
	279
67.1	280	First, click “Sync Profiles” on the ribbon bar and enter a name for the new sync profile. Confirm the name by clicking “Next,” which will take you to the sync profile's filter settings.
	281	In the upper section, specify which products you want to assign to this sync profile. In the middle section, specify which update classification you want to include, and in the lower section, specify the languages.
1.1	282
67.1	283	{{aagon.infobox}}
	284	All values displayed are loaded from the metadata you downloaded upon completing the First Step.
	285	{{/aagon.infobox}}
1.1	286
	287
	288
	289
67.1	290	= Migrating the ACMP Server Repository Using a Tool =
1.1	291
67.1	292	With the introduction of Windows Update Management, a tool is provided that allows you to move the ACMP Server as a file repository via a graphical user interface. The //SwapServerFileRepository.exe// tool can be found in the server directory after updating to version 5.4.7. The installation directory for the ACMP Server is located at //%ProgramFiles(x86)%\Aagon\ACMP Server//.
1.1	293
	294	{{aagon.infobox}}
67.1	295	Multi-server instances are not currently supported.
1.1	296	{{/aagon.infobox}}
	297
67.1	298	=== Preparation ===
1.1	299
23.1	300	{{aagon.warnungsbox}}
67.1	301	We strongly recommend that you create a database backup before proceeding with the following steps. Click [[here >>doc:ACMP.610.Datenbankmanagement.Vollständiges ACMP Backup durchführen.WebHome]]to learn how to do this.
23.1	302	{{/aagon.warnungsbox}}
1.1	303
67.1	304	Before the file repository can be moved, you must first exit the server service. This will cancel any Jobs and Rollouts that are still running.
	305	Also, make sure that there is enough free space available for the file repository at the destination and that the destination is clear.
1.1	306
23.1	307
1.1	308
67.1	309	=== Using SwapServerFileRepository.exe ===
1.1	310
67.1	311	1. Open the installation directory and run //SwapServerFileRepository.exe// from there with administrative privileges.
	312	1. Stop the ACMP Server service using the tool or through the Services management console.
	313	1. Use the radio button to select the target type. You can specify a local path or a UNC network share. With a UNC network share, you have the option to pass user data. You can also test the connection using the //Test connection// button.
	314	1. Proceed to the next page to start the copy process.
	315	1. Once the copy process is complete, you will see a summary.
	316	1. Start the ACMP Server service.
	317	1. Verify that the move was successful. You can do this, among other ways, as follows:
	318	1*. Open ticket attachments
	319	1*. Download files from a ClientCommand repository
	320	1*. Download documents within the //Documents// folder
	321	1. Delete the folder //C:\Program Files (x86)\Aagon\ACMP Server\FileRepository// provided that no operational issues are observed.
1.1	322
67.1	323	=== Restoring the Original State ===
1.1	324
67.1	325	If ACMP does not function as expected, you can restore the prior state as follows:
	326
	327	1. Stop the ACMP Server service.
	328	1. Restore the database backup that you created earlier.
	329	1. Delete the //config.xml// file, which is located at //C:\ProgramData\Aagon\ACMP\Server\Config\%{GUID}%// when the Server service exits.
	330	1. Start the ACMP Server service.