But how big is your image when you add office updates, and how long does this take to replicate out to other locations that might be using SCCM for OSD?
-Fritzroy From: [email protected] To: [email protected] Subject: Re: [mssms] RE: Patch/WIM Injection Date: Tue, 28 Oct 2014 15:06:14 +0000 I still capture a reference image since we add office into our image. ConfigMgr doesn't patch office when you apply the update list to the WIM. I cut about an hour off of the image time by having office updates inside of the WIM. Thanks, Chris Brucker On Oct 28, 2014, at 11:01 AM, John Aubrey <[email protected]> wrote: I try to remember to inject the updates into the image every month, but forget a lot of time. Every few months I’ll go and recreate my image from a reference VM. I just run out of time to do it any more often. I also put very little into our actual image. The task sequence handles all the software installs. From: [email protected] [mailto:[email protected]] On Behalf Of Bradley, Matt Sent: Tuesday, October 28, 2014 10:55 AM To: [email protected] Subject: [mssms] Patch/WIM Injection I’ve read that some people do not like injecting monthly patches directly into the OS WIM. Some prefer to just capture reference images. Being that a bad patch could be removed from a WIM if it was determined to be bad, I’d like to hear some feedback on why some choose to still stay away from this method, and stay with reference image capture. Thanks. The information contained in this message from First Financial Bancorp or its affiliates and any attachments are confidential. It is not intended for transmission to, or receipt by, anyone other than the addressee(s), or a person authorized to deliver it to the named addressee(s). If you have received this message in error, you are prohibited from copying, distributing or using the information. Please contact the sender immediately by return email and delete the original message.
