Install updates in Task Sequence (Full Version)

All Forums >> [Management Products] >> System Center Products >> System Center Configuration Manager



Message

johneijg -> Install updates in Task Sequence (9/12/2008 9:36:49 AM)

We just started our lab testing with SCCM SP1 and the Image creation process.

We created a task sequence similar configured as in our MDT Task sequence in
the production network.
The entire task sequence runs like a charm, all apps get installed, the
customization and such runs great.

The only part which we can't get working is the Install Software updates
(Install All updates).
We created an update list and package and deployed it to the new deployment
collection.

We've already repeated the installation of SCCM SP1 SUP and the WSUS 3.0 SP1
all with no joy.

When the task sequence runs everything installs fine but the Install updates
returns an error 0x8004005:

SMSTS.log

<![LOG[ Update with CIID
Site_6F772B19-83E9-4BFB-BA39-DA9EF437DC19/SUM_6f5dc828-0f05-4577-9a8a-74ab1cbe00a9
failed with hr = 0x80040669]LOG]!><time="16:58:54.681+-120" date="09-11-2008"
component="InstallSWUpdates" context="" type="0" thread="3476"
file="installswupdate.cpp:393">

<![LOG[ Update with CIID
Site_6F772B19-83E9-4BFB-BA39-DA9EF437DC19/SUM_26da5716-5999-4ab2-8806-800f7af93c93
failed with hr = 0x80040669]LOG]!><time="16:58:54.782+-120" date="09-11-2008"
component="InstallSWUpdates" context="" type="0" thread="3476"
file="installswupdate.cpp:393">

<![LOG[ Update with CIID
Site_6F772B19-83E9-4BFB-BA39-DA9EF437DC19/SUM_2be6143c-5547-4fee-afc6-37cd3d2d585d
failed with hr = 0x80040669]LOG]!><time="16:58:54.862+-120" date="09-11-2008"
component="InstallSWUpdates" context="" type="0" thread="3476"
file="installswupdate.cpp:393">

<![LOG[ Update with CIID
Site_6F772B19-83E9-4BFB-BA39-DA9EF437DC19/SUM_278bb66c-ce54-40fb-a5a2-ae55804c3917
failed with hr = 0x80040669]LOG]!><time="16:58:54.942+-120" date="09-11-2008"
component="InstallSWUpdates" context="" type="0" thread="3476"
file="installswupdate.cpp:393">

<![LOG[Received job completion notification from Updates Deployment Agent
]LOG]!><time="16:58:57.696+-120" date="09-11-2008"
component="InstallSWUpdate" context="" type="1" thread="1496"
file="installswupdate.cpp:1156">

<![LOG[One or more updates failed to install,
hr=0x80004005]LOG]!><time="16:58:57.696+-120" date="09-11-2008"
component="InstallSWUpdate" context="" type="3" thread="1496"
file="main.cpp:235">

<![LOG[InstallUpdates(pInstallUpdate, tType, sJobID, ulCookie),
HRESULT=80004005
(e:\nts_sms_fre\sms\client\osdeployment\installswupdate\main.cpp,279)]LOG]!><time="16:58:57.696+-120"
date="09-11-2008" component="InstallSWUpdate" context="" type="0"
thread="1496" file="main.cpp:279">

<![LOG[Setting TSEnv variable
SMSTSInstallUpdateJobGUID=]LOG]!><time="16:58:57.696+-120" date="09-11-2008"
component="InstallSWUpdate" context="" type="1" thread="1496"
file="main.cpp:113">

<![LOG[Process(pInstallUpdate, tType), HRESULT=80004005
(e:\nts_sms_fre\sms\client\osdeployment\installswupdate\main.cpp,349)]LOG]!><time="16:58:57.696+-120"
date="09-11-2008" component="InstallSWUpdate" context="" type="0"
thread="1496" file="main.cpp:349">

<![LOG[Process completed with exit code
2147500037]LOG]!><time="16:58:57.706+-120" date="09-11-2008"
component="TSManager" context="" type="1" thread="1760"
file="commandline.cpp:1102">

UpdateHandler.log:

]LOG]!><time="16:58:50.626+-120" date="09-11-2008"
component="UpdatesHandler" context="" type="1" thread="2028"
file="event.cpp:525">

<![LOG[State Transition - Update 5f70c49b-f85a-446b-b9af-442463feb026, State
= COMPLETE_FAILED]LOG]!><time="16:58:50.636+-120" date="09-11-2008"
component="UpdatesHandler" context="" type="1" thread="2028"
file="atomicupdate.cpp:874">

<![LOG[CBundledUpdate -- Failed to download update
(5f70c49b-f85a-446b-b9af-442463feb026). Error =
0x80040669]LOG]!><time="16:58:50.636+-120" date="09-11-2008"
component="UpdatesHandler" context="" type="3" thread="2028"
file="bundledupdate.cpp:846">

<![LOG[Raising event:

[SMS_CodePage(850), SMS_LocaleID(1043)]

instance of SMS_SUMAgentUpdateError_NoContent

{

ClientID = "GUID:29A7B545-A4A1-4B28-852B-B15BBCFAE6B3";

DateTime = "20080911145850.646000+000";

MachineName = "MAC000802ABF21B";

ModelName =
"Site_6F772B19-83E9-4BFB-BA39-DA9EF437DC19/SUM_26da5716-5999-4ab2-8806-800f7af93c93";

ProcessID = 1400;

SdmPackageVersion = "4";

SiteCode = "MAB";

ThreadID = 2028;

UpdateId = "26da5716-5999-4ab2-8806-800f7af93c93";

};

]LOG]!><time="16:58:50.646+-120" date="09-11-2008"
component="UpdatesHandler" context="" type="1" thread="2028"
file="event.cpp:525">

<![LOG[Bundle update (26da5716-5999-4ab2-8806-800f7af93c93) internal state
transition: WAIT_CONTENTS to COMPLETE_FAILED]LOG]!><time="16:58:50.656+-120"
date="09-11-2008" component="UpdatesHandler" context="" type="1"
thread="2028" file="bundledupdate.cpp:165">

<![LOG[CDeploymentJob -- Failed to download update
(26da5716-5999-4ab2-8806-800f7af93c93). Error =
0x80040669]LOG]!><time="16:58:50.666+-120" date="09-11-2008"
component="UpdatesHandler" context="" type="3" thread="2028"
file="job.cpp:2328">

<![LOG[Bundle update (278bb66c-ce54-40fb-a5a2-ae55804c3917) internal state
transition: DOWNLOAD_READY to WAIT_CONTENTS]LOG]!><time="16:58:50.666+-120"
date="09-11-2008" component="UpdatesHandler" context="" type="1"
thread="2028" file="bundledupdate.cpp:165">

<![LOG[Bundle update (278bb66c-ce54-40fb-a5a2-ae55804c3917) is requesting
download from child updates for action
(INSTALL)]LOG]!><time="16:58:50.666+-120" date="09-11-2008"
component="UpdatesHandler" context="" type="1" thread="2028"
file="bundledupdate.cpp:830">

<![LOG[State Transition - Update 744cacc6-be9b-4fbe-9c6b-49286ef87d53, State
= WAIT_CONTENTS]LOG]!><time="16:58:50.676+-120" date="09-11-2008"
component="UpdatesHandler" context="" type="1" thread="2028"
file="atomicupdate.cpp:874">

<![LOG[Starting download on action (INSTALL) for Update
(744cacc6-be9b-4fbe-9c6b-49286ef87d53)]LOG]!><time="16:58:50.676+-120"
date="09-11-2008" component="UpdatesHandler" context="" type="1"
thread="2028" file="update.cpp:385">

<![LOG[Content Text = <Content
ContentId="744cacc6-be9b-4fbe-9c6b-49286ef87d53" Version="1"><FileContent
Name="WindowsXP-KB950762-x86-ENU.exe"
Hash="BFA04C9D2E62B4695D1BB8953486788C8A8C11E4" HashAlgorithm="SHA1"
Size="559144"/></Content>

]LOG]!><time="16:58:50.676+-120" date="09-11-2008"
component="UpdatesHandler" context="" type="1" thread="2028"
file="updatepolicy.cpp:349">

<![LOG[First need to check contents
availability]LOG]!><time="16:58:50.676+-120" date="09-11-2008"
component="UpdatesHandler" context="" type="1" thread="2028"
file="update.cpp:405">

<![LOG[Unable to get locations, no need to continue with
download]LOG]!><time="16:58:50.776+-120" date="09-11-2008"
component="UpdatesHandler" context="" type="3" th......



direland -> RE: Install updates in Task Sequence (9/12/2008 12:20:49 PM)

Is this for an XP image and if so, is XP SP3 or Office 2003 SP3 in your update package?



johneijg -> RE: Install updates in Task Sequence (9/12/2008 1:04:50 PM)

It indeed is an XP SP3 image, we tried it both with and without Office 2003 SP3, both gave the same result.



direland -> RE: Install updates in Task Sequence (9/12/2008 1:10:30 PM)

Is SP3 part of your .WIM or are you trying to deploy it via the Software Update task?  Can you post your WindowsUpdate.log from %windir%?



johneijg -> RE: Install updates in Task Sequence (9/12/2008 1:29:43 PM)

We are trying to build a new gold image, we have XP with SP3 slipstreamed as OS Installation package.
The MDT task sequense is set to use that package, all goes well (xp installs, apps such as .net and ie7 install) till it reaches the Install Software Update point.

When we leave the updates for what they are and continue to use the windows xp build which was just deployed we can see the WUAhandler.log saying that updates are available, however they will never be deployed to the sccm client.

I'll try to get my handson the windowsupdate.log during the weekend.

Perhaps good to mention the server run Windows 2008 x64 with Wsus 3.0 SP1 and SCCM 2007 SP1 within VMWare ESX 3.51.



direland -> RE: Install updates in Task Sequence (9/12/2008 1:44:11 PM)

I had a similar issue that I worked with Microsoft on.  They provided a work around until they figure out what the problem is but it sounds like it's in the hands of the SUS team.

Check your WindowsUpdate.log and see what version the Windows Update agent is.  Mine was 7.1.  Microsoft's work around was to install Windows Update Agent 7.2 prior to the Software Update task.  Then run Software Update task twice (set the first one to continue on error).

Here's the links to the 7.2 agent if you want to try it...

x86
http://download.windowsupdate.com/windowsupdate/redist/standalone/7.2.6001.784/windowsupdateagent30-x86.exe

x64
http://download.windowsupdate.com/windowsupdate/redist/standalone/7.2.6001.784/windowsupdateagent30-x64.exe

and the command line to run...
windowsupdateagent30-x86.exe /wuforce /quiet /norestart

If you decide to try it, please let me know your results.  I'll send the MS rep a link to this post as they are still collecting info on the issue I experienced.

Thanks,

Dan



johneijg -> RE: Install updates in Task Sequence (9/12/2008 5:15:02 PM)

Dan,

Thanks for the advise, I installed the newer Windows Update agent and checked that it installed properly by reviewing the Windowsupdate.log. Unfortunately the error remains.
The Software Update task initiates and attempts to download the updates but then fails.




direland -> RE: Install updates in Task Sequence (9/13/2008 12:21:45 PM)

You do have two Software Update tasks with the first one set to continue on error, correct?  This was key in the workaround that Microsoft gave me.



johneijg -> RE: Install updates in Task Sequence (9/15/2008 5:57:02 AM)

New update on my problem:
The installation of the new Autoupdate 7.2 agent didn't resolve the issue, two SU runs, one set to run on error would still fail.
I then found a different post which advised to recreate the Software distribution point which I did.

The situation has become a little better now, the initial Software Update job runs like charm. However as soon as we add Office 2003 all software updates start to fail again. I confirmed the agent is still 7.2.

The error code received is: HRESULT: 0x80070005




direland -> RE: Install updates in Task Sequence (9/15/2008 6:36:34 AM)

Are you still running the two SU tasks after adding Office 2003?



johneijg -> RE: Install updates in Task Sequence (9/15/2008 6:59:20 AM)

yup running the two SU tasks



direland -> RE: Install updates in Task Sequence (9/15/2008 7:27:17 AM)

What are the DCOM permissions set to on your WSUS server?  I'm seeing some posts saying they corrected that error code you gave by setting Everyone to full on Remote Launch.



johneijg -> RE: Install updates in Task Sequence (9/15/2008 10:50:15 AM)

At  the end the solution seemed to be more simple then expected.

To sum it up:
To resolve the download failure I had to recreate the distribution point.

To resolve the Software update failure after the Office 2003 install it turned out to be the Task sequence installation order.

Some of the Windows Update Agent components were overwritten by the Office 2003 setup, therefor the updates would eventually execute when the client was deployed and the SCCM Client detected the older components but it refused to install the updates during the task sequence.
By deploying the Windows Update Client after the Office 2003 installation the updates do get processed properly and my core image is finally ready.

Many thanks to all for your advise.



direland -> RE: Install updates in Task Sequence (9/15/2008 2:48:13 PM)

Just out of curiosity, are you still having to run the SU task twice or was just putting the Windows Update Agent install task after Office 2003 all that was required?

On my issue, Microsoft said it was due to the scan limit being exceeded (in roundtrips).  He emailed me earlier today explaining that they have a permanent fix and he would be sending to me shortly.



johneijg -> RE: Install updates in Task Sequence (9/16/2008 1:39:13 PM)

We still need to run 2 scans. I am curious what they will come up with as a fix so please keep me posted.



pen_69 -> RE: Install updates in Task Sequence (12/27/2008 10:54:06 AM)

quote:

ORIGINAL: direland

Just out of curiosity, are you still having to run the SU task twice or was just putting the Windows Update Agent install task after Office 2003 all that was required?

On my issue, Microsoft said it was due to the scan limit being exceeded (in roundtrips).  He emailed me earlier today explaining that they have a permanent fix and he would be sending to me shortly.


hi direland,
i am also struggling with the various problems with Software Update steps..
have you received further info, or this permanent fix? has it a kb number so i can get it from microsoft?

thanks in advance..



direland -> RE: Install updates in Task Sequence (1/6/2009 7:13:30 AM)

quote:

ORIGINAL: pen_69

hi direland,
i am also struggling with the various problems with Software Update steps..
have you received further info, or this permanent fix? has it a kb number so i can get it from microsoft?

thanks in advance..



I don't think there is a kb yet for this, but the engineer who helped me on this issue emailed the solution we used.  It was all due to round trips and the instructions below should take care of it for you...

The current number of roundtrips allowed by WSUS is 200 per client session. 
The default maximum size of XML data that WSUS allows during each roundtrip is currently 200 KB.
To reduce the number of roundtrips to be within the 200 roundtrip limit per client session, you can adjust the adjust the maximum size of XML data downloads per trip from the 200 KB limit to an unlimited size.

To adjust the maximum size of XML allowed per request, you will need to adjust a setting within the WSUS SUSDB database.
You can adjust this setting by running the following SQL script on the WSUS server:

==========
USE SUSDB
GO
UPDATE tbConfigurationC SET MaxXMLPerRequest = 0
==========

NOTE:  You will need to run this on the WSUS/SUP.  You should check to see if the SUSDB is hosted by the default Windows Internal Database (WIDS) or by full SQL.  You can check the following registry keys on the SUP to determine what is hosting SUSDB:
HKLM\SOFTWARE\Microsoft\Update Services\Server\Setup\SqlServerName


SUSDB hosted by WIDS:
HKLM\SOFTWARE\Microsoft\Update Services\Server\Setup\SqlServerName is equal to %computername%\MICROSOFT##SSEE
This denotes Windows Internal Database is installed and hosting SUSDB

If you are using Windows Internal Database for SUSDB, you can easily run the script by installing Microsoft SQL Server Management Studio Express from:  <http://www.microsoft.com/downloads/details.aspx?FamilyID=c243a5ae-4bd1-4e3d-94b8-5a0f62bf7796&DisplayLang=en>

After installing Microsoft SQL Server Management Studio Express, you will need to use the following connection string to connect to the SUSDB using:
\\.\pipe\MSSQL$MICROSOFT##SSEE\sql\query <file:///\\.\pipe\MSSQL$MICROSOFT%23%23SSEE\sql\query>

After connecting to the SUSDB, simply open a new query and past the following:
USE SUSDB
GO
UPDATE tbConfigurationC SET MaxXMLPerRequest = 0


SUSDB is hosted by Microsoft SQL Server 2005:
HKLM\SOFTWARE\Microsoft\Update Services\Server\Setup\SqlServerName is equal to %computername%
This denotes Microsoft SQL Server 2005 is installed locally and hosting SUSDB

When using Microsoft SQL Server 2005, you can open Microsoft SQL Server Management Studio and connect to the SUSDB via TCP/IP using the following syntax:  servername\sql_instance

After connecting to the SUSDB, simply open a new query and past the following:
USE SUSDB
GO
UPDATE tbConfigurationC SET MaxXMLPerRequest = 0




Page: [1]

Valid CSS!




Forum Software © ASPPlayground.NET Advanced Edition 2.4.5 ANSI
0.2070313