I have secondary site clients (sccm 2007 r2) that are stuck "waiting for content" for hours now. The package i'm trying to deploy is only 100mb.

Now I have just recently setup secondary sites, so I'm sure there is something I'm missing.

• I have verified that the package has successfully distributed to the secondary site DP.
• I have checked a secondary site computer and in the cache folder the package folder is created, but no files are present, not even temp files.
• The site status for all secondary sites are all listed as "Ok".
• I have tried changing the webDav defaultapppool from "Integrated" to "Classic", waited awhile with no result.
• The setup logs on the secondary site root system drive looks ok.
• I don't see any errors in the distmgr.log.

What else could I check? Any help is appreciated.

Thanks,

Michael

Hi Michael,

Check the client site logs for any error, the below blog will helpful to identify the error in any,

http://blogs.technet.com/b/configmgrteam/archive/2010/01/14/troubleshooting-client-content-download-in-configuration-manager-2007.aspx

Also check if the article in the following link helps:

http://blogs.technet.com/b/configurationmgr/archive/2009/11/04/some-configmgr-2007-clients-never-install-packages-report-status-of-waiting-on-content.aspx

Hi, On the clients, check the CAS.log and clientlocation.log to check where the client is downloading its content from