That’s what I figured, thanks for your help. From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Tyler S. Humbard (DOTComm) Sent: Tuesday, April 25, 2017 8:15 AM To: mssms@lists.myitforum.com Subject: Re: [mssms] Windows 10 Sysprep Question
I'm pretty sure you need to run the script during the OSD, if you're going to do it that way. The other option is to prevent the build and capture process from internet access. I personally run it during OSD. This<https://virtualfeller.com/2017/04/19/optimize-vdi-windows-10-default-apps-original-anniversary-and-creator-updates/> is for VDI, but still lists the good apps to remove. Tyler Humbard | Server Systems Administrator II CONFIDENTIALITY NOTICE: This e-mail message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. On Tue, Apr 25, 2017 at 7:04 AM, Morris, Spencer <smor...@wrallp.com<mailto:smor...@wrallp.com>> wrote: Hi, I was wondering when everyone was removing appx provisioned packages from their images? I was running the script to remove them before capturing the image, but running into issues with sysprep failing. Would it be better to just run the script as part of the imaging task sequence and not during the build and capture? Thanks for your help. [2016 Design Firm of the Year] [WRA 100 Years] The information supplied in this message may be privileged, confidential and/or exempt from disclosure under applicable law. If you are not the intended recipient of this message, the sender does not intend delivery to you to waive any privilege or right pertaining to this message. You have no right to retain, disseminate, copy or disclose the material contained herein. If you have received this message in error, please immediately notify the sender by return e-mail, and delete the errant message. Thank you. WRA_Disclaimer_v20070222a
