easy solution for you.
You just need to change agent policy for these laptops.
Go to McAfee Agent Policies>click Repository >Click Default> here just move the http repository at first number> Save and apply this policy on these laptops.
So next time agents on these laptops will fetch their updates from http server first. )
easy answer: it doesn't work you CAN'T put it in first Notice the small bar far on the left of the line ? Just next to the positon-number ? That's why it's blocked
An answer would be to just disable the epo, but as we do maintenance on the laptops, they still should be able to update through our local network
however when you select repositories by the order shown (3rd radio button) you should be able to reorder the list (dim grey explanation line just above the box highlight). Did not try, just gave a tip . But once a site is fallback you may not be able to reorder, so it is in a position but the last, after all. In this case I'd attempt to set up a new repository to Mcafee site, HTTP but not fallback and order it first.
As for the heavy timeouts per site until updater gives up taking the next site: I think this is hardcoded
Simply create a new Agent repository policy with the local repository disabled leaving the http source as the only valid one.
Create new a new branch in your system tree, break inheritance and apply the policy. Move all the laptops into that branch
i do not want the local repository to be disabled or left out at all, as i use them when i connect the laptops to the local network. Have to try if i can create a fake local repository that points to a http:// address
The problem is: i can't force the HTTP update to be done in first place, only EPO update in first place
i do not want the local repository to be disabled or left out at all
Ans: 1.Add a local repository with http address as I mentioned above, apply this Agent Policy to the mobile laptops.
Ans: Do not disable local ePO repository and place it as faalback, so when these laptops connects to the local network then they would have fallback updates as well.
i marked them as answers and tried, as adding the HTTP to the NAI updater works, but my problem still persists: the agent takes 5minutes to start (aka: showing up in the tray) and no update is done. sometimes it is, sometimes not.
I finished up by adding a shortcut to the desktop to mcupdate.exe /update so the update can be performed manually. This sometimes starts the updater, sometimes not. I guess it's not starting the updater because the agent desperately first tries to do sth else....