What do you do with these "bad" patches? offline servicing for 2012? or are we talking 2007 here and using DISIM? or something else? :)
On Thu, Jul 17, 2014 at 7:05 AM, Miller, Todd <[email protected]> wrote: > Yes, you need to rescan for patches before running the second (or third) > Install Software Updates step. > > > > The method to rescan is just like in the article you reference… > > > > Run Command line with > > WMIC /namespace:\\root\ccm path sms_client CALL TriggerSchedule > "{00000000-0000-0000-0000-000000000113}" /NOINTERACTIVE > > > > You need to wait for a little while for the scan to complete too. > > > > > > Be careful to not deploy any patches that cause a double reboot during > your OSD deployments (including Build and Capture). For me these “bad” > updates are currently… > > > > (I imagine more than one person will chime in and tell you that you should > be using MDT Light Touch to do your build and capture, but you can just > ignore them. They’re wrong. J) > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Murray, Mike > *Sent:* Wednesday, July 16, 2014 12:53 PM > *To:* [email protected] > *Subject:* [mssms] Software updates not installing during build & capture > > > > Our build & capture task sequence is advertised to All Systems, yet many > software updates are not being installed, and we run the install software > updates task twice with a restart in between. When we deploy the captured > image, we’ll see 50+ updates installing. W why wouldn’t these updates be > applying? > > > > Is something like this needed? http://www.toolzz.com/?p=1059 > > > > > > Best Regards, > > > > Mike Murray > > Desktop Management Coordinator - IT Support Services > > California State University, Chico > > 530.898.4357 > [email protected] > > > > > > > ------------------------------ > Notice: This UI Health Care e-mail (including attachments) is covered by > the Electronic Communications Privacy Act, 18 U.S.C. 2510-2521, is > confidential and may be legally privileged. If you are not the intended > recipient, you are hereby notified that any retention, dissemination, > distribution, or copying of this communication is strictly prohibited. > Please reply to the sender that you have received the message in error, > then delete it. Thank you. > ------------------------------ > >
