none
Software Updates do not install during OS Deployment (timeout / Error 800705b4) RRS feed

  • Question

  • Hello,

    I am not able to get "Install Software Updates" TS working fine during OS deployment.

    I do use SCCM 2012 R2 and am trying to deploy Windows Server 2012 R2 OS.

    Basically it appears the task sequence failed during "Waiting for RefreshUpdates complete notification from Updates Deployment Agent" tep because of a 30 mn timeout (as shown below in smsts.log)

    I checked misc. logs (WUAHandler.log, UpdatesStore.log, UpdatesHandler.log, UpdatesDeployment.log) after the deployment. And everything looks fine from my perspective. Software update assessment is performed, expected missing updates are identified, and added to deployment list. All those operations are performed in less than 5 mn (vs. the 30 mn timeout)

    I saw I am not the only one to have this problem and tried a few suggestions but nothing works in my case:

    - Add SMSMP to install properties of SCCM client

    - Move Software Update tasks at the end after a restart

    Also I noticed that after the computer has been deployed, he is getting updates installed as required after some time. It only does not work during OSD

    smsts.log

    (...)
    [3677] Added/updated setting 'ccm_civersioninfo:modelname=site_51d7d30c-9a48-4567-a874-a8286f2ad18a/sum_ffe47cde-7e1a-40ff-b0bc-2f15d905b07c:version=201'. InstallSWUpdate 4/16/2014 4:28:56 PM 3136 (0x0C40)
    [3678] Added/updated setting 'ccm_civersioninfo:modelname=site_51d7d30c-9a48-4567-a874-a8286f2ad18a/sum_fff5c650-e48c-4eaa-95b5-ad761e082d85:version=200'. InstallSWUpdate 4/16/2014 4:28:56 PM 3136 (0x0C40)
    [3679] Added/updated setting 'ccm_civersioninfo:modelname=site_51d7d30c-9a48-4567-a874-a8286f2ad18a/sum_fffe5631-f35f-48ba-b72a-21f0b6fffa8c:version=200'. InstallSWUpdate 4/16/2014 4:28:56 PM 3136 (0x0C40)
    Unlocked ActualConfig successfully InstallSWUpdate 4/16/2014 4:28:56 PM 3136 (0x0C40)
    Unlocked policy transaction lock successfully InstallSWUpdate 4/16/2014 4:28:56 PM 3136 (0x0C40)
    Raising event:

    instance of CCM_PolicyAgent_SettingsEvaluationComplete
    {
     ClientID = "GUID:87C34D3F-6F61-49AF-8C94-437F2B1C810D";
     DateTime = "20140416142856.458000+000";
     PolicyNamespace = "\\\\.\\root\\ccm\\policy\\machine\\actualconfig";
     ProcessID = 3132;
     ThreadID = 3136;
    };
     InstallSWUpdate 4/16/2014 4:28:56 PM 3136 (0x0C40)
    Successfully submitted event to the Status Agent. InstallSWUpdate 4/16/2014 4:28:56 PM 3136 (0x0C40)
    End TS policy evaluation InstallSWUpdate 4/16/2014 4:28:56 PM 3136 (0x0C40)
    Policy evaluation initiated InstallSWUpdate 4/16/2014 4:28:56 PM 3136 (0x0C40)
    GetIPriviledgedInstallInterface successful InstallSWUpdate 4/16/2014 4:28:56 PM 3136 (0x0C40)
    Refreshing Updates InstallSWUpdate 4/16/2014 4:28:56 PM 3136 (0x0C40)
    Successfully initiated RefreshUpdates operation  InstallSWUpdate 4/16/2014 4:28:58 PM 3136 (0x0C40)
    Waiting for RefreshUpdates complete notification from Updates Deployment Agent InstallSWUpdate 4/16/2014 4:28:58 PM 3136 (0x0C40)
    FALSE, HRESULT=800705b4 (e:\nts_sccm_release\sms\client\osdeployment\installswupdate\installswupdate.cpp,1273) InstallSWUpdate 4/16/2014 4:58:59 PM 3136 (0x0C40)
    Timedout waiting for updates refresh complete notification InstallSWUpdate 4/16/2014 4:58:59 PM 3136 (0x0C40)
    WaitForRefreshUpdatesComplete(spInstall), HRESULT=800705b4 (e:\nts_sccm_release\sms\client\osdeployment\installswupdate\installswupdate.cpp,1331) InstallSWUpdate 4/16/2014 4:58:59 PM 3136 (0x0C40)
    RefreshUpdates(), HRESULT=800705b4 (e:\nts_sccm_release\sms\client\osdeployment\installswupdate\installswupdate.cpp,923) InstallSWUpdate 4/16/2014 4:58:59 PM 3136 (0x0C40)
    InstallUpdates(pInstallUpdate, tType, sJobID, sActiveRequestHandle), HRESULT=800705b4 (e:\nts_sccm_release\sms\client\osdeployment\installswupdate\main.cpp,248) InstallSWUpdate 4/16/2014 4:58:59 PM 3136 (0x0C40)
    Setting TSEnv variable SMSTSInstallUpdateJobGUID= InstallSWUpdate 4/16/2014 4:58:59 PM 3136 (0x0C40)
    Process(pInstallUpdate, tType), HRESULT=800705b4 (e:\nts_sccm_release\sms\client\osdeployment\installswupdate\main.cpp,302) InstallSWUpdate 4/16/2014 4:58:59 PM 3136 (0x0C40)
    Process completed with exit code 2147943860 TSManager 4/16/2014 4:58:59 PM 2224 (0x08B0)
    !--------------------------------------------------------------------------------------------! TSManager 4/16/2014 4:58:59 PM 2224 (0x08B0)
    Failed to run the action: Install Software Updates.
    This operation returned because the timeout period expired. (Error: 800705B4; Source: Windows) TSManager 4/16/2014 4:58:59 PM 2224 (0x08B0)
    (...)

    Wednesday, April 16, 2014 4:23 PM

Answers

  •  I checked that the OSD computers are in the patch management collection during OSD.

    Nope, that's not good enough. The update deployments must target the exact same collection that the task sequence deployment does for it to work.

    Jason | http://blog.configmgrftw.com

    Friday, April 18, 2014 2:01 AM
  • Do you have any updates available in the future? If so, these updates will cause the Update Evaluation timeout and return wrong code to TS manager.

    Juke Chou

    TechNet Community Support

    Thursday, April 17, 2014 4:06 PM
    Moderator

All replies

  • %windir%\WindowsUpdate.log might also contain additional information.

    Torsten Meringer | http://www.mssccmfaq.de

    Wednesday, April 16, 2014 4:28 PM
  • Can you describe exactly how you did this: "Add SMSMP to install properties of SCCM client"

    Also, what kind of boundaries are you using?


    Jason | http://blog.configmgrftw.com

    Wednesday, April 16, 2014 8:48 PM
  • are the Updates deployed to *exactly* the same collection for which the OSD TS is deployed?

    e.g. Unknown Computers? All Systems? Servers-which-need-rebuild?

    Or, if using Unknown Computers, have you added the x64 or x86 Unknown Computer object into the relevant updates deployment collection?

    At a high level, software updating works like this:

    - what do I need (scan/detect)
    - am I allowed to have that (is there a deployment for me)
    - where do I get that from (content location)
    - install it now? (maintenance window?)
    - did it install? (error result)


    Don
    (Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
    This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)


    • Edited by DonPick Wednesday, April 16, 2014 9:47 PM
    Wednesday, April 16, 2014 9:43 PM
  • Hello All,

    Thanks all for your suggestions.

    • WindowsUpdate.log: One strange thing in this log. It appears the update assessment is done against Microsoft updates, not my internal WSUS server (despite a GPO  Policy which enforces that for all computers in the domain)
    • SMSMP: In the TS "Setup Windows and ConfigMgr", I added "SMSMP=<FQDN>" to the field "Installation Properties"
    • How do I target software update deployment: I don't use unknown computers. Computers are identified for OSD by the MAC address. They are added to a special OSD collection. This collection is added to my standard collection for patch management. The same I use for monthly deployment of all servers. I checked that the OSD computers are in the patch management collection during OSD.
    Thursday, April 17, 2014 3:56 AM
  • Do you have any updates available in the future? If so, these updates will cause the Update Evaluation timeout and return wrong code to TS manager.

    Juke Chou

    TechNet Community Support

    Thursday, April 17, 2014 4:06 PM
    Moderator
  •  I checked that the OSD computers are in the patch management collection during OSD.

    Nope, that's not good enough. The update deployments must target the exact same collection that the task sequence deployment does for it to work.

    Jason | http://blog.configmgrftw.com

    Friday, April 18, 2014 2:01 AM
  • Good morning Jason,

    With all the Software Update Task Sequence fixes in 1902 listed here, and with 1906 and 1910 out, is there still a requirement for update deployments to target the exact same collection that the task sequence deployment for updates to work during OSD?

    Thanks,

    -nils

    Tuesday, December 3, 2019 4:56 PM
  • Yes. This behavior isn't a bug or due to a bug. It's by design.

    Jason | https://home.configmgrftw.com | @jasonsandys

    • Proposed as answer by nf_ Tuesday, December 3, 2019 6:06 PM
    Tuesday, December 3, 2019 5:22 PM
  • Thank you.
    Tuesday, December 3, 2019 6:06 PM