I'm currently testing a distribution package I've created to change some of the Office 2003 licenses used across our network. The idea is to remove Office 2003 pro and replace it with Office 2003 std (in addition it'll apply Office 2003 sp3 & install Access 2007 runtime).
The problem I have is the when deploying the package (which is ~600Mb) to a test box on a remote site (over adsl link - 512k) it's not reporting a successful completion. Checking the machine itself and the task has completed correctly (all applications are installed) - the sdclient log file is complete and returns the expected exit code, but the whole task takes around 12 hours to complete (I'm using a bandwidth aware multicast push, limited to 25% of available bandwidth).
Viewing the log file from the console only has information about the process up to around 6 hours into the task.
Presumably there's a limit to how long a target will stay in the 'active' list before timing out and failing; my question is can this be increased at all, or do I need to look at changing my deployment package?
I've added the batch file used for the script & log files mentioned above if these are of any use in aiding my query.
Any advice appreciated.