When using the Use Toolkit Package task in a ConfigMgr 2007 task sequence, the Microsoft Deployment Toolkit 2010 Update 1 files package specified in the Use Toolkit Package task does not download correctly when the Distribution Point is on a Windows Server 2008 or newer server. The behavior will be different depending on the download method chosen under the Distribution Points tab in the properties of the advertisement.
Download content locally when needed by running task sequence
When the Task Sequence reaches the Use Toolkit Package task, the files for the package specified in the Use Toolkit Package will start to download and the progress bar will reach about 27%. The download will then all of a sudden stop, restart from the beginning, only to reach 27% again, and then restart again. On the third attempt it will the progress bar will get past 27% and finish downloading successfully. Reviewing the SMSTS.log on the client PC will show the following error:
Downloaded file from http://<DP_Server>:80/SMS_DP_SMSPKG<Drive_Letter>%24/<Package_ID>/Tools/OSDResults/OSDResults.exe to D:\_SMSTaskSequence\Packages\<Package_ID>\Tools/OSDResults/OSDResults.exe InstallSoftware
dwStatusCode>=200 && dwStatusCode<=299, HRESULT=80004005 (e:\nts_sms_fre\sms\framework\tscore\downloadcontent.cpp,1090) InstallSoftware
WinHttpQueryHeaders() returns status code 404 (Not Found) InstallSoftware
Download() failed with 0x80004005 InstallSoftware
DownloadFile(sSourceFile, sDestinationFile, ulTotalSizeRequired, ulDownLoaded), HRESULT=80004005 (e:\nts_sms_fre\sms\framework\tscore\downloadcontent.cpp,1175) InstallSoftware
Error downloading file from http://<DP_Server>:80/SMS_DP_SMSPKG<Drive_Letter>%24/<Package_ID>/Tools/OSDResults/OSDResults.exe.config to D:\_SMSTaskSequence\Packages\<Package_ID>\Tools/OSDResults/OSDResults.exe.config InstallSoftware
DownloadFiles(sSource, setDirs, setFiles, sDestination), HRESULT=80004005 (e:\nts_sms_fre\sms\framework\tscore\resolvesource.cpp,2434) InstallSoftware
Retrying download... InstallSoftware
The above error will be displayed a second time, followed by the following line after the second failure:
Tried all the available http based locations. SMB based locations will be attempted now. InstallSoftware
After the second error and the above message, the download will be tried a third time and will then succeed.
Examining the IIS logs on the distribution point server will reveal the following error:
<GMT_Date> <GMT_Time> <DP_Server_IP> GET /SMS_DP_SMSPKG<Drive_Letter>$/<Package_ID_Of_Pacakage_In_Use_Toolkit_Package>/Tools/OSDResults/OSDResults.exe.config - 80 - <Client_IP> SMS+TS 404 7 64 15
Download all contents locally before starting task sequence
When the advertisement is initiated either manually via the Run Advertised Programs control panel or automatically via a mandatory assignment, the download for the packages of the Task Sequence begins but never completes. Because the download for the Task Sequence packages never completes, the Task Sequence never begins or launches and the SMSTS.log is never created on the client PC.
Reviewing client logs associated with downloading packages and executing the Task Sequence (execmgr.log, CAS.log, DataTransferService.log, ContentTransferManager.log) will not contain any errors. The client logs indicate that the downloads for the packages have begun, but the downloads never complete. Some of the client logs may have messages indicating that the downloads are in a pending or waiting state such as:
DataTransferService.log
Execute called for DTS job '{GUID}'. Current state: 'PendingDownload'.
execmgr.log
Execution Request for package <Task_Sequence_ID> program * state change from WaitingDependency to WaitingContent execmgr
Persisting task sequence request for program * package <Task_Sequence_ID> in state WaitingContent execmgr
If the advertisement for the Task Sequence was initiated manually via the Run Advertised Programs control panel, the Program Download Status window will show a progress bar that initially shows progress, but eventually stops and does not complete. The percentage complete will fail at a randomly different point each time the download is attempted.
Examining the IIS logs on the distribution point server will reveal the following error:
<GMT_Date> <GMT_Time> <DP_Server_IP> HEAD /SMS_DP_SMSPKG<Drive_Letter>$/<Package_ID_Of_Pacakage_In_Use_Toolkit_Package>/Tools/OSDResults/OSDResults.exe.config - 80 - <Client_IP> Microsoft+BITS/7.5 404 7 0 218
Running Bitsadmin.exe on the client PC with the following command line:
bitsadmin.exe /list /allusers /verbose
while the download is in the hung state will reveal the following error:
ERROR FILE: http://<DP_Server>:80/SMS_DP_SMSPKG<Drive_Letter>$/<Pacakge_ID>/Tools/OSDResults/OSDResults.exe.config -> C:\Windows\system32\CCM\Cache\<Pacakage_ID>.<Source_Version>.<GUID>\Tools/OSDResults/OSDResults.exe.config
ERROR CODE: 0x80190194 - HTTP status 404: The requested URL does not exist on the server.ERROR CONTEXT: 0x00000005 - The error occurred while the remote file was being processed.
Access content directly from a distribution point when needed by the running task sequence
No download issues are experienced when the advertisement for the Task Sequence is set to run from the distribution point (DP).