We do, but that’s because we use a B&C with ConfigMgr. We don’t build our image with MDT. No issues here, the build in task cleans it up perfectly.
Heres our client switches: SMSCACHESIZE=51200 SMSMP=SERVER CCMLOGMAXSIZE=5000000 CCMLOGMAXHISTORY=5 PATCH="%_SMSTSMDataPath%\OSD\CAS00805\x64\hotfix\configmgr2012ac-r2-kb3026739-x64.msp" We are loading R2 CU4. Daniel Ratliff From: [email protected] [mailto:[email protected]] On Behalf Of Phil Wilcock Sent: Wednesday, November 04, 2015 12:58 PM To: [email protected] Subject: RE: [MDT-OSD] Whats in your base image ? So does anyone put the SCCM client in the image? Been fiddling with that for our labsetup but can’t for the life of me get the client to behave when it pops up in the new machine.. I install using ccmsetup with no sitecode etc Stop ccmexec Delete smscfg.ini Delete the computer certs Do this - wmic /namespace:\\root\ccm\invagt path inventoryActionStatus where InventoryActionID=”{00000000-0000-0000-0000-000000000001}” DELETE /NOINTERACTIVE Then the machine gets sysprepped etc So the new machine gets deployed, and configmgr finds the site in AD, contacts the MP, but then stops dead in it’s tracks.. Certificate issues? Just wondering if anyone out there has a silver bullet solution for this up their sleeve ☺ Cheers Phil From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Wilson, J Kevin Sent: 03 November 2015 15:16 To: [email protected]<mailto:[email protected]> Subject: RE: [MDT-OSD] Whats in your base image ? …that’s when you begin looking at App Volumes / App Disks / layering technologies in general to “attach” disks full of apps to the system. Kevin Wilson Desktop and Hardware Architecture End User Technology Services From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Bain.John Sent: Tuesday, November 03, 2015 10:02 AM To: [email protected]<mailto:[email protected]> Subject: RE: [MDT-OSD] Whats in your base image ? *** Exercise caution. This is an EXTERNAL email. DO NOT open attachments or click links from unknown senders or unexpected email. *** I wish it were possible to pack office into its own wim … then you could layer wim overtop of wim through the deployment process John Bain – CIC Engineering Office: JETS C657 | Tel: 613-437-6829 From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Steve Whitcher Sent: November 3, 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. The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information.
