Howdy Jason,

Usually I would. It runs the CheckSUR process to repair windows servicing (CBS) 
or log issues for manual remediation. You can run it as many times as you like 
without it installing as a traditional hotfix.

-Stephen

> On Dec 5, 2014, at 9:33 PM, Jason Sandys <[email protected]> wrote:
> 
> Have you tried injecting into into your image using DISM?
> 
> 
> J
> From: [email protected] <[email protected]> on 
> behalf of Stephen Leuthold <[email protected]>
> Sent: Friday, December 5, 2014 12:37 PM
> To: [email protected]
> Subject: Re: [mssms] Problems running KB947821 (System Update Readiness Tool) 
> during OSD
>  
> Anyone successfully running this KB via OSD task sequence ?
> 
> -Stephen
> 
> On Dec 4, 2014, at 9:47 AM, Stephen Leuthold <[email protected]> 
> wrote:
> 
>> Unfortunately we are still supporting Windows Server 2008 non-R2 
>> 64-bit/32-bit on rare occasions. There seems to be an issue where 
>> post-deployment of this OS where we cannot see what updates are installed 
>> (PowerShell Get-Hotfix or query Win32_QuickFixEngineering) because there are 
>> issues with windows servicing (CBS). To remediate the issue we run KB947821 
>> v35, copy some missing files to %windir%\Temp\CheckSUR\servicing\Packages 
>> and then run KB947821 again. Works like a champ outside of a task sequence! 
>> I take these steps out of the TS and OSD completes all the way through with 
>> no issues.
>> 
>> What is happening in my case during OSD (SC2012R2 CM CU1) is it will run 
>> KB947821 successfully (exit code 0 in execmgr) then the task sequence engine 
>> just goes away and I see the CTRL+ALT+DEL screen. Unfortunately I was not 
>> able to successfully increase the smsts.log size to see what's going on 
>> despite following method 2 here: 
>> http://www.windows-noob.com/forums/index.php?/topic/11071-how-can-i-increase-the-smstslog-file-size-for-pxe-based-os-deployments-using-system-center-2012-r2-configuration-manager/
>>  and updating my client install properties in the task sequence to 
>> CCMLOGMAXSIZE=2621440 CCMLOGMAXHISTORY=3.
>> 
>> So my questions are:
>> 1) What might I be doing wrong that is preventing the logmaxhistory and size 
>> to increase?
>> 2) Anyone else successfully running KB947821 during OSD with success?
>> 
>> Gracias!
>> 
>> -Stephen
> 
> 



Reply via email to