good advice from the guys above, I'd also suggest you try both approaches (fat versus thin image), and only include updates and apps that everyone will use that don't change too often, in fact i cover this in my book, also on amazon - http://www.amazon.com/Windows-noob-Guides-Configuration-Manager-2012/dp/9187445166/ref=sr_1_1?s=books&ie=UTF8&qid=1449000925&sr=1-1
On Tue, Dec 1, 2015 at 8:49 PM, <[email protected]> wrote: > Bake updates into your reference image. (this will save you the most time > per machine.) > > > > If every machine gets office, bake that in as well. Plus office updates. > > > > Only put applications that don't change often into the image ( not java, > not flash player, not adobe reader). > > > > This is called a "hybrid" image, not fully thin, but not thick either. > > > > This way you can update it as often as you want to lower the number of > patches applying during the imaging process, but you aren't pinned to > updating every time adobe has a zero day. > > > > If your new to OSD the following books are very useful, heck I reference > them all the time as well: > > > > > http://www.amazon.com/Stealing-Pride-Vol-Customizations-ConfigMgr/dp/9187445034/ref=sr_1_1?ie=UTF8&qid=1448999110&sr=8-1&keywords=stealing+with+pride > > > > > http://www.amazon.com/Deployment-Fundamentals-Vol-Real-World-Infrastructure-ebook/dp/B00OI2H47S/ref=dp_kinw_strp_1 > > > > Here are some great reference sites: > > http://deploymentbunny.com/ > > > > http://deploymentresearch.com/ > > > > > ------------------------------ > *From:* [email protected] [[email protected]] > on behalf of Beardsley, James [[email protected]] > *Sent:* Tuesday, December 01, 2015 2:26 PM > *To:* [email protected] > *Subject:* [mssms] Plain image or fully loaded? > > Whats the recommended way of building an image? We’re getting ready to > start using OSD (previously used standalone MDT) and we’re trying to decide > if we go with how we’ve done things in the past where we load a ton of apps > that everyone uses on to the image and then capture it. Or, is it > recommended to simply capture a plain OS-only image and then build apps > into the task sequence to install afterwards? I know that everyone probably > has their own method of building an image but I’d appreciate some insight > on which one you use and why… > > > > In our testing (granted this may have been due to the hardware of the OSD > server vs the MDT server), we’ve found that the time it takes to do a plain > image and then install updates and apps afterwards via TS were taking an > hour or more for each computer. On the other hand, when we stuffed a bunch > of apps on to the image and captured it and deployed it via MDT, we were > able to image a computer in about 25-30 minutes. That’s quite a big > discrepancy so needless to say, I’m having trouble convincing some within > our group who are responsible for imaging machines all day to go with the > plain image + subsequent task sequence method. > > > > Could anyone provide links for recommendations on how to setup the image > for OSD and if you have any good general OSD-related links, I’d love to see > them. > > > > Thanks, > > > > *James Beardsley |* Firm Technology Group > > Dixon Hughes Goodman LLP > > > > [image: cid:8644FC49-D5C9-45AE-B387-04FAFC0CC7A5] <http://www.dhgllp.com/> > > > ------------------------------ > > *Confidentiality Notice:* This e-mail is intended only for the addressee > named above. It contains information that is privileged, confidential or > otherwise protected from use and disclosure. If you are not the intended > recipient, you are hereby notified that any review, disclosure, copying, or > dissemination of this transmission, or taking of any action in reliance on > its contents, or other use is strictly prohibited. If you have received > this transmission in error, please reply to the sender listed above > immediately and permanently delete this message from your inbox. Thank you > for your cooperation. > > >
