jackd

Bump - any ideas for what to investigate here? Thanks

Forgot to mention that once the TS finishes and the machine gets into windows I can run the install fine and the client is deployed.

I am using an MDT integrated UDI task sequence to deploy an operating system (Win7 x64), install the SCCM client then install applications/packages. After the OS .wim file is applied the SCCM Client package is downloaded to C:\_SMSTaskSequence\OSD\SP100017\ The machine then reboots and goes back into the task sequence to install the client, but fails. The appropriate bit of ccmsetup.log is below and the full file is attached Despite copying the files locally to C:\_SMSTaskSequence\OSD\SP100017\ it is looking for them in C:\windows\ccmsetup\, when it doesnt find them it tries to download them via BITS. The SCCM server is serving these files up ok (if I stick the URL to the file in a browser it serves it up without needing authentication). From hitting F8 during the task sequence and running "bitsadmin /list /allusers /verbose" it shows the BITS jobs are there but in a suspended state. Running "bitsadmin /listfiles <ID of bits job>" it shows no files in any of the bits jobs. "bitsadmin /reset" won't cancel the jobs as they are running under SYSTEM. Also tried stopping the bits service, deleting the BITS related files under C:\ProgramData\Microsoft and starting the service, which clears the jobs from BITS but when ccmsetup.exe is rerun the jobs are readded as suspended and the same thing happens. I also tried pausing the TS, copying the client files from C:\_SMSTaskSequence\OSD\SP100017\ to where it is expecting (C:\Windows\ccmsetup\) then resuming. However even though client.msi is in C:\Windows\ccmsetup\ where it is looking for it, it still tries to grab it via BITS and fails C:\Windows\ccmsetup\client.msi defintately exists locally (tried with both 32 and 64 bit files) but for some reason it still wants to go off and grab it from the SCCM server via BITS. I've searched high and low over the internet and read all the suggestions but am stumped. ccmsetup.log