(Reposted for reference) One particularly hot topic at the Midwest Management Summit 2014 conference last month was a relatively recent but increasingly frequent issue that was called out by Kent Agerlund in his blog post “House of Cards – The ConfigMgr Software Update Point and WSUS” (referred to all week as “the house of cards post”). This issue seemed to be popping up more and more in the community, but I had yet to see it with any of my…
The content side of Software Updates in ConfigMgr can be a bit confusing. Unlike Packages and Applications, in which the entirety of the content is downloaded to the local cache, when the client downloads Software Updates it only downloads the individual update. As such, the Deployment Package is nothing more than a means of getting groups of individual updates out onto the Distribution Points to make them available for download. The Deployment Packages are created independently of the Software Update Groups though,…
Due to some issues with my myITforum.com blog, including losing almost two years worth of posts, I’ve decided to bring up a new blog. Fortunately, I have nearly all the posts I’ve lost cached in WebStory, so I’ll be going back through and re-publishing the ones that I feel may still hold some relevant content. Cheers!
(Reposted for reference) Ran into this issue recently and wanted to document it in case anyone else ran across the same problem. Scenario: I have set up a ConfigMgr 2012 Task Sequence to deploy Windows Server 2012 R2 and I want to customize the server with some Roles and Features after the OS comes down. I have created a PowerShell script (including some basic logging) to add some of the ConfigMgr DP prereqs… …and I’ve created a legacy Package and Program to…