Add an entry to the repository list and specify the folder the new distributed repository uses.
Caution
Do not configure distributed repositories to reference the same directory as your Main Repository. Doing so locks files on the Main Repository, causing pulls and package check-ins to fail and leaving the Main Repository in an unusable state.
For details about product features, usage, and best practices, click ? or Help.
Select Menu → Software → Distributed Repositories, then click Actions → New Repository. The Distributed Repository Builder opens.
On the Description page, type a unique name and select HTTP, UNC, or FTP, then click Next. The name of the repository does not need to be the name of the system hosting the repository.
On the Server page, configure one of the following server types.
HTTP server type or FTP server type
From the URL drop-down list, select DNS Name, IPv4, or IPv6 as the type of server address, then enter the address.
Option
Definition
DNS Name
Specifies the DNS name of the server.
IPv4
Specifies the IPv4 address of the server.
IPv6
Specifies the IPv6 address of the server.
Enter the port number of the server: HTTP default is 80. FTP default is 21.
For HTTP server types, specify the Replication UNC path for your HTTP folder.
UNC server type
Enter the network directory path where the repository resides. Use this format:
\\<COMPUTER>\<FOLDER>.
Click Next.
On the Credentials page:
Enter Download credentials. Use credentials with read-only permissions to the HTTP server, FTP server, or UNC share that hosts the repository.
HTTP or FTP server type
Select Anonymous to use an unknown user account.
Select FTP or HTTP authentication (if the server requires authentication), then enter the user account information.
UNC server type
Select Use credentials of logged-on account to use the credentials of the currently logged-on user.
Select Enter the download credentials, then enter domain and user account information.
Click Test Credentials. After a few seconds, a confirmation message appears, stating that the site is accessible to systems using the authentication information. If credentials are incorrect, check the following:
User name and password
URL or path on the previous panel of the Builder
HTTP, FTP, or UNC site on the system
Enter Replication credentials.
The server uses these credentials when it replicates DAT files, engine files, or other product updates from the Main Repository to the distributed repository. These credentials must have both read and write permissions for the distributed repository:
For FTP, enter the user account information.
For HTTP or UNC, enter domain and user account information.
Click Test Credentials. After a few seconds, a confirmation message appears that the site is accessible to systems using the authentication information. If credentials are incorrect, check the following:
User name and password
URL or path on the previous panel of the Builder
HTTP, FTP, or UNC site on the system
Click Next. The Package Types page appears.
Select whether to replicate all packages or selected packages to this distributed repository, then click Next.
If you choose the Selected packages option, manually select the Signatures and engines and Products, patches, service packs, etc. you want to replicate.
Optionally select to Replicate legacy DATs.
Note
Ensure all packages required by managed systems using this repository are not deselected. Managed systems go to one repository for all packages — if a needed package type is not present in the repository, the task fails. This feature ensures packages that only a few systems use are not replicated throughout your whole environment.
Review the Summary page, then click Save to add the repository. The ePO - On-prem software adds the new distributed repository to its database.