The package won't be pre-staged. I had the same issue when rolling out Office 2010 to about 1200 Sales Reps. The package I had to send them was over 1 GB.
I ended up creating a second managed software delivery that moved (not copied) all of the package files to the cache folder for the installation. So that when the installation Managed Software Delivery was kicked off by the end user, the detection rule ran and found the files.
The batch I used is below:
copy /Y FilesExist.txt C:\Tools
md "C:\program files\altiris\altiris agent\agents\softwaremanagement\software delivery\{INSTALL PACKAGE GUID}"
move "C:\program files\altiris\altiris agent\agents\softwaremanagement\software delivery\{STAGING PACKAGE GUID}\cache" /Y "C:\program files\altiris\altiris agent\agents\softwaremanagement\software delivery\{INSTALL PACKAGE GUID}"
exit
The first line is for compliance only, though I probably should have chosen to look for a particular file within the package itself in its new location. :)
The second and third lines make the directory that the installation files will live in, and then moves the entire cache folder of the staging package to it.
So the staging delivery is this:
- Second Managed Software Delivery (the STAGING PACKAGE referenced above) downloads to its own cache folder under "c:\program files\altiris\altiris agent\agents\softwaremanagement\software delivery\{STAGING PACKAGE GUID}\cache" folder
- The batch file copies my compliance file to C:\Tools
- The directory for the real installation (the INSTALL PACKAGE referenced) is created
- The staging files (cache folder) are then moved from the {STAGING PACKAGE GUID} folder to the {INSTALL PACKAGE GUID} folder
Then, when your users kick off the install on their own, the download task only verifies the files exist in the {INSTALL PACKAGE GUID}\cache folder, which takes seconds instead of minutes or hours.
Hope this helps you.