True, MDT makes it very simple to add/remove applications in the build. It is that very fact that makes MDT perfect for generating your base images. Particularly if you’re using SCCM to deploy.
Every case is going to be different and each IT shop needs to evaluate the options to find what best fits for them. In our case, putting Office into the base image was the best option for us (same with the Oracle client). Deploying the base image with Office included was faster than deploying a :lighter” base image and then installing Office. Besides the speed of the deployment (which was our top concern) having Office in the base image saved the disk space of having a base image and then a separate package for Office on all of our SCCM distribution points. The other side of that blade though is exactly what you point out. We are looking to upgrade Office, that mandates that we generate a new base image. (Granted MDT makes that simple.) Our hardware fleet has evolved since we started using SCCM for OSD. Back then we had laptops with 5400 RPM drives. Now everything is coming in with SSDs. We’ve also upgraded our SCCM infrastructure, so disk space on the DPs isn’t as much of a concern now. When we move to Office 2016 I may opt to keep it out of the base image and install it at build time. The bottom line for all this is that you need to test. There is no “one size fits all” solution. Take what you hear, take the opinions that everyone offers and test. See what works best for you in your environment. What are your concerns and how do they rank? Once you know your criteria you can then test to see what will meet your needs. Thanks Mike From: [email protected] [mailto:[email protected]] On Behalf Of David Landry Sent: Wednesday, November 4, 2015 11:42 AM To: [email protected] Subject: RE: [MDT-OSD] Whats in your base image ? Putting any application into the image makes no sense to me. Except for something like Silverlight. Nothing but critical updates and OS service packs goes into my base image. To put any application into the image, whether it is Adobe Reader or Office means any time you want to move to a new version of that software, you need to redo your image. MDT was designed to make it easy to remove, add, and/or replace applications you want to deploy, without touching your base image. It is easier to create a new software distribution package than it is to create an entire new image whenever you change from one application to another. Anything short of this means you are not using the full potential of MDT. But, if you are willing to accept the additional maintenance that goes along with putting applications into the image … then you should do it. Regards, Dave Landry From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Chris Barnes Sent: Wednesday, November 04, 2015 11:12 AM To: [email protected]<mailto:[email protected]> Subject: RE: [MDT-OSD] Whats in your base image ? Makes sense. I have always installed 3rd party AV during the deployment process, not on the base image, just know it’s possible with Symantec. Good to know about issues with Sysprep. Chris Barnes Coretek Services | Enterprise Consultant • 248.684.9400 ext 276 office • 248.767.4415 cell • [email protected] • http://www.coretekservices.com<http://www.coretekservices.com/> From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Johan Arwidmark Sent: Tuesday, November 03, 2015 10:05 PM To: [email protected]<mailto:[email protected]> Subject: RE: [MDT-OSD] Whats in your base image ? Third party antivirus are the top reasons for issues with sysprep, so to avoid current and future issues it’s in general better to install them at deployment time. / Johan From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Chris Barnes Sent: den 3 november 2015 08:09 To: [email protected]<mailto:[email protected]> Subject: RE: [MDT-OSD] Whats in your base image ? There is a file that you can delete after the install that will force it to create a new GUID when its re-imaged, gets around this issue. If you google around for how to get SEP on an imaged machine you will find the Symantec KB. Chris Barnes Coretek Services | Enterprise Consultant • 248.684.9400 ext 276 office • 248.767.4415 cell • [email protected] • http://www.coretekservices.com<http://www.coretekservices.com/> From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Steve Whitcher Sent: Tuesday, November 03, 2015 9:48 AM To: [email protected]<mailto:[email protected]> Subject: Re: [MDT-OSD] Whats in your base image ? It's been quite a while since that decision was made, but as I recall it was due to SEP generating unique ID's for each client at the time of install. If we included it in the base image, it confused the management server when it had the 'same' computer checking in with it many times. On Tue, Nov 3, 2015 at 8:36 AM, Karamol, David S <[email protected]<mailto:[email protected]>> wrote: Steve, Is there a reason you didn’t put Symantec in your base image? From: [email protected]<mailto:[email protected]> [mailto:[email protected]<mailto:[email protected]>] On Behalf Of Steve Whitcher Sent: Tuesday, November 03, 2015 8:30 AM To: [email protected]<mailto:[email protected]> Subject: Re: [MDT-OSD] Whats in your base image ? Office Foxit Enterprise Reader 7zip And of course windows and office updates. During deployment of the base image, we add Symantec Endpoint Protection and (Unfortunately) Java. That covers the majority of what our users need, as our LOB app is delivered using RemoteApp. On Tue, Nov 3, 2015 at 8:16 AM, Bain.John <[email protected]<mailto:[email protected]>> wrote: When preparing your base image for sysprep, do you think it’s worth installing your default desktop applications into your image before capturing your wim ? John John Bain – CIC Engineering Office: JETS C657 | Tel: 613-437-6829<tel:613-437-6829> ________________________________ THIS E-MAIL AND ANY MATERIALS TRANSMITTED WITH IT MAY CONTAIN CONFIDENTIAL OR PROPRIETARY MATERIAL FOR THE SOLE USE OF THE INTENDED RECIPIENT. ANY REVIEW, USE, DISTRIBUTION OR DISCLOSURE BY OTHERS IS STRICTLY PROHIBITED. IF YOU ARE NOT THE INTENDED RECIPIENT, OR AUTHORIZED TO RECEIVE THE INFORMATION FROM THE RECIPIENT, PLEASE NOTIFY THE SENDER BY REPLY E-MAIL AND DELETE ALL COPIES OF THIS MESSAGE. ********************************************************** Electronic Mail is not secure, may not be read every day, and should not be used for urgent or sensitive issues
