XP SP3 Deployement Question

Hi,

My users don't have administrator rights and don't get a notification
balloon from WU.
i've noticed the SP3 doesn't appear wtih 'install and shutdown' or get
scheduled for install like other updates.Only when i log in with
administrator credentials the notification balloon appears.

Is there other way to deploy ad get sure sp3 get installed via WSUS?

any help appreciated,

Stefan

"sver" <> wrote in message
news:F0AA21B1-63EA-4DF7-A35A-...
> Hi,
>
> My users don't have administrator rights and don't get a notification
> balloon from WU.
> i've noticed the SP3 doesn't appear wtih 'install and shutdown' or get
> scheduled for install like other updates.

The issue here is more likely that something (prerequisite) is not yet
installed that is required for SP3 than it is that SP3 is not being
scheduled for installation.

> Only when i log in with
> administrator credentials the notification balloon appears.

Most unusual.

Can you please log into this system with administrator credentials, and then
capture and post the most recent detection event from the WindowsUpdate.log?


--
Lawrence Garvin, M.S., MCITP:EA, MCDBA
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2009)

MS WSUS Website: http://www.microsoft.com/wsus
My Websites: http://www.onsitechsolutions.com;
http://wsusinfo.onsitechsolutions.com
My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin

All security and critical updates are installed ,what other prerequisites are
needed?

Thanks for the quick response

regards,
Stefan

"Lawrence Garvin [MVP]" wrote:

> "sver" <> wrote in message
> news:F0AA21B1-63EA-4DF7-A35A-...
> > Hi,
> >
> > My users don't have administrator rights and don't get a notification
> > balloon from WU.
> > i've noticed the SP3 doesn't appear wtih 'install and shutdown' or get
> > scheduled for install like other updates.
>
> The issue here is more likely that something (prerequisite) is not yet
> installed that is required for SP3 than it is that SP3 is not being
> scheduled for installation.
>
> > Only when i log in with
> > administrator credentials the notification balloon appears.
>
> Most unusual.
>
> Can you please log into this system with administrator credentials, and then
> capture and post the most recent detection event from the WindowsUpdate.log?
>
>
> --
> Lawrence Garvin, M.S., MCITP:EA, MCDBA
> Principal/CTO, Onsite Technology Solutions, Houston, Texas
> Microsoft MVP - Software Distribution (2005-2009)
>
> MS WSUS Website: http://www.microsoft.com/wsus
> My Websites: http://www.onsitechsolutions.com;
> http://wsusinfo.onsitechsolutions.com
> My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin
>
>

"sver" <> wrote in message
news:15209918-67D0-4B1B-92ED-...
> All security and critical updates are installed ,what other prerequisites
> are
> needed?

With all due respect, I rarely buy into the statement that "all security and
critical updates are installed", because:

1. Nobody said the problem was limited to security/critical updates.
2. Even so, it's rarely true.

I'm happy to help ... but in order to do so...

>> Can you please log into this system with administrator credentials, and
>> then
>> capture and post the most recent detection event from the
>> WindowsUpdate.log?


--
Lawrence Garvin, M.S., MCITP:EA, MCDBA
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2009)

MS WSUS Website: http://www.microsoft.com/wsus
My Websites: http://www.onsitechsolutions.com;
http://wsusinfo.onsitechsolutions.com
My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin

sver wrote:

> My users don't have administrator rights and don't get a notification
> balloon from WU.
> i've noticed the SP3 doesn't appear wtih 'install and shutdown' or get
> scheduled for install like other updates.Only when i log in with
> administrator credentials the notification balloon appears.

I can confirm that in my domain there was no problem with scheduling the SP3
install.

The behaviour you describe is normal for Automatic Updates; are you sure your
clients are pointed at a WSUS server? Or, if they were using Automatic Updates
at the time SP3 was downloaded and were then moved to WSUS, the AU behaviour
might be carried over.

Harry.

Here the log file Lawrence:

