You can manually inject into any WIM. Where is creating your hybrid image failing?
If you want to place all patches into a directory and have DISM inject everything it can into the WIM it works great. Just point DISM to the directory with all the OS patches (no need to call each patch individually). Review the log file for what patches could not be injected. What we do: To create our deployment WIMs, we have an OS deployment package to build a VM for the base OS. The package joins to the patching backend and calls patching. The VM logs in as local admin and runs a script to ensure all tasks are complete. Its last step is to pop a completion message. We review the system for completion then save a copy of the VM at that point. After we capture the VM so we can use it for the configured deployment WIMs, we run our sysprep and capture task to get the base OS deployment WIM from the VM. Then restore the VM, add all required components for the next deployment image (we have a task set to call for each image required), review, run the sysprep and capture task. Repeat until you have all your deployment WIMs. We rarely recreate the base VM. Simply fire it up and patch. Save the updated VM and recapture the various deployment WIMs. Peter Boyles BIS Engineering Analyst PepsiCo Inc. | Global End User Services | GEUS Deploy From: [email protected] [mailto:[email protected]] On Behalf Of Miller, Todd Sent: Thursday, June 4, 2015 1:10 PM To: [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. ________________________________
