Showing results for 
Search instead for 
Did you mean: 
Level 10
Report Inappropriate Content
Message 1 of 1

Extra.dat Deployment Client Task Behaviours


I wanted to clarify the behavior of performing Extra.dat upgrades via ePO client tasks.


We have an extra.dat checked into the master repository.

We have multiple distributed repositories.

We have initiated a replication task to deploy the extra.dat to the have multiple distributed repositories, but, either:

  1. The replication has not completed on repositories yet, or
  2. The replication has failed on some repositories.


  1. If we run a client update task to deploy the Extra.dat to a PC whose closest repository doesn't have the new Extra.DAT (it still has an old Extra.DAT), will the clients attempt to pull the Extra.dat from another repository?  Or will the update task fail?
  2. If we have an existing client update task created already for an old Extra.dat that's been set to run "asap" months ago, will the client task re-run again "asap" once the new Extra.dat is checked in?  Usually to be on the safe side I delete and recreate the client task, but I just wanted to confirm the behavior.
More McAfee Tools to Help You
  • Subscription Service Notification (SNS)
  • How-to: Endpoint Removal Tool
  • Support: Endpoint Security
  • eSupport: Policy Orchestrator
  • Community Help Hub

      New to the forums or need help finding your way around the forums? There's a whole hub of community resources to help you.

    • Find Forum FAQs
    • Learn How to Earn Badges
    • Ask for Help
    Go to Community Help

    Join the Community

      Thousands of customers use the McAfee Community for peer-to-peer and expert product support. Enjoy these benefits with a free membership:

    • Get helpful solutions from McAfee experts.
    • Stay connected to product conversations that matter to you.
    • Participate in product groups led by McAfee employees.
    Join the Community
    Join the Community