2009-06-29 08:38:03:661 1080 a5c AU Triggering AU detection through
DetectNow API
2009-06-29 08:38:03:661 1080 a5c AU Triggering Online detection
(non-interactive)
2009-06-29 08:38:03:661 1080 13c AU #############
2009-06-29 08:38:03:661 1080 13c AU ## START ## AU: Search for updates
2009-06-29 08:38:03:661 1080 13c AU #########
2009-06-29 08:38:03:661 1080 13c AU <<## SUBMITTED ## AU: Search for updates
[CallId = {EC956530-2F5A-4EE7-AED3-2BD663F16D22}]
2009-06-29 08:38:03:661 1080 724 Agent *************
2009-06-29 08:38:03:661 1080 724 Agent ** START ** Agent: Finding updates
[CallerId = AutomaticUpdates]
2009-06-29 08:38:03:661 1080 724 Agent *********
2009-06-29 08:38:03:661 1080 724 Agent * Online = Yes; Ignore download
priority = No
2009-06-29 08:38:03:661 1080 724 Agent * Criteria = "IsHidden=0 and
IsInstalled=0 and DeploymentAction='Installation' and IsAssigned=1 or
IsHidden=0 and IsPresent=1 and DeploymentAction='Uninstallation' and
IsAssigned=1 or IsHidden=0 and IsInstalled=1 and
DeploymentAction='Installation' and IsAssigned=1 and RebootRequired=1 or
IsHidden=0 and IsInstalled=0 and DeploymentAction='Uninstallation' and
IsAssigned=1 and RebootRequired=1"
2009-06-29 08:38:03:661 1080 724 Agent * ServiceID =
{3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}
2009-06-29 08:38:03:661 1080 724 Agent * Search Scope = {Machine}
2009-06-29 08:38:03:770 1080 724 Misc Validating signature for
C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default \wuident.cab:
2009-06-29 08:38:03:879 1080 724 Misc Microsoft signed: Yes
2009-06-29 08:38:06:208 1080 724 Misc Validating signature for
C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default \wuident.cab:
2009-06-29 08:38:06:224 1080 724 Misc Microsoft signed: Yes
2009-06-29 08:38:06:318 1080 724 Misc Validating signature for
C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default \wsus3setup.cab:
2009-06-29 08:38:06:318 1080 724 Misc Microsoft signed: Yes
2009-06-29 08:38:06:333 1080 724 Setup *********** Setup: Checking whether
self-update is required ***********
2009-06-29 08:38:06:333 1080 724 Setup * Inf file:
C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default \wsus3setup.inf
2009-06-29 08:38:06:349 1080 724 Setup Update NOT required for
C:\WINDOWS\system32\cdm.dll: target version = 7.2.6001.788, required version
= 7.1.6001.65
2009-06-29 08:38:06:349 1080 724 Setup Update NOT required for
C:\WINDOWS\system32\wuapi.dll: target version = 7.2.6001.788, required
version = 7.1.6001.65
2009-06-29 08:38:06:349 1080 724 Setup Update NOT required for
C:\WINDOWS\system32\wuapi.dll.mui: target version = 7.2.6001.788, required
version = 7.1.6001.65
2009-06-29 08:38:06:349 1080 724 Setup Update NOT required for
C:\WINDOWS\system32\wuauclt.exe: target version = 7.2.6001.788, required
version = 7.1.6001.65
2009-06-29 08:38:06:349 1080 724 Setup Update NOT required for
C:\WINDOWS\system32\wuaucpl.cpl: target version = 7.2.6001.788, required
version = 7.1.6001.65
2009-06-29 08:38:06:365 1080 724 Setup Update NOT required for
C:\WINDOWS\system32\wuaucpl.cpl.mui: target version = 7.2.6001.788, required
version = 7.1.6001.65
2009-06-29 08:38:06:365 1080 724 Setup Update NOT required for
C:\WINDOWS\system32\wuaueng.dll: target version = 7.2.6001.788, required
version = 7.1.6001.65
2009-06-29 08:38:06:365 1080 724 Setup Update NOT required for
C:\WINDOWS\system32\wuaueng.dll.mui: target version = 7.2.6001.788, required
version = 7.1.6001.65
2009-06-29 08:38:06:365 1080 724 Setup Update NOT required for
C:\WINDOWS\system32\wucltui.dll: target version = 7.2.6001.788, required
version = 7.1.6001.65
2009-06-29 08:38:06:365 1080 724 Setup Update NOT required for
C:\WINDOWS\system32\wucltui.dll.mui: target version = 7.2.6001.788, required
version = 7.1.6001.65
2009-06-29 08:38:06:380 1080 724 Setup Update NOT required for
C:\WINDOWS\system32\wups.dll: target version = 7.2.6001.788, required version
= 7.1.6001.65
2009-06-29 08:38:06:380 1080 724 Setup Update NOT required for
C:\WINDOWS\system32\wups2.dll: target version = 7.2.6001.788, required
version = 7.1.6001.65
2009-06-29 08:38:06:396 1080 724 Setup Update NOT required for
C:\WINDOWS\system32\wuweb.dll: target version = 7.2.6001.788, required
version = 7.1.6001.65
2009-06-29 08:38:06:396 1080 724 Setup WARNING: Warning: Setup callback
ReportProgress failed: 0x8007000d
2009-06-29 08:38:06:396 1080 724 Setup * IsUpdateRequired = No
2009-06-29 08:38:09:225 1080 724 PT +++++++++++ PT: Synchronizing server
updates +++++++++++
2009-06-29 08:38:09:225 1080 724 PT + ServiceId =
{3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL =
http://wsus.update.local:8530/Client...ce/client.asmx
2009-06-29 08:38:09:506 1080 724 PT WARNING: Cached cookie has expired or
new PID is available
2009-06-29 08:38:09:506 1080 724 PT Initializing simple targeting cookie,
clientId = ecaff028-3680-4ed2-918d-3a7d38dc4853, target group = , DNS name =
XXXXXXX
2009-06-29 08:38:09:506 1080 724 PT Server URL =
http://wsus.update.local:8530/Simple...impleAuth.asmx
2009-06-29 08:38:09:600 1080 724 Agent WARNING: Failed to evaluate Installed
rule, updateId = {A901C1BD-989C-45C6-8DA0-8DDE8DBB69E0}.103, hr = 8024E001
2009-06-29 08:38:13:601 1080 724 PT +++++++++++ PT: Synchronizing extended
update info +++++++++++
2009-06-29 08:38:13:601 1080 724 PT + ServiceId =
{3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL =
http://wsus.update.local:8530/Client...ce/client.asmx
2009-06-29 08:38:14:429 1080 724 Agent Update
{55576129-536E-40AD-921F-4611846199DE}.101 is pruned out due to potential
supersedence
2009-06-29 08:38:14:429 1080 724 Agent * Added update
{60B990A0-6EFA-47BE-8F5A-7DF2C402583E}.112 to search result
2009-06-29 08:38:14:429 1080 724 Agent * Found 1 updates and 46 categories
in search; evaluated appl. rules of 347 out of 777 deployed entities
2009-06-29 08:38:14:429 1080 724 Agent *********
2009-06-29 08:38:14:429 1080 724 Agent ** END ** Agent: Finding updates
[CallerId = AutomaticUpdates]
2009-06-29 08:38:14:429 1080 724 Agent *************
2009-06-29 08:38:14:445 1080 f60 AU >>## RESUMED ## AU: Search for updates
[CallId = {EC956530-2F5A-4EE7-AED3-2BD663F16D22}]
2009-06-29 08:38:14:445 1080 f60 AU # 1 updates detected
2009-06-29 08:38:14:445 1080 f60 AU #########
2009-06-29 08:38:14:445 1080 f60 AU ## END ## AU: Search for updates
[CallId = {EC956530-2F5A-4EE7-AED3-2BD663F16D22}]
2009-06-29 08:38:14:445 1080 f60 AU #############
2009-06-29 08:38:14:445 1080 f60 AU AU setting next detection timeout to
2009-06-30 03:11:13
2009-06-29 08:38:14:445 1080 f60 AU Setting AU scheduled install time to
2009-06-29 09:00:00
2009-06-29 08:38:19:431 1080 724 Report REPORT EVENT:
{E5068A72-5591-4C0A-BE42-C1C3CF8FC27D} 2009-06-29
08:38:14:429+0200 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software
Synchronization Windows Update Client successfully detected 1 updates.
2009-06-29 08:38:19:431 1080 724 Report REPORT EVENT:
{46EA8710-128B-4BDE-9D2C-EDAC6A2D84BE} 2009-06-29
08:38:14:429+0200 1 156 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Pre-Deployment Check Reporting client status.


Thanks for the help,

stefan

"Lawrence Garvin [MVP]" wrote:

> "sver" <> wrote in message
> news:15209918-67D0-4B1B-92ED-...
> > All security and critical updates are installed ,what other prerequisites
> > are
> > needed?
>
> With all due respect, I rarely buy into the statement that "all security and
> critical updates are installed", because:
>
> 1. Nobody said the problem was limited to security/critical updates.
> 2. Even so, it's rarely true.
>
> I'm happy to help ... but in order to do so...
>
> >> Can you please log into this system with administrator credentials, and
> >> then
> >> capture and post the most recent detection event from the
> >> WindowsUpdate.log?
>
>
> --
> Lawrence Garvin, M.S., MCITP:EA, MCDBA
> Principal/CTO, Onsite Technology Solutions, Houston, Texas
> Microsoft MVP - Software Distribution (2005-2009)
>
> MS WSUS Website: http://www.microsoft.com/wsus
> My Websites: http://www.onsitechsolutions.com;
> http://wsusinfo.onsitechsolutions.com
> My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin
>
>

"sver" <> wrote in message
news:B44EFD13-1364-4279-AED3-...

> 2009-06-29 08:38:06:396 1080 724 Setup WARNING: Warning: Setup callback
> ReportProgress failed: 0x8007000d

This is unexpected.

> 2009-06-29 08:38:09:600 1080 724 Agent WARNING: Failed to evaluate
> Installed
> rule, updateId = {A901C1BD-989C-45C6-8DA0-8DDE8DBB69E0}.103, hr = 8024E001

This is an issue being experienced by many, including myself, and is
currently under investigation. It's not related to XP SP3.

> 2009-06-29 08:38:14:429 1080 724 Agent * Added update
> {60B990A0-6EFA-47BE-8F5A-7DF2C402583E}.112 to search result
> 2009-06-29 08:38:14:429 1080 724 Agent * Found 1 updates and 46
> categories
> in search; evaluated appl. rules of 347 out of 777 deployed entities

The client found ONE update that needs to be installed. This is Windows XP
Service Pack 3.

> 2009-06-29 08:38:14:445 1080 f60 AU # 1 updates detected

> 2009-06-29 08:38:19:431 1080 724 Report REPORT EVENT:
> {E5068A72-5591-4C0A-BE42-C1C3CF8FC27D} 2009-06-29
> 08:38:14:429+0200 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0
> AutomaticUpdates Success Software
> Synchronization Windows Update Client successfully detected 1 updates.

So the client is successfully detecting XP SP3. Next step is to find out
what happened from here.

Please post the log entries from the next scheduled installation event.

--
Lawrence Garvin, M.S., MCITP:EA, MCDBA
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2009)

MS WSUS Website: http://www.microsoft.com/wsus
My Websites: http://www.onsitechsolutions.com;
http://wsusinfo.onsitechsolutions.com
My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin

Lawrence,

Herby the log of today.I've noticed SP3 is unpacked already in i386 folder
in subfolder of Softwaredistribution folder,but still no succes with
scheduled install.Thanks for spending some of your valuable time on this.

2009-06-30 05:11:13:049 1080 14c AU #############
2009-06-30 05:11:13:049 1080 14c AU ## START ## AU: Search for updates
2009-06-30 05:11:13:049 1080 14c AU #########
2009-06-30 05:11:13:049 1080 14c AU <<## SUBMITTED ## AU: Search for updates
[CallId = {73E02C6D-E541-4DDA-B030-FE57CEFA9C7B}]
2009-06-30 05:11:13:049 1080 594 Agent *************
2009-06-30 05:11:13:049 1080 594 Agent ** START ** Agent: Finding updates
[CallerId = AutomaticUpdates]
2009-06-30 05:11:13:049 1080 594 Agent *********
2009-06-30 05:11:13:049 1080 594 Agent * Online = Yes; Ignore download
priority = No
2009-06-30 05:11:13:049 1080 594 Agent * Criteria = "IsHidden=0 and
IsInstalled=0 and DeploymentAction='Installation' and IsAssigned=1 or
IsHidden=0 and

IsPresent=1 and DeploymentAction='Uninstallation' and IsAssigned=1 or
IsHidden=0 and IsInstalled=1 and DeploymentAction='Installation' and
IsAssigned=1 and RebootRequired=1 or

IsHidden=0 and IsInstalled=0 and DeploymentAction='Uninstallation' and
IsAssigned=1 and RebootRequired=1"
2009-06-30 05:11:13:049 1080 594 Agent * ServiceID =
{3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}
2009-06-30 05:11:13:049 1080 594 Agent * Search Scope = {Machine}
2009-06-30 05:11:13:064 1080 594 Misc Validating signature for
C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default \wuident.cab:
2009-06-30 05:11:13:158 1080 594 Misc Microsoft signed: Yes
2009-06-30 05:11:15:486 1080 594 Misc Validating signature for
C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default \wuident.cab:
2009-06-30 05:11:15:486 1080 594 Misc Microsoft signed: Yes
2009-06-30 05:11:20:377 1080 594 Misc Validating signature for
C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default \wsus3setup.cab:
2009-06-30 05:11:20:377 1080 594 Misc Microsoft signed: Yes
2009-06-30 05:11:20:392 1080 594 Setup *********** Setup: Checking whether
self-update is required ***********
2009-06-30 05:11:20:392 1080 594 Setup * Inf file:
C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default \wsus3setup.inf
2009-06-30 05:11:20:408 1080 594 Setup Update NOT required for
C:\WINDOWS\system32\cdm.dll: target version = 7.2.6001.788, required version
= 7.1.6001.65
2009-06-30 05:11:20:408 1080 594 Setup Update NOT required for
C:\WINDOWS\system32\wuapi.dll: target version = 7.2.6001.788, required
version = 7.1.6001.65
2009-06-30 05:11:20:424 1080 594 Setup Update NOT required for
C:\WINDOWS\system32\wuapi.dll.mui: target version = 7.2.6001.788, required
version = 7.1.6001.65
2009-06-30 05:11:20:424 1080 594 Setup Update NOT required for
C:\WINDOWS\system32\wuauclt.exe: target version = 7.2.6001.788, required
version = 7.1.6001.65
2009-06-30 05:11:20:424 1080 594 Setup Update NOT required for
C:\WINDOWS\system32\wuaucpl.cpl: target version = 7.2.6001.788, required
version = 7.1.6001.65
2009-06-30 05:11:20:424 1080 594 Setup Update NOT required for
C:\WINDOWS\system32\wuaucpl.cpl.mui: target version = 7.2.6001.788, required
version = 7.1.6001.65
2009-06-30 05:11:20:424 1080 594 Setup Update NOT required for
C:\WINDOWS\system32\wuaueng.dll: target version = 7.2.6001.788, required
version = 7.1.6001.65
2009-06-30 05:11:20:439 1080 594 Setup Update NOT required for
C:\WINDOWS\system32\wuaueng.dll.mui: target version = 7.2.6001.788, required
version = 7.1.6001.65
2009-06-30 05:11:20:439 1080 594 Setup Update NOT required for
C:\WINDOWS\system32\wucltui.dll: target version = 7.2.6001.788, required
version = 7.1.6001.65
2009-06-30 05:11:20:439 1080 594 Setup Update NOT required for
C:\WINDOWS\system32\wucltui.dll.mui: target version = 7.2.6001.788, required
version = 7.1.6001.65
2009-06-30 05:11:20:439 1080 594 Setup Update NOT required for
C:\WINDOWS\system32\wups.dll: target version = 7.2.6001.788, required version
= 7.1.6001.65
2009-06-30 05:11:20:455 1080 594 Setup Update NOT required for
C:\WINDOWS\system32\wups2.dll: target version = 7.2.6001.788, required
version = 7.1.6001.65
2009-06-30 05:11:20:471 1080 594 Setup Update NOT required for
C:\WINDOWS\system32\wuweb.dll: target version = 7.2.6001.788, required
version = 7.1.6001.65
2009-06-30 05:11:20:471 1080 594 Setup WARNING: Warning: Setup callback
ReportProgress failed: 0x8007000d
2009-06-30 05:11:20:471 1080 594 Setup * IsUpdateRequired = No
2009-06-30 05:11:23:643 1080 594 PT +++++++++++ PT: Synchronizing server
updates +++++++++++
2009-06-30 05:11:23:643 1080 594 PT + ServiceId =
{3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL =

http://wsus.update.local:8530/Client...ce/client.asmx
2009-06-30 05:11:23:986 1080 594 PT WARNING: Cached cookie has expired or
new PID is available
2009-06-30 05:11:23:986 1080 594 PT Initializing simple targeting cookie,
clientId = ecaff028-3680-4ed2-918d-3a7d38dc4853, target group = , DNS name =
xxxxxx
2009-06-30 05:11:23:986 1080 594 PT Server URL =
http://wsus.update.local:8530/Simple...impleAuth.asmx
2009-06-30 05:11:24:064 1080 594 Agent WARNING: Failed to evaluate Installed
rule, updateId = {A901C1BD-989C-45C6-8DA0-8DDE8DBB69E0}.103, hr = 8024E001
2009-06-30 05:11:27:861 1080 594 PT +++++++++++ PT: Synchronizing extended
update info +++++++++++
2009-06-30 05:11:27:861 1080 594 PT + ServiceId =
{3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL =

http://wsus.update.local:8530/Client...ce/client.asmx
2009-06-30 05:11:29:033 1080 594 Agent Update
{55576129-536E-40AD-921F-4611846199DE}.101 is pruned out due to potential
supersedence
2009-06-30 05:11:29:033 1080 594 Agent * Added update
{60B990A0-6EFA-47BE-8F5A-7DF2C402583E}.112 to search result
2009-06-30 05:11:29:033 1080 594 Agent * Found 1 updates and 46 categories
in search; evaluated appl. rules of 346 out of 775 deployed entities
2009-06-30 05:11:29:033 1080 594 Agent *********
2009-06-30 05:11:29:033 1080 594 Agent ** END ** Agent: Finding updates
[CallerId = AutomaticUpdates]
2009-06-30 05:11:29:033 1080 594 Agent *************
2009-06-30 05:11:29:049 1080 fd4 AU >>## RESUMED ## AU: Search for updates
[CallId = {73E02C6D-E541-4DDA-B030-FE57CEFA9C7B}]
2009-06-30 05:11:29:049 1080 fd4 AU # 1 updates detected
2009-06-30 05:11:29:049 1080 fd4 AU #########
2009-06-30 05:11:29:049 1080 fd4 AU ## END ## AU: Search for updates
[CallId = {73E02C6D-E541-4DDA-B030-FE57CEFA9C7B}]
2009-06-30 05:11:29:049 1080 fd4 AU #############
2009-06-30 05:11:29:049 1080 fd4 AU AU setting next detection timeout to
2009-06-30 22:06:47
2009-06-30 05:11:29:049 1080 fd4 AU Setting AU scheduled install time to
2009-06-30 09:00:00
2009-06-30 05:11:34:127 1080 594 Report REPORT EVENT:
{CE02A5A2-D3FB-43D3-BFE1-2A920E20447E} 2009-06-30
05:11:29:033+0200 1 147 101 {00000000-

0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software
Synchronization Windows Update Client successfully detected 1 updates.
2009-06-30 05:11:34:127 1080 594 Report REPORT EVENT:
{4EC45D2E-5729-4889-8722-37E3CF41B071} 2009-06-30
05:11:29:033+0200 1 156 101 {00000000-

0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Pre-Deployment
Check Reporting client status.
2009-06-30 05:24:36:075 1080 594 Report Uploading 2 events using cached
cookie, reporting URL =

http://wsus.update.local:8530/Report...ebService.asmx
2009-06-30 05:24:36:090 1080 594 Report Reporter successfully uploaded 2
events.
2009-06-30 05:42:33:307 1080 14c AU AU received policy change subscription
event
2009-06-30 07:31:40:094 1080 14c AU AU received policy change subscription
event
2009-06-30 09:00:10:068 1080 14c AU Forced install timer expired for
scheduled install
2009-06-30 09:00:10:068 1080 14c AU UpdateDownloadProperties: 0 download(s)
are still in progress.
2009-06-30 09:00:10:068 1080 14c AU Setting AU scheduled install time to
2009-07-01 09:00:00
2009-06-30 09:19:48:583 1080 14c AU AU received policy change subscription
event


"Lawrence Garvin [MVP]" wrote:

> "sver" <> wrote in message
> news:B44EFD13-1364-4279-AED3-...
>
> > 2009-06-29 08:38:06:396 1080 724 Setup WARNING: Warning: Setup callback
> > ReportProgress failed: 0x8007000d
>
> This is unexpected.
>
> > 2009-06-29 08:38:09:600 1080 724 Agent WARNING: Failed to evaluate
> > Installed
> > rule, updateId = {A901C1BD-989C-45C6-8DA0-8DDE8DBB69E0}.103, hr = 8024E001
>
> This is an issue being experienced by many, including myself, and is
> currently under investigation. It's not related to XP SP3.
>
> > 2009-06-29 08:38:14:429 1080 724 Agent * Added update
> > {60B990A0-6EFA-47BE-8F5A-7DF2C402583E}.112 to search result
> > 2009-06-29 08:38:14:429 1080 724 Agent * Found 1 updates and 46
> > categories
> > in search; evaluated appl. rules of 347 out of 777 deployed entities
>
> The client found ONE update that needs to be installed. This is Windows XP
> Service Pack 3.
>
> > 2009-06-29 08:38:14:445 1080 f60 AU # 1 updates detected
>
> > 2009-06-29 08:38:19:431 1080 724 Report REPORT EVENT:
> > {E5068A72-5591-4C0A-BE42-C1C3CF8FC27D} 2009-06-29
> > 08:38:14:429+0200 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0
> > AutomaticUpdates Success Software
> > Synchronization Windows Update Client successfully detected 1 updates.
>
> So the client is successfully detecting XP SP3. Next step is to find out
> what happened from here.
>
> Please post the log entries from the next scheduled installation event.
>
> --
> Lawrence Garvin, M.S., MCITP:EA, MCDBA
> Principal/CTO, Onsite Technology Solutions, Houston, Texas
> Microsoft MVP - Software Distribution (2005-2009)
>
> MS WSUS Website: http://www.microsoft.com/wsus
> My Websites: http://www.onsitechsolutions.com;
> http://wsusinfo.onsitechsolutions.com
> My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin
>
>

"sver" <> wrote in message
news:902D7BEE-D027-43BD-8C20-...

> Lawrence,
>
> Herby the log of today.I've noticed SP3 is unpacked already in i386 folder
> in subfolder of Softwaredistribution folder,but still no succes with
> scheduled install.Thanks for spending some of your valuable time on this.

> 2009-06-30 05:11:29:033 1080 594 Agent * Added update
> {60B990A0-6EFA-47BE-8F5A-7DF2C402583E}.112 to search result

> 2009-06-30 05:11:29:033 1080 594 Agent * Found 1 updates and 46
> categories
> in search; evaluated appl. rules of 346 out of 775 deployed entities

> 0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software
> Synchronization Windows Update Client successfully detected 1 updates.
> 2009-06-30 05:11:34:127 1080 594 Report REPORT EVENT:
> {4EC45D2E-5729-4889-8722-37E3CF41B071} 2009-06-30
> 05:11:29:033+0200 1 156 101 {00000000-

> 2009-06-30 09:00:10:068 1080 14c AU Forced install timer expired for
> scheduled install
> 2009-06-30 09:00:10:068 1080 14c AU UpdateDownloadProperties: 0
> download(s)
> are still in progress.


The issue here appears to be that the client is only detecting the update.

I see no evidence that the client has downloaded the update,
nor is there any evidence that the update was previously downloaded,
and it's certainly not been scheduled for installation -- which is why it's
not installing!

Please review your WSUS Server and verify that the file content for this
update is actually downloaded to the WSUS Server.

Also, review the logfile at
%windir%\SoftwareDistribution\ReportingEvents.log,
as well as the entire WindowsUpdate.log,
to see if you can find any evidence that this update was downloaded to the
client.

As for SP3 being already unpacked in an i386 folder in a subfolder of the
SoftwareDistribution folder, see if you can match up the creation time of
that SoftwareDistribution folder with log entries from the
WindowsUpdate.log, and demonstrate that this folder actually exists as a
result of anything that the WUAgent did. If the WUAgent created that folder,
it would have done so either as a result of a scheduled installation event
(9am local), or as a result of a user-interaction with the WUAgent
initiating an interactive installation.

Btw.... installing a SERVICE PACK at 9am, during working hours, is a REALLY
BAD IDEA.


--
Lawrence Garvin, M.S., MCITP:EA, MCDBA
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2009)

MS WSUS Website: http://www.microsoft.com/wsus
My Websites: http://www.onsitechsolutions.com;
http://wsusinfo.onsitechsolutions.com
My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin