ePO - On-prem ensures secure communication between the client and repository using SSL/TLS certificates.
You must add repository certificate to ePO - On-prem server.
Ensure to use Trellix Agent 5.8.2 extension and packages.
Caution
Ensure to configure distributed repositories to reference the different directory from your Main Repository. Otherwise, it locks files on the Main Repository, causing pulls and package check-ins to fail and leaving the Main Repository in an unusable state.
Select Menu → Software → Distributed Repositories, then click Actions → New Repository. The Distributed Repository Builder opens.
On the Description page, type a unique name for your repository, select HTTP, 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 HTTP server type.
From the URL drop-down list, select one of these options 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.
For HTTP server types, specify the Replication path for your HTTP folder.
Configure HTTPS Repository settings:
Select the Enable HTTPS Communication checkbox to enable the secured communication.
Specify the HTTPS Port: default is 443.
Click Select Repository Certificate to upload the added certificate.
Click Next.
On the Credentials page:
Enter Download credentials. Use credentials with read-only permissions to the HTTP server.
Select Anonymous to enable the anonymous access.
Select HTTP authentication (if the server requires authentication), then enter your ePO account information.
Click Test Connection. 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 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:
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 site on the system
Click Next.
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 selected. 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.