This doc assumes that allowing LDAV to remove the old AV client works for you; it gets more complicated if you're running something weird that LANDesk can't get rid of.

By default, when you schedule an LDAV deployment, LANDesk will create a deployment package and send it to the client. This deployment package runs vulscan, which removes the old AV client and downloads everything necessary for the new client. That works like a champ on local area networks, because "everything necessary" gets taken care of through Peer Download. Add in some flaky networking though, and you want to make sure the right thing is done... removing the old AV client and not installing the new one would be bad. Here's how to make sure it'll do what you want:

• 
• make sure you select a policy, since you want this to be client initiated. Personally, I would also use an scan and repair settings which displays UI so the user doesn't power down with AV half-installed, but that's your call.
  
• We'll be back to here...
  
• If you need to change the method, do so
  
• This package is something we'll modify. Note the name.
  
• It should be under your distribution packages... edit its properties, and include all the files in ldlogon/antivirus except backups and nt4.

This will cause the agent to download the av files to sdmcache before it runs the remove-old-and-install-new job, which is exactly what you want. If it's disconnected partway through, no big deal.