Yup, it kills the install. Found that out myself on the Windows 8.1 Update 1.
Just bump the update time for the update within the SCCM console to match what your environment needs unless the CBS log that Ivan pointed to is showing some other issue. Rick J. Jones Wireless from AT&T Domestic Desktop Application Management D: (425) 288-6240 C: (206) 419-1104 From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Lindenfeld, Ivan Sent: Wednesday, May 28, 2014 6:48 AM To: mssms@lists.myitforum.com Subject: [mssms] RE: Issue installing 2008 R2 SP1 via software updates Look at c:\windows\windowsupdate.log to see if it finished or what the status is. I recently performed the same deployment. Also, c:\windows\logs\cbs\cbs.log I didn't know about the cbs.log until a few weeks ago. Ivan From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com] On Behalf Of Corkill, Daniel Sent: Tuesday, May 27, 2014 6:36 PM To: mssms@lists.myitforum.com<mailto:mssms@lists.myitforum.com> Subject: [mssms] Issue installing 2008 R2 SP1 via software updates I scheduled the deployment of SP1 for Windows Server 2008 R2 to a server last night at 3am using ConfigMgr software updates. Looking at Software Center this morning the installation status is still "installing". I looked at wuahandler.log and can see it started the installation at 3am, but approx an hour later at 4:08am I'm seeing: Async searching completed. WUAHandler 28/05/2014 3:34:03 AM 1272 (0x04F8) Successfully completed scan. WUAHandler 28/05/2014 3:34:04 AM 4060 (0x0FDC) Successfully canceled running installation. WUAHandler 28/05/2014 4:08:09 AM 3736 (0x0E98) Async install completed. WUAHandler 28/05/2014 4:08:09 AM 2016 (0x07E0) When I checked the max run time for this update in ConfigMgr it's set at 60mins and the description states, "when a software update installation exceeds the max run time, ConfigMgr no longer monitors the installation...". I'm aware this setting is also used to calculate whether the update can run within any defined maintenance windows but I set the update to install regardless of maintenance windows so this shouldn't be the issue. When it says after 60 mins it stops monitoring, does that mean the SP installation has continued and completed and it's just not aware of it or has it terminated the installation? I can't see any activity in the processes list; not sure what will happen after I reboot it. Does anyone have any ideas what might have occurred? I'm also interested to know if there's a log generated by the SP install that I can review for hopefully more info. Daniel. ********************************************************************* This email, including any attachment, is confidential to the intended recipient. It may also be privileged and may be subject to copyright. If you have received this email in error, please notify the sender immediately and delete all copies of the email. Any confidentiality or privilege is not waived. Neither the Council nor the sender warrant that this email does not contain any viruses or other unsolicited items. This email is an informal Council communication. The Council only accepts responsibility for information sent under official letterhead and duly signed by, or on behalf of, the Chief Executive Officer. Privacy Collection Notice Logan City Council may collect your personal information, e.g. name, residential address, phone number etc, in order to conduct its business and/or meet its statutory obligations. The information will only be accessed by employees and/or Councillors of Logan City Council for Council business related activities only. If your personal information will be passed onto a third party, Council will advise you of this disclosure, the purpose of the disclosure and reason why. Your information will not be given to any other person or agency unless you have given us permission or we are required by law. ________________________________ NOTICE: The information contained in this message is proprietary and/or confidential and may be privileged. If you are not the intended recipient of this communication, you are hereby notified to: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately.
