I've always preferred to add AV afterwards, Doing it with the agent is really only suited for when you do a new machine.
See what happens when you push it out later, not through agent config though, do it using the agent setting options as in the screenshot below.
MarXtar Ltd/MarXtar Corporation
LANDESK One Development Partner
The One-Stop Shop for LANDESK Enhancements
Because this is a trial period I am pushing the AV out to test machines afterwards and using the method in your screenshot. I thought maybe pushing it out with an agent might be better, but the agent install just fails too. I tried installing the AV via the agent install on a freshly imaged machine and it works. So the agent failing must be because of McAfee.
I have also tried relaxing the McAfee security. I set McAfee to allow the McAfee processes to be stopped, but that did not seem to help.
When I create a scheduled task from the Install/Update security components I notice that it's running a script with vulscan.exe
I think I should be able to use this. I've created a batch script to remove McAfee from the command line. If I could then schedule this to run on the next boot then have the batch script trigger a reboot then it would work.
I've tried putting it in the RunOnce registry section but it won't launch. I think I need something to run the command when the user logs into the desktop versus the machine booting up. Is there anything like that?
I'm trying to minimize the time when my clients don't have AV installed and to make sure that all my clients get AV reliably.