I've been trying to find time to dig into this in more detail, but on machines
which do a WIM boot, (HP Stream, etc.) would this be helpful in reducing the
space utilization after updates are applied to the machine? The challenge with
the small SSD machines like the Streams it that while they start out with about
of the 3rd of the disk available, it fills up insanely fast.
--
There are 10 kinds of people in the world...
those who understand binary and those who don't.
From: [email protected] [mailto:[email protected]] On
Behalf Of Boyles, Peter J {BIS}
Sent: Thursday, June 4, 2015 1:57 PM
To: [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.
________________________________
