Is there a way to monitor this once you start it? From: [email protected] [mailto:[email protected]] On Behalf Of Marcum, John Sent: Monday, November 25, 2013 12:49 PM To: '[email protected]' Subject: [MDT-OSD] RE: TS failing after Updates
I haven't seen how to "schedule" them. It looks like a one-time thing to me. ________________________________ John Marcum Sr. Desktop Architect Bradley Arant Boult Cummings LLP ________________________________ From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Miller, Todd Sent: Monday, November 25, 2013 12:21 PM To: [email protected]<mailto:[email protected]> Subject: [MDT-OSD] RE: TS failing after Updates I haven't had trouble with offline servicing myself, but you could absolutely reduce the risk by only injecting the updates that cause this double reboot problem. Myself, I don't schedule offline updates. I just have injected a few updates that I have found that either need to be on the computer for the SCCM client to work properly - in the 2007 days -- or in the case of that new October update that hoses the task sequence. Some people would go all in on the off-line updates, but I am happy with the old way of applying updates during the build/capture task sequence and only injecting when really necessary. I appreciate your mistrust of the process. It has never sounded like a good idea to inject patches into the "pristine" WIM to me either, but sometimes you gotta do what you gotta do. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Linkey, Mike Sent: Monday, November 25, 2013 10:50 AM To: [email protected]<mailto:[email protected]> Subject: [MDT-OSD] RE: TS failing after Updates Thought I tried that once and it hosed up my wim file. I will look at it again though. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Miller, Todd Sent: Monday, November 25, 2013 10:39 AM To: [email protected]<mailto:[email protected]> Subject: [MDT-OSD] RE: TS failing after Updates Investigate offline patching. Once the patches are "baked in" to your image, then there is no trouble deploying a WIM that already has these patches. You might also consider maintaining a separate update list for the deployment process apart from already deployed machines. The process to inject offline patches is the easier way out though. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Linkey, Mike Sent: Monday, November 25, 2013 10:14 AM To: [email protected]<mailto:[email protected]> Subject: [MDT-OSD] RE: TS failing after Updates Well that stinks. How are you supposed to add them then? From reading, you have to install them like a package? From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Nash Pherson Sent: Monday, November 25, 2013 9:08 AM To: [email protected]<mailto:[email protected]> Subject: [MDT-OSD] RE: TS failing after Updates The resource which is running the task sequence can't have any Deployments of Software Update Groups that contain the Updates listed in this article: http://support.microsoft.com/kb/2894518 They cause 2 reboots and the task sequence can't follow the system through the second reboot. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Linkey, Mike Sent: Monday, November 25, 2013 8:48 AM To: [email protected]<mailto:[email protected]> Subject: [MDT-OSD] TS failing after Updates Not sure why this has started to happen, but when we put on a Windows 7 image via our TS now, it is failing when it trys to install the Windows updates. I disabled the step and it seems to work ok after that. So I am confused why all of the sudden this would start to happen. We have a Windows 8 TS and it works fine. Attached is the smsts.log file that has the issue in it. It almost seems as if that step is corrupting WMI somehow, but really don't have a clue why. Was hoping someone has seen something like this before. Mike L. ________________________________ 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. ________________________________ ________________________________ 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. ________________________________ ________________________________ Confidentiality Notice: This e-mail is from a law firm and may be protected by the attorney-client or work product privileges. If you have received this message in error, please notify the sender by replying to this e-mail and then delete it from your computer. ________________________________ Confidentiality Notice: This e-mail is from a law firm and may be protected by the attorney-client or work product privileges. If you have received this message in error, please notify the sender by replying to this e-mail and then delete it from your computer.
