It will only cleanup a few hundred MB on a 5GB wim file at best with Windows 10, don't think it's worth the time. Especially as it seems Microsoft rarely tests that feature.
/ Johan Johan Arwidmark Microsoft MVP - Cloud and Datacenter Management CTO - TrueSec E-mail: [email protected]<mailto:[email protected]> Twitter: @jarwidmark<http://twitter.com/jarwidmark> Web: https://truesec.com Blog: https://deploymentresearch.com Mobile: +1 630 881 8852 Address: Oxtorgsgrand 2, 111 57 Stockholm, Sweden From: [email protected] [mailto:[email protected]] On Behalf Of Chobeaux, Sebastien Sent: den 7 september 2017 09:41 To: [email protected] Subject: [MDT-OSD] RE: WindowsUpdateAgent breaking CleanupBeforeSysprep Interested in the answer as well :) thanks De : [email protected]<mailto:[email protected]> [mailto:[email protected]] De la part de Klish, Brian Envoyé : August 17, 2017 3:03 PM À : [email protected]<mailto:[email protected]> Objet : [MDT-OSD] RE: WindowsUpdateAgent breaking CleanupBeforeSysprep Johan, can you elaborate on that a bit? I really like the idea of cleaning up the image. Should we just be running this command on Windows 10? DISM.exe /online /Cleanup-Image /StartComponentCleanup /ResetBase Looking at the script it's using /RestoreHealth, but I have no idea why. -Brian From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Johan Arwidmark Sent: Thursday, July 20, 2017 6:04 PM To: [email protected]<mailto:[email protected]> Subject: [MDT-OSD] RE: WindowsUpdateAgent breaking CleanupBeforeSysprep Don't use the script for Windows 10. / Johan From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Miller, Todd Sent: den 20 juli 2017 11:22 To: [email protected]<mailto:[email protected]> Subject: [MDT-OSD] WindowsUpdateAgent breaking CleanupBeforeSysprep I am trying to solve a problem in my build and capture process in Windows 10. I am using the cleanup script from Mikael and Johan to reduce the image size before sysprep. I am using version 2.5 of the script which I think is the latest on Github. What I think I am seeing is that during the final DISM resetbase cleanup routine, Windows Update is kicking off while the DISM command is still running and that is breaking the cleanup process. At least I think that is what is happening based on the CBS.log The final DISM section process is going along fine in the CBS.log and then I see a line in the log right at the spot where it errors that says -- Session <<>> initialized by client WindowsUpdateAgent and then the CBS process errors out and the DISM cleanup command also errors. Looking at the CleanupBeforeSysprep, would it make sense in the Windows 10 section to either move restarting the wuaserv service to after the resetbase section -- 'Execute DISM.exe /online /Cleanup-Image /StartComponentCleanup /ResetBase ? or alternately, move the whole Cleaning Up the SoftwareDistribution folder to after the reset base section? I don't exactly know the reasoning behind starting the service back up before cleanup - so maybe that is a dumb idea. Is it ? ________________________________ Notice: This UI Health Care e-mail (including attachments) is covered by the Electronic Communications Privacy Act, 18 U.S.C. 2510-2521 and is intended only for the use of the individual or entity to which it is addressed, and may contain information that is privileged, confidential, and exempt from disclosure under applicable law. If you are not the intended recipient, any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the sender immediately and delete or destroy all copies of the original message and attachments thereto. Email sent to or from UI Health Care may be retained as required by law or regulation. Thank you. ________________________________ ________________________________ AVIS IMPORTANT: Les renseignements contenus ou joints à ce courriel sont pour l'usage exclusif du destinataire ou de l'institution à qui ce courriel s'adresse et peuvent contenir des renseignements privilégiés, confidentiels et exempts de divulgation conformément à la Loi sur l'accès à l'information municipale et la protection de la vie privée. Dans l'éventualité que le récepteur du présent courriel n'est pas le destinataire concerné ou la personne autorisée à acheminer le message au destinataire concerné, vous êtes, par la présente, avisé(e), que toute divulgation, diffusion, distribution ou reproduction de la présente communication est strictement interdite. Si vous recevez ce message par erreur, veuillez immédiatement en informer l'expéditeur ou l'expéditrice par courriel et détruire celui-ci ainsi que toutes les pièces jointes qu'il comporte. Merci de votre collaboration.
