Download and execute is default in 2012 (and 2007) so unless you explicitly changed it and ensured that the content was available separately in a DP share, then it will be download and execute.
Boundaries are the primary culprit to review as mentioned. J From: [email protected] [mailto:[email protected]] On Behalf Of Dzikowski, Michael Sent: Wednesday, January 8, 2014 4:45 PM To: '[email protected]'; '[email protected]' Subject: RE: [mssms] mssms: Waiting for content - sccm 2012 Boundaries? Anything different with those clients? Maintenance Windows? Sent with Good (www.good.com<http://www.good.com>) -----Original Message----- From: Taxter, Latisha [[email protected]<mailto:[email protected]>] Sent: Wednesday, January 08, 2014 04:43 PM Central Standard Time To: [email protected]<mailto:[email protected]> Subject: [mssms] mssms: Waiting for content - sccm 2012 I have a package that I pushed to a number of pcs. Half of them installed, and the other half are stuck at waiting for content. I did not have this set to download to cache. They are all assigned and active. What can I look at on the client to find out why? Thanks. Latisha Taxter [email protected]<mailto:[email protected]> [email protected]<mailto:[email protected]> • 208-625-4192 È509-953-9085 http://www.kootenaihealth.org Confidentiality Statement: The contents of this email and any attachments are confidential. They are intended for the named recipients only. If you have received this email in error, please notify the system manager or the sender immediately and do not disclose or provide copies of the contents to anyone.
