You can use distributed repositories to update the engine and content files efficiently on systems in your organization. Distributed repositories enable you to host security content locally throughout your network so that client systems can receive updates more quickly.
When planning a content file update strategy, consider the following:
Number of clients
Number of sites
Number of systems at each remote site
How remote sites access the Internet
Designate at least one system in your organization to retrieve updates from the Trellix download site. Once downloaded to your organization, replicate the updated files to distributed repositories throughout your organization. Then, use Trellix Agent Product Update client tasks to update client systems from the distributed repositories.
Product Update tasks enable you to:
Schedule network-wide content file rollouts.
Use a schedule to stagger content file updates or phase in updates to different parts of the network at convenient times and with minimal intervention.
Split duties for rollout administration.
Keep update traffic primarily internal and increase network bandwidth efficiency by using different servers or domain controllers, in different network regions or divisions. This strategy also reduces the potential for network security breaches.
Reduce updated content or engine file download waiting time.
Traffic on computers protected by Trellix increases dramatically on regular content file publishing dates and whenever new product versions are available. Avoiding the competition for network bandwidth enables you to deploy your new software with minimal interruptions.