AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
Press question mark to learn the rest of the keyboard shortcuts Log In Sign Up User account menu 0 Waiting for content.Immediately after taking the 5-day SCCM class from Microsoft, my deployments to the clients werent working as expected.
Lots of clients would end up in Unknown in deployment status for days before finally succeeding. Another issue was that clients would be Waiting for content for days, even though the package is on the distribution point, and its very tiny (1k batch script). Over the past few months, the SCCM admin upgraded to 1610, increased the WSUS application pool in IIS (windowsupdate.log was showing alot of 0x80072EE2 timeouts), cleaned up the database, and re-indexed the SQL database. While this has helped performance (in the console at least) immensely, the timeouts continue, and Waiting for content for small 1k batch scripts are still an issue. ![]() We have 30 boundaries defined by IP range, and out of those 30, 14 are assigned to a boundary group A, 15 are assigned to boundary group B, and the rest are assigned to boundary group C. In Properties for group A and B, under the References tab, the Assigned Site has our site selected, but under site system servers, its blank. In group C, the site system servers has our site listed in there. When I pushed a 1k script to group A along with a forced policy update yesterday, almost all the clients are sitting there Waiting for content still this morning. When I deployed the same script to clients in group C, along with a forced policy update, the clients received and completed it within 5 minutes. Sccm Deployment Waiting For Another Program Download Request OnlyThis is whats showing up in the CAS log: Location update from CTM for content XXX001E3.1 and request D4CC22C0-74A8-41C3-8176-2BD0AE8FC6CD ContentAccess 1022018 6:05:22 AM 4168 (0x1048) Download request only, ignoring location update ContentAccess 1022018 6:05:22 AM 4168 (0x1048) The Default-Site-Boundary-Group does have the site in the site system servers section under references, though, with a fallback time of 120 minutes. Could this be the cause of the Waiting for content 5 comments share save hide report 50 Upvoted This thread is archived New comments cannot be posted and votes cannot be cast Sort by best. Sure enough, the next day, there were NO Waiting for content. I deployed a 1k script to 26 machines, and after a forced computer policy update, within 5 minutes, they had all downloaded and executed the script. Appreciate the feedback.:) level 1 1 point 2 years ago I had to re read your post a few times lol. I dont know what purpose having the site system servers blank in the boundary groups serves. Im going to have him add them to the 2 boundary groups to see if content kicks off on the deployments. Thanks for validating my theory.:) Continue this thread View Entire Discussion (5 Comments) More posts from the SCCM community Continue browsing in rSCCM rSCCM All things System Center Configuration Manager. Members 261 Online Created Nov 11, 2011 Join help Reddit App Reddit coins Reddit premium Reddit gifts about careers press advertise blog Terms Content policy Privacy policy Mod policy Reddit Inc 2020.
0 Comments
Read More
Leave a Reply. |