Install Software Updates Task Error - InstallTargetedUpdates failed, error 80040708
We are deploying Windows 7 with a task sequence. The task sequence includes the Install Software Updates task. After reviewing a test deployment, it appears the machine is seeing which patches are missing. Unfortunately the patches never apply during the deployment. I use a script similar to the one linked here to force an updates scan: http://www.petervanderwoude.nl/post/Installing-Software-Updates-via-a-Task-Sequence-in-ConfigMgr-2007.aspx The error I keep seeing is in the UpdatesDeployment.log file: http://i55.tinypic.com/15qwysm.jpg
October 22nd, 2010 5:35pm

Can you provide more information about your environment? Mixed or Native mode? Windows 7 Ultimate or Enterprise? Domain or Workgroup? What switches are you installing the SCCM client with in the deployment task sequence? (If Any) Are you getting any errors in you LocationServices.log? (If your machine is not a member of the domain when it does a scan it will not find the SLP from AD and the errors will appear here) Are the patches you have deployed still valid? Is the deployment dates still OK?Brett Moffett
Free Windows Admin Tool Kit Click here and download it now
October 25th, 2010 9:24am

Hi, For this error: InstallTargetUpdates failed, error 80040708 It seemed it isn't seeing the updates. Make sure you have advertised updates to the collection. Also, deploying the updates to the unknown computers is an option.Please 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.
October 25th, 2010 10:15am

Can you provide more information about your environment? Mixed or Native mode? Windows 7 Ultimate or Enterprise? Domain or Workgroup? What switches are you installing the SCCM client with in the deployment task sequence? (If Any) Are you getting any errors in you LocationServices.log? (If your machine is not a member of the domain when it does a scan it will not find the SLP from AD and the errors will appear here) Are the patches you have deployed still valid? Is the deployment dates still OK? Brett Moffett Mixed Mode Windows 7 Enterprise Domain SMSCACHESIZE=5120 FSP=server1.domain.com SMSSLP=server1.domain.com SMSMP=server2.domain.com CCMLOGLEVEL=0 CCMLOGMAXHISTORY=2 LocationServices.log is clean. The client receives the correct site code and MP I don't control the patching but it appears the deployment package is targeting a custom Windows 7 machine collection. I will see if we can create a deployment package to target Unknown Computers.
Free Windows Admin Tool Kit Click here and download it now
October 25th, 2010 6:41pm

If you are not seeing any errors in the LocationServices.log file then the client can talk to the MP and SUP fine. The next thing to look at is the targeting of the updates. Make sure the machines that are being built are a member of the collection. If you have a Windows 7 custom collection it might have the old client account in that and when you rebuild the machine that record becomes obsolete and a new record is created. Only issue is the collection refreshes on a schedule and when the machine is rebuilding it has not become a member of that collection yet. I usually advertise my updates to the collection I am using to deploy the OS to along with the production collection of my machines. This could also be done to all Unknown computers however I'm not sure that once a computer has a client it will be classified as an Unknown Computer.Brett Moffett
October 26th, 2010 12:39am

If you are not seeing any errors in the LocationServices.log file then the client can talk to the MP and SUP fine. The next thing to look at is the targeting of the updates. Make sure the machines that are being built are a member of the collection. If you have a Windows 7 custom collection it might have the old client account in that and when you rebuild the machine that record becomes obsolete and a new record is created. Only issue is the collection refreshes on a schedule and when the machine is rebuilding it has not become a member of that collection yet. I usually advertise my updates to the collection I am using to deploy the OS to along with the production collection of my machines. This could also be done to all Unknown computers however I'm not sure that once a computer has a client it will be classified as an Unknown Computer. Brett Moffett After advertising the updates to Unknown Computers the updates are now being installed. Thank you guys for the help
Free Windows Admin Tool Kit Click here and download it now
October 26th, 2010 12:58am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics