If you build your main Distribution Package to run the install commands, you could setup an additional distribution package as a dependency that simply extracts the files.
We do something similar for extremley large installs. We bundle the installation files in several self extracting compressed files and set this up as its own distribution package. We set the Detection logic to the last file that is extracted. We also do this because we extract and keep our installation files in a directory outside of SDMCache.This part is silent.
The main install distribution package is setup so that it has a dependency on our file extraction package, and is generally much smaller in size, 1-2MB and contains the installation instruction commands. This part we usually keep silent, but is also where we would display something to the end user.
I suppose if you setup your Scheduled Task\Delivery method as a Policy\Required Installation, it would work best for your remote users. We use this generally for our PUSH jobs.
On the other hand... hopefully you are using LANDesk patching for acrobat updates and have a gateway setup for better management of your mobile users. The new features to also download the patches direct from the origin (ex: direct from adobe instead of through our gateway or vpn) is something we have been waiting for.