Once you install the latest ConfigMgr service packs, or v.Next, the "Operating System Installers" are called OS upgrade packages, since that's the only case where they need to be used: for performing an in-place upgrade to a new OS (Windows 10).
Thanks, -Michael From: [email protected] [mailto:[email protected]] On Behalf Of Schwan, Phil Sent: Thursday, June 4, 2015 3:46 PM To: [email protected] Subject: [MDT-OSD] RE: Patching install.wim Correct, you no longer need to use the Operating System Installers, particularly for Win7 and later. It does make life a bit easier :) -Phil From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Miller, Todd Sent: Thursday, June 4, 2015 5:27 PM To: [email protected]<mailto:[email protected]> Subject: [MDT-OSD] RE: Patching install.wim Hmm. I didn't know it was possible to import and use the Install.wim in the build and capture instead of running Windows setup. I think that got added in SP1 of 2012 and I missed it. (old dog, meet new tricks) So there's no reason to have "Operating System Installers" for Win7+ and just dump everything in the "OS Images" instead. There is really no need to run the "setup" method with Windows 7 anymore? Oh, well. Too late for now... I am trying out this method , which updates the Intall.wim which is then imported and runs still as an Windows Setup in Build & Capture https://www.raymond.cc/blog/create-an-integrated-up-to-date-windows-7-install-disc/ Thanks for the suggestions. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Jason Sandys Sent: Thursday, June 04, 2015 2:46 PM To: [email protected]<mailto:[email protected]> Subject: [MDT-OSD] RE: Patching install.wim This is what I do also. I actually inject a handful of others things manually like 2775511 and IE11 before I even import it into ConfigMgr. Then I use offline updates and then use this updated WIM during a B&C to add other things as well. Note that I add the updates (like 2775511) offline first because it superseded many updates as does adding IE11 and thus prevents them from having to be injected by the offline updates process. J From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Schwan, Phil Sent: Thursday, June 4, 2015 2:18 PM To: [email protected]<mailto:[email protected]> Subject: [MDT-OSD] RE: Patching install.wim Why not import install.wim as an Operating System Image and use Scheduled Updates to slipstream updates into the base media? I do it all the time; it was my primary workaround for the multi-reboot patch issue. -Phil _________________________________________________________________ Phil Schwan | Technical Architect, Enterprise Windows Services Microsoft VTSP ([email protected]<mailto:[email protected]>) Project Leadership Associates | 2000 Town Center, Suite 1900, Southfield, MI 48075 Lync: 312.756.1626 Mobile: 419.262.5133 www.projectleadership.net<http://www.projectleadership.net/> [linkedin_logo-19x20] <http://www.linkedin.com/in/philschwan> [Twitter-Logo1-20x20] <https://twitter.com/philschwan> [wordpress-logo3] <http://myitforum.com/myitforumwp/author/philschwan> [Description: Description: Description: Arrow email]Lead with Strategy. Leverage Technology. Deliver Results. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Miller, Todd Sent: Thursday, June 4, 2015 2:10 PM To: [email protected]<mailto:[email protected]> Subject: [MDT-OSD] RE: Patching install.wim I think we are talking about two different things. I am asking about patching the install.wim file that comes on the Windows 7 x64 DVD. I think you are talking about injecting patches into your captured WIM - using offline servicing. SCCM will not apply patches to install.wim images loaded into the "Operating System Installers" - only the captured images in "Operating System Images" Yes, I too inject patches into the Image WIM between Build and Capture refreshes. The problem I am trying to solve is the 4-6 hour build and capture time that is done to create the patched hybrid image that is then used for client deployment. I would like to reduce the time it takes and increase the reliability of the Build and Capture task sequence. It is failing about 25% of the time and has ~ 190 post SP1 patches to apply and takes many hours to run. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Boyles, Peter J {BIS} Sent: Thursday, June 04, 2015 12:57 PM To: [email protected]<mailto:[email protected]> Subject: [MDT-OSD] RE: Patching install.wim I use patch injection to keep WIMs updated and it works great. Understand that some patches cannot be installed in offline mode. It is a balancing act between WIM size buildup and patches that cannot be installed offline that determine when to create a new WIM for deployment. Peter Boyles BIS Engineering Analyst PepsiCo Inc. | Global End User Services | GEUS Deploy From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Miller, Todd Sent: Thursday, June 4, 2015 12:40 PM To: [email protected]<mailto:[email protected]> Subject: [MDT-OSD] Patching install.wim I am thinking of updating my install.wim by slipstreaming patches into it. I want to do this to reduce the number of patches that are required to be installed during my build and capture task sequence. Is this a good/bad/safe idea? http://scug.be/sccm/2011/07/27/windows-7-osd-deployment-sccm-or-mdt-and-starting-with-a-patched-media-more-secure-amp-saves-time/ or http://blogs.technet.com/b/configmgrdogs/archive/2012/02/15/applying-windows-updates-to-a-base-wim-using-dism-and-powershell.aspx or http://happysccm.com/optimize-the-build-and-capture-time-and-size-sccm-build/ (I am not interested in using light touch for build and capture) ________________________________ Notice: This UI Health Care e-mail (including attachments) is covered by the Electronic Communications Privacy Act, 18 U.S.C. 2510-2521, is confidential and may be legally privileged. If you are not the intended recipient, you are hereby notified that any retention, dissemination, distribution, or copying of this communication is strictly prohibited. Please reply to the sender that you have received the message in error, then delete it. Thank you. ________________________________ ________________________________ Notice: This UI Health Care e-mail (including attachments) is covered by the Electronic Communications Privacy Act, 18 U.S.C. 2510-2521, is confidential and may be legally privileged. If you are not the intended recipient, you are hereby notified that any retention, dissemination, distribution, or copying of this communication is strictly prohibited. Please reply to the sender that you have received the message in error, then delete it. Thank you. ________________________________ ________________________________ Notice: This UI Health Care e-mail (including attachments) is covered by the Electronic Communications Privacy Act, 18 U.S.C. 2510-2521, is confidential and may be legally privileged. If you are not the intended recipient, you are hereby notified that any retention, dissemination, distribution, or copying of this communication is strictly prohibited. Please reply to the sender that you have received the message in error, then delete it. Thank you. ________________________________
