Hello, I had the updates working during the task sequence "Capture and Build". Since this week it does not work any more. No problem wile deploying those updates on the machine which is joined to the domain. Software install works as expected. Any idea's ? The task sequence execution engine failed executing the action (Install Updates) in the group (Build the Reference Machine) with the error code 2147943860 Action output: 8F1EC}"' compiled in 'root\ccm\policy\machine' namespace Policy verification done GetIPriviledgedInstallInterface successful Refreshing Updates Successfully initiated RefreshUpdates operation Waiting for RefreshUpdates complete notification from Updates Deployment Agent FALSE, HRESULT=800705b4 (e:\nts_sms_fre\sms\client\osdeployment\installswupdate\installswupdate.cpp,1351) WaitForRefreshUpdatesComplete(spInstall), HRESULT=800705b4 (e:\nts_sms_fre\sms\client\osdeployment\installswupdate\installswupdate.cpp,1410) RefreshUpdates(), HRESULT=800705b4 (e:\nts_sms_fre\sms\client\osdeployment\installswupdate\installswupdate.cpp,998) InstallUpdates(pInstallUpdate, tType, sJobID, ulCookie), HRESULT=800705b4 (e:\nts_sms_fre\sms\client\osdeployment\installswupdate\main.cpp,279) Setting TSEnv variable SMSTSInstallUpdateJobGUID= Process(pInstallUpdate, tType), HRESULT=800705b4 (e:\nts_sms_fre\sms\client\osdeployment\installswupdate\main.cpp,349) Timedout waiting for updates refresh complete notification. The operating system reported error 2147943860: This operation returned because the timeout period expired.

check with your network people maybe they change a proxy setting or similar, is your SLP correctly configured like so ? Build and Capture Windows 7 sample task sequence adding windows updates by specifying the SLP My step by step SCCM Guides I'm on Twitter > ncbrady

800705b4 = This operation returned because the timeout period expired. Any chance that you are running into this issue: http://support.microsoft.com/kb/2009754/en-usTorsten Meringer | http://www.mssccmfaq.de

I do not use any proxy. SLP is there, properties are: SMSSLP=TST-SCMSV00.xxx.xx SMSMP=TST-SCMSV00.xxx.xx I can also see in the ccmsetup.log that those properties are used. Software install works normally.....

this must be something else since there are no updates installed at all.

What kind of boundaries are you using? What OS are you building with the TS?Jason | http://myitforum.com/cs2/blogs/jsandys | Twitter @JasonSandys

I have an IP Subnet defined and Active Directory. My OS is Windows 7. But first of all it WAS working perfectly... Anyhow, when I look at LocationServices.log it says the following: <![LOG[Won't send a client assignment fallback status point message because the last assignment error matches this one.]LOG]!><time="15:35:48.267+-120" date="03-28-2011" component="LocationServices" context="" type="1" thread="1280" file="fspclientdeployassign.cpp:201"> <![LOG[Failed to refresh site code. Error: 0x80004005]LOG]!><time="15:35:48.267+-120" date="03-28-2011" component="LocationServices" context="" type="3" thread="1280" file="lsnetworkchangetask.cpp:106"> And I have no clientlocation.log ....

Please make sure that you have enable all ports for SCCM on your firewalls. Please refer: Ports Used by Configuration Manager http://technet.microsoft.com/en-us/library/bb632618.aspx You may specially pay attention on: 3. Site Server < -- > Software Update Point 4. Software Update Point -- > Internet 5. Site Server < -- > State Migration Point 6. Client -- > Software Update Point 7. Client -- > State Migration PointPlease remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

I have resolved the problem. I have tried to deploy R3 hotfix using ClientPatch folder. Afterwards I have chosen another method because the patch was not applied. TheClientPatch folder was still distributed on the DP. As you can read below it can happen that the msi properties are not applied in this case. So SMSSLP SMSMP were not set. In the msi ccm and client setup logfile however everything was ok. I did not expect that having this folder on DP can have that impact. Later on I have found this, after my problem was already resolved. http://blogs.technet.com/b/configmgrteam/archive/2009/04/08/automatically-applying-hotfixes-to-the-configuration-manager-2007-client-during-installation.aspx