Advertised Programs Do Not Download

I was deploying the HP WebCam software to Notebooks and it just would not work.

I even went back to the start and cleared the advertisement, re-created the package and program, cleared the cache on the target client and then readvertised.

It took a bit of log digging but i found it in the end.

1st Log: PolicyAgent on Client – Client receives policy update from triggered schedule (see previous thread)

2nd Log: Execmgr on Client – Client receives advertised program and sends to download

3rd Log: ContentTransferMananger on Client – Client starts downloading to cache. (Enters phase DOWNLOADING_DATA)

4th Log: CAS on Client – Client starts to download but NotifyDownloadProgressEx shows downloaded size 0

5th Log: DataTransferService on Client – the final entry is cdtsjob::joberror follwed by job GUID

At this point nothing else happens. I checked BITS throttling, all ok on server and client.

Thanks for reading this far, here is the good bit…

BITS goes through IIS on the distribution point. So check the logs on the DP. (C:\inetpub\logs\LogFiles\W3SVC1). Check the newest log and the latest entries. Here is mine:

2011-02-18 16:22:42 HEAD /SMS_DP_SMSPKGD$/00100028/WEBCAM_X64_10/BIN/AS_Storage_w32.dll – 80 – Microsoft+BITS/7.5 404 8 0 199
The key here is the code at the end. I have a 404 error. Another common scenario is a 401 error. The number directly after is the subcode, i.e. 404.8 in my case.

Here is the key to the http codes:

401.7 means the applicationHost.config needs to be correctly edited for webDav, 404.8 means part of the path is designated a ‘hidden segment’ in applicationHost.config – you should remember making similar changes when you installed SCCM.

By default, one of the segments hidden in the applicationHost.config is ‘bin’ and HP’s download of software contains bin folders. 

Removing the bin entry from the hiddenSegments section of applicationHost.config resolves the issue.

Hope it helps.


3 thoughts on “Advertised Programs Do Not Download

  1. Nancy Stafford June 15, 2011 / 3:54 pm

    Oh Yes! This solved a few problems we have been having for a while with packages that would not download. I did have to download and install the IIS 7.0 Administrative Pack in order to see the request filtering as we are using Windows Server 2008. The steps are very helpful AND I now have another location to look for log files. Thank you.

  2. Neontiger08 June 18, 2011 / 3:42 pm

    Hi, I was wondering when you deployed the Webcam software what method did you use to see if a machine had Webcam hardware on it? I am trying to create a collection where it has all machines that have a Webcam device of some sort installed, pushing out Polycom CMA Desktop, on it and am struggling to find anyone who has had a successful method. My worst case scenario is creating a collection based on System Model where I know certain machines come with a built in webcam.
    Kind Regards

    • andrewdcraig June 21, 2011 / 8:21 am

      Hi David, Webcams are PnP devices, you could use a WMI query to retireive information on PnP Device Instances:
      gwmi -Namespace root\CIMV2 -Class Win32_PnPEntity | where{$ -like ‘*webcam*’}
      Then create a query-based collection,
      HTH, when i get a minute away from my current project I’ll set up the collection with the query and post the steps and settings here.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s