SBS 2k3 SP2 and WSUS 3.0 SP1

Our client has only one server and it's OS is Windows 2k3 Server for SBS
SP2. I tried putting WSUS 3.0 SP1 on there a couple months ago and set to
automatically approve critical/security updates. I checked in and saw that
the server itself nor clients could communicate with the WSUS on the server.
After modifying the domain GPO for both groups of machines I got to a
certain point and was stuck. So I've backed up the WSUS database, updates,
and log files and then uninstalled WSUS through the Add/Remove programs (to
sort of start from scratch). Server has been restarted.

Applied 40+ updates that came out since then. Restart will be done before
reinstall of WSUS.

My question are, other than Microsoft saying to not use wizard configuration
tool that pops up during the installation nor setting synchronzation to
manual, is there anything else that I should be aware of when I reinstall
WSUS 3.0 SP1?

If the server was called Server1 then the pointer (WUServer, WUStatusServer)
would be http://Server1:8530 for the machines to recieve updates from if I'm
having Server1's D drive act as the repository for the approved update?

"Seab" <> wrote in message
news:...


> My question are, other than Microsoft saying to not use wizard
> configuration tool that pops up during the installation

There's no reason NOT to use the setup wizard when installing WSUS 3 SP1 on
an SBS2003SP2 system, provided that the R2 Technologies version of WSUS has
not previously been installed. Given your descriptions above, I don't think
this is the case here.

> nor setting synchronzation to manual,

Well, setting synchronization to manual is not something I'd do for ANY WSUS
Server, except those I was doing testing/training on.

> is there anything else that I should be aware of when I reinstall WSUS 3.0
> SP1?

There are a *LOT* of things you should be aware of before installing WSUS
3.0 SP1 anywhere, but particularly on Small Business Server.

[1] Read the Release Notes TWICE, and verify none of those issues are
applicable.

[2] Review the Deployment Guide and make sure you understand the basics.

[3] If it doesn't work as expected, after installation -- perform
DIAGNOSTICS before changing anything. For example, in your original
installation, you noted that neither the clients, nor the server itself,
could communicate with the wsus services. There are several well-known
causes and simple remediations for these causes. Post back here and ASK if
you have any issues. (Note: Modifying the Default Domain Policy is not on
the list of recommended remediations, or even on the list of recommended
practices. Create a =WSUS= policy for deploying WSUS. In fact, you'll
probably need to create three WSUS policies -- one for desktops, one for
notebooks, and one for servers, and the server policy will need to be linked
to two different OUs.)

> If the server was called Server1 then the pointer (WUServer,
> WUStatusServer) would be http://Server1:8530 for the machines to recieve
> updates from

Correct.

> if I'm having Server1's D drive act as the repository for the approved
> update?

Where the update repository is, has absolutely nothing to do with the URL
for WUServer and WUStatusServer. The value would be http://Server1:8530 for
SBS2003 under ANY conditions.


--
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

Good early morning,
The server and two out of the eight clients (most client machines hibernate)
have show up in the Update Services admin console since the reinstall, but
that still have not upated their status. I have run the rule to have it
automatically approve critical/security updates as well as WSUS updates. I
found three areas (Default Domain Policy, Small Business Server Client
Computer, & Small Business Server Windows Firewall), in which Update
Services was configured ,for all authenticated users, of which I was
unaware. After installing WSUS 3.0 SP1, I found and changed those policies
that dealt with Windows Updates to not configured. I have two Update
Services policies, one holding the server and another holding the client
machines. The server SUS GPO, client diagostic readout, and windows
update.log (~3am gpudate /force, ~3:15am wuauclt.exe /detectnow) are listed
as follows:

Allow non-administrators to recieve update notifications: Enabled
Configure Automatic Updates: Enabled
Configure automatic updating: 4 - Auto download and schedule the
install
The following settings are only required and applicable if 4 is selected
Scheduled install day 0 - Every day
Scheudled install time: 03:00

Policy
Do not display 'Install Updates and Shut Down' option in Shut Down Windows
dialog box: Enabled
No auto-restart with logged on users for scheduled automatic updates
installations: Enabled
Re-prompt for restart with scheduled installations: Enabled
Wait for the following period before prompting again with a scheduled
restart (minutes): 30

Specify intranet Microsoft update service location: Enabled
Set the intranet update service for detecting updates:
http://XXXXXX:8530
Set the intranet statistics server: http://XXXXXX:8530


WSUS Client Diagnostics Tool

Checking Machine State
Checking for admin rights to run tool . . . . . . . . . PASS
Automatic Updates Service is running. . . . . . . . . . PASS
Background Intelligent Transfer Service is running. . . PASS
Wuaueng.dll version 7.2.6001.788. . . . . . . . . . . . PASS
This version is WSUS 2.0

Checking AU Settings
AU Option is 4: Scheduled Install . . . . . . . . . . . PASS
Option is from Policy settings

Checking Proxy Configuration
Checking for winhttp local machine Proxy settings . . . PASS
Winhttp local machine access type
<Direct Connection>
Winhttp local machine Proxy. . . . . . . . . . NONE
Winhttp local machine ProxyBypass. . . . . . . NONE
Checking User IE Proxy settings . . . . . . . . . . . . PASS
User IE Proxy. . . . . . . . . . . . . . . . . NONE
User IE ProxyByPass. . . . . . . . . . . . . . NONE
User IE AutoConfig URL Proxy . . . . . . . . . NONE
User IE AutoDetect
AutoDetect not in use

Checking Connection to WSUS/SUS Server
WUServer = http://XXXXXX:8530
WUStatusServer = http://XXXXXX:8530
UseWuServer is enabled. . . . . . . . . . . . . . . . . PASS
Connection to server. . . . . . . . . . . . . . . . . . PASS
SelfUpdate folder is present. . . . . . . . . . . . . . PASS

Press Enter to Complete


2009-06-15 02:59:35:828 7184 2334 Misc =========== Logging initialized
(build: 7.2.6001.788, tz: -0700) ===========
2009-06-15 02:59:35:828 7184 2334 Misc = Process:
C:\WINDOWS\system32\wuauclt.exe
2009-06-15 02:59:35:828 7184 2334 AUClnt Launched Client UI process
2009-06-15 02:59:35:875 7184 2334 Misc =========== Logging initialized
(build: 7.2.6001.788, tz: -0700) ===========
2009-06-15 02:59:35:875 7184 2334 Misc = Process:
C:\WINDOWS\system32\wuauclt.exe
2009-06-15 02:59:35:875 7184 2334 Misc = Module:
C:\WINDOWS\system32\wucltui.dll
2009-06-15 02:59:35:875 7184 2334 CltUI AU client got new directive =
'Install Approval', serviceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7},
return = 0x00000000
2009-06-15 02:59:35:875 7184 2334 CltUI AU client creating default WU/WSUS
UI plugin
2009-06-15 03:00:10:000 1060 664 AU Forced install timer expired for
scheduled install
2009-06-15 03:00:10:000 1060 664 AU UpdateDownloadProperties: 0 download(s)
are still in progress.
2009-06-15 03:00:10:000 1060 664 AU #############
2009-06-15 03:00:10:000 1060 664 AU ## START ## AU: Install updates
2009-06-15 03:00:10:000 1060 664 AU #########
2009-06-15 03:00:10:000 1060 664 AU # Initiating scheduled install
2009-06-15 03:00:10:000 1060 664 AU # Approved updates = 1
2009-06-15 03:00:10:109 1060 664 AU <<## SUBMITTED ## AU: Install updates /
installing updates [CallId = {DA0A5E5A-3119-4296-B1FD-4838071A2258}]
2009-06-15 03:00:10:109 1060 2090 Agent *************
2009-06-15 03:00:10:109 1060 2090 Agent ** START ** Agent: Installing
updates [CallerId = AutomaticUpdates]
2009-06-15 03:00:10:109 1060 2090 Agent *********
2009-06-15 03:00:10:109 1060 2090 Agent * Updates to install = 1
2009-06-15 03:00:10:109 7184 2334 CltUI AU client got new directive =
'Shutdown', serviceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, return =
0x00000000
2009-06-15 03:00:10:187 1060 2090 Agent WARNING: fail to get update
deployments with error 0x80248007
2009-06-15 03:00:10:187 1060 2090 Agent * Title = Update for Windows
Server Update Services (WSUS) 3 Service Pack 1 (KB954960)
2009-06-15 03:00:10:187 1060 2090 Agent * UpdateId =
{9772AEDE-91AB-499A-B1E7-00D357DEAE89}.100
2009-06-15 03:00:10:187 1060 2090 Agent * Bundles 1 updates:
2009-06-15 03:00:10:187 1060 2090 Agent *
{2C34B6C0-8AA6-406A-9EF9-69D8D0CAC5D3}.100
2009-06-15 03:00:10:281 1060 2090 Agent *********
2009-06-15 03:00:10:281 1060 1a54 AU >>## RESUMED ## AU: Installing update
[UpdateId = {9772AEDE-91AB-499A-B1E7-00D357DEAE89}]
2009-06-15 03:00:10:281 1060 2090 Agent ** END ** Agent: Installing
updates [CallerId = AutomaticUpdates]
2009-06-15 03:00:10:281 1060 1a54 AU # WARNING: Install failed, error =
0x80240017 / 0x00000000
2009-06-15 03:00:10:281 1060 2090 Agent *************
2009-06-15 03:00:10:281 1060 1a54 AU Install call completed.
2009-06-15 03:00:10:281 1060 1a54 AU # WARNING: Install call completed,
reboot required = No, error = 0x00000000
2009-06-15 03:00:10:281 1060 1a54 AU #########
2009-06-15 03:00:10:281 1060 1a54 AU ## END ## AU: Installing updates
[CallId = {DA0A5E5A-3119-4296-B1FD-4838071A2258}]
2009-06-15 03:00:10:281 1060 1a54 AU #############
2009-06-15 03:00:10:281 1060 1a54 AU Install complete for all calls, reboot
NOT needed
2009-06-15 03:00:10:281 1060 1a54 AU Setting AU scheduled install time to
2009-06-16 10:00:00
2009-06-15 03:00:10:281 1060 1a54 AU AU setting pending client directive to
'Install Approval'
2009-06-15 03:00:10:281 1060 1a54 AU Changing existing AU client directive
from 'Shutdown' to 'Install Approval', session id = 0x0
2009-06-15 03:00:10:281 1060 1a54 AU Triggering Offline detection
(non-interactive)
2009-06-15 03:00:10:281 1060 664 AU #############
2009-06-15 03:00:10:296 1060 664 AU ## START ## AU: Search for updates
2009-06-15 03:00:10:296 1060 664 AU #########
2009-06-15 03:00:10:296 1060 664 AU <<## SUBMITTED ## AU: Search for updates
[CallId = {53955A07-0B12-4440-B5A8-E474E2907DAC}]
2009-06-15 03:00:10:296 1060 22f0 Agent *************
2009-06-15 03:00:10:296 1060 22f0 Agent ** START ** Agent: Finding updates
[CallerId = AutomaticUpdates]
2009-06-15 03:00:10:296 1060 22f0 Agent *********
2009-06-15 03:00:10:296 1060 22f0 Agent * Online = No; Ignore download
priority = No
2009-06-15 03:00:10:296 1060 22f0 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-15 03:00:10:296 1060 22f0 Agent * ServiceID =
{3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}
2009-06-15 03:00:10:296 1060 22f0 Agent * Search Scope = {Machine}
2009-06-15 03:00:10:312 1060 664 AU AU received handle event
2009-06-15 03:00:10:312 1060 664 AU AU setting pending client directive to
'Install Approval'
2009-06-15 03:00:10:437 1060 22f0 Agent * Found 0 updates and 0 categories
in search; evaluated appl. rules of 0 out of 0 deployed entities
2009-06-15 03:00:10:890 1060 22f0 Agent *********
2009-06-15 03:00:10:890 1060 22f0 Agent ** END ** Agent: Finding updates
[CallerId = AutomaticUpdates]
2009-06-15 03:00:10:890 1060 22f0 Agent *************
2009-06-15 03:00:10:890 1060 1a54 AU >>## RESUMED ## AU: Search for
updates [CallId = {53955A07-0B12-4440-B5A8-E474E2907DAC}]
2009-06-15 03:00:10:890 1060 1a54 AU # 0 updates detected
2009-06-15 03:00:10:890 1060 1a54 AU #########
2009-06-15 03:00:10:890 1060 1a54 AU ## END ## AU: Search for updates
[CallId = {53955A07-0B12-4440-B5A8-E474E2907DAC}]
2009-06-15 03:00:10:890 1060 1a54 AU #############
2009-06-15 03:00:10:890 1060 1a54 AU Setting AU scheduled install time to
2009-06-16 10:00:00
2009-06-15 03:00:25:312 1060 664 AU No pending client directive
2009-06-15 03:01:05:015 1060 22f0 PT WARNING: Cached cookie has expired or
new PID is available
2009-06-15 03:01:05:015 1060 22f0 PT Initializing simple targeting cookie,
clientId = f4e03ff8-4f6f-4588-8780-1867a06a55a2, target group = Server 2003
SBS, DNS name = server.lozano.local
2009-06-15 03:01:05:015 1060 22f0 PT Server URL =
http://XXXXXX:8530/SimpleAuthWebService/SimpleAuth.asmx
2009-06-15 03:01:05:828 1060 22f0 PT WARNING: GetCookie failure, error =
0x8024400D, soap client error = 7, soap error code = 300, HTTP status code =
200
2009-06-15 03:01:05:828 1060 22f0 PT WARNING: SOAP Fault: 0x00012c
2009-06-15 03:01:05:828 1060 22f0 PT WARNING:
faultstring:System.Web.Services.Protocols.SoapExce ption: Fault occurred
at
Microsoft.UpdateServices.Internal.SoapUtilities.Th rowException(ErrorCode
errorCode, String message, String[] clientIds)
at
Microsoft.UpdateServices.Internal.ClientImplementa tion.GetCookie(AuthorizationCookie[]
authCookies, Cookie oldCookie, DateTime lastChange, DateTime
currentClientTime, String protocolVersion)
at
Microsoft.UpdateServices.Internal.Client.GetCookie (AuthorizationCookie[]
authCookies, Cookie oldCookie, DateTime lastChange, DateTime currentTime,
String protocolVersion)
2009-06-15 03:01:05:828 1060 22f0 PT WARNING: ErrorCode:ConfigChanged(2)
2009-06-15 03:01:05:828 1060 22f0 PT WARNING: Messagenull)
2009-06-15 03:01:05:828 1060 22f0 PT WARNING:
Method:"http://www.microsoft.com/SoftwareDistribution/Server/ClientWebService/GetCookie"
2009-06-15 03:01:05:828 1060 22f0 PT WARNING:
ID:4716ea43-40a6-430c-9ed3-d222f9e99ec2
2009-06-15 03:01:05:859 1060 22f0 PT WARNING: Cached cookie has expired or
new PID is available
2009-06-15 03:01:05:859 1060 22f0 PT Initializing simple targeting cookie,
clientId = f4e03ff8-4f6f-4588-8780-1867a06a55a2, target group = Server 2003
SBS, DNS name = server.lozano.local
2009-06-15 03:01:05:859 1060 22f0 PT Server URL =
http://XXXXXX:8530/SimpleAuthWebService/SimpleAuth.asmx
2009-06-15 03:01:05:937 1060 22f0 Report Uploading 1 events using cached
cookie, reporting URL =
http://XXXXXX:8530/ReportingWebServi...ebService.asmx
2009-06-15 03:01:06:000 1060 22f0 Report Reporter successfully uploaded 1
events.
2009-06-15 03:15:01:343 1060 1c24 AU Triggering AU detection through
DetectNow API
2009-06-15 03:15:01:343 1060 1c24 AU Triggering Online detection
(non-interactive)
2009-06-15 03:15:01:343 1060 664 AU #############
2009-06-15 03:15:01:343 1060 664 AU ## START ## AU: Search for updates
2009-06-15 03:15:01:343 1060 664 AU #########
2009-06-15 03:15:01:343 1060 664 AU <<## SUBMITTED ## AU: Search for updates
[CallId = {BBFEDB93-4851-4EF0-A885-F5311D1FE226}]
2009-06-15 03:15:01:343 1060 22f0 Agent *************
2009-06-15 03:15:01:343 1060 22f0 Agent ** START ** Agent: Finding updates
[CallerId = AutomaticUpdates]
2009-06-15 03:15:01:343 1060 22f0 Agent *********
2009-06-15 03:15:01:343 1060 22f0 Agent * Online = Yes; Ignore download
priority = No
2009-06-15 03:15:01:343 1060 22f0 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-15 03:15:01:343 1060 22f0 Agent * ServiceID =
{3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}
2009-06-15 03:15:01:343 1060 22f0 Agent * Search Scope = {Machine}
2009-06-15 03:15:01:343 1060 22f0 Misc Validating signature for
C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default \wuident.cab:
2009-06-15 03:15:01:359 1060 22f0 Misc Microsoft signed: Yes
2009-06-15 03:15:01:359 1060 22f0 Misc WARNING: WinHttp:
SendRequestToServerForFileInformation failed with 0x80190194
2009-06-15 03:15:01:359 1060 22f0 Misc WARNING: WinHttp:
ShouldFileBeDownloaded failed with 0x80190194
2009-06-15 03:15:01:359 1060 22f0 Misc WARNING: DownloadFileInternal failed
for http://XXXXXX:8530/selfupdate/wuident.cab: error 0x80190194
2009-06-15 03:15:01:359 1060 22f0 Setup FATAL: IsUpdateRequired failed with
error 0x80244019
2009-06-15 03:15:01:359 1060 22f0 Setup WARNING: SelfUpdate: Default
Service: IsUpdateRequired failed: 0x80244019
2009-06-15 03:15:01:359 1060 22f0 Setup WARNING: SelfUpdate: Default
Service: IsUpdateRequired failed, error = 0x80244019
2009-06-15 03:15:01:359 1060 22f0 Agent * WARNING: Skipping scan,
self-update check returned 0x80244019
2009-06-15 03:15:02:421 1060 22f0 Agent * WARNING: Exit code = 0x80244019
2009-06-15 03:15:02:421 1060 22f0 Agent *********
2009-06-15 03:15:02:421 1060 22f0 Agent ** END ** Agent: Finding updates
[CallerId = AutomaticUpdates]
2009-06-15 03:15:02:421 1060 22f0 Agent *************
2009-06-15 03:15:02:421 1060 22f0 Agent WARNING: WU client failed Searching
for update with error 0x80244019
2009-06-15 03:15:02:421 1060 1a54 AU >>## RESUMED ## AU: Search for
updates [CallId = {BBFEDB93-4851-4EF0-A885-F5311D1FE226}]
2009-06-15 03:15:02:421 1060 1a54 AU # WARNING: Search callback failed,
result = 0x80244019
2009-06-15 03:15:02:421 1060 1a54 AU # WARNING: Failed to find updates
with error code 80244019
2009-06-15 03:15:02:421 1060 1a54 AU #########
2009-06-15 03:15:02:421 1060 1a54 AU ## END ## AU: Search for updates
[CallId = {BBFEDB93-4851-4EF0-A885-F5311D1FE226}]
2009-06-15 03:15:02:421 1060 1a54 AU #############
2009-06-15 03:15:02:421 1060 1a54 AU AU setting next detection timeout to
2009-06-15 15:15:02
2009-06-15 03:15:02:421 1060 1a54 AU Setting AU scheduled install time to
2009-06-16 10:00:00
2009-06-15 03:15:06:359 1060 22f0 Report REPORT EVENT:
{0DF48560-6F7A-407C-83E2-04F3BA56560A} 2009-06-15 03:15:01:359-0700 1 148
101 {D67661EB-2423-451D-BF5D-13199E37DF28} 0 80244019 SelfUpdate Failure
Software Synchronization Windows Update Client failed to detect with error
0x80244019.
2009-06-15 03:17:30:828 1060 22f0 Report Uploading 1 events using cached
cookie, reporting URL =
http://XXXXXX:8530/ReportingWebServi...ebService.asmx
2009-06-15 03:17:30:828 1060 22f0 Report Reporter successfully uploaded 1
events.

Thanks,
Sean Shay


"Lawrence Garvin [MVP]" <> wrote in message
news:...
> "Seab" <> wrote in message
> news:...
>
>
>> My question are, other than Microsoft saying to not use wizard
>> configuration tool that pops up during the installation
>
> There's no reason NOT to use the setup wizard when installing WSUS 3 SP1
> on an SBS2003SP2 system, provided that the R2 Technologies version of WSUS
> has not previously been installed. Given your descriptions above, I don't
> think this is the case here.
>
>> nor setting synchronzation to manual,
>
> Well, setting synchronization to manual is not something I'd do for ANY
> WSUS Server, except those I was doing testing/training on.
>
>> is there anything else that I should be aware of when I reinstall WSUS
>> 3.0 SP1?
>
> There are a *LOT* of things you should be aware of before installing WSUS
> 3.0 SP1 anywhere, but particularly on Small Business Server.
>
> [1] Read the Release Notes TWICE, and verify none of those issues are
> applicable.
>
> [2] Review the Deployment Guide and make sure you understand the basics.
>
> [3] If it doesn't work as expected, after installation -- perform
> DIAGNOSTICS before changing anything. For example, in your original
> installation, you noted that neither the clients, nor the server itself,
> could communicate with the wsus services. There are several well-known
> causes and simple remediations for these causes. Post back here and ASK if
> you have any issues. (Note: Modifying the Default Domain Policy is not on
> the list of recommended remediations, or even on the list of recommended
> practices. Create a =WSUS= policy for deploying WSUS. In fact, you'll
> probably need to create three WSUS policies -- one for desktops, one for
> notebooks, and one for servers, and the server policy will need to be
> linked to two different OUs.)
>
>> If the server was called Server1 then the pointer (WUServer,
>> WUStatusServer) would be http://Server1:8530 for the machines to recieve
>> updates from
>
> Correct.
>
>> if I'm having Server1's D drive act as the repository for the approved
>> update?
>
> Where the update repository is, has absolutely nothing to do with the URL
> for WUServer and WUStatusServer. The value would be http://Server1:8530
> for SBS2003 under ANY conditions.
>
>
> --
> 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
>

"Sean" <> wrote in message
news:%...
> Good early morning,
> The server and two out of the eight clients (most client machines
> hibernate) have show up in the Update Services admin console since the
> reinstall, but that still have not upated their status.

Given that clients are hibernating, and we're coming off of a weekend, this
is not unexpected. In general it may take up to 24 hours before clients will
appear in the WSUS Admin Console -- assuming they have a policy properly
applied.

> I found three areas (Default Domain Policy, Small Business Server Client
> Computer, & Small Business Server Windows Firewall), in which Update
> Services was configured ,for all authenticated users, of which I was
> unaware.

> After installing WSUS 3.0 SP1, I found and changed those policies that
> dealt with Windows Updates to not configured.

Neither the Default Domain Policy, nor the SBS Windows Firewall policy
should have any configurations for the WindowsUpdate policy! The SBS Client
Computer policy is where the R2 Technologies installation of WSUS3
configured a policy, and this could be an artifact of having previously
installed WSUS2 from the R2 Technologies.

Note also that changing a policy back to NOT CONFIGURED, will not UNDO
anything previously applied by that policy. A policy of this type forces a
registry value to be set. Reverting the policy back to Not Configured simply
ends the forcing of the value at system startup and policy refresh, but if
the registry has already been configured -- it will continue to function
with the previously set values (which may not be what you actually want).

As particularly relates to an SBS2003, you need a policy linked to the
Domain Controllers OU. I'd venture a guess that the previous policy
configured in the Default Domain Policy is what was getting the SBS2003
client configured. If you've taken that away, you'll need to configure a new
policy and link it to the Domain Controllers OU.

> I have two Update Services policies, one holding the server and another
> holding the client machines. The server SUS GPO, client diagostic readout,
> and windows update.log (~3am gpudate /force, ~3:15am wuauclt.exe
> /detectnow) are listed as follows:
>
> Allow non-administrators to recieve update notifications: Enabled
> Configure Automatic Updates: Enabled
> Configure automatic updating: 4 - Auto download and schedule the
> install
> The following settings are only required and applicable if 4 is
> selected
> Scheduled install day 0 - Every day
> Scheudled install time: 03:00

You probably do not want to configure *servers* to automatically installed
updates and reboot. The common practice for servers is to use AUOption #3,
and to install updates interactively at a time when it is convenient to
reboot the server.

> 2009-06-15 03:00:10:000 1060 664 AU #############
> 2009-06-15 03:00:10:000 1060 664 AU ## START ## AU: Install updates
> 2009-06-15 03:00:10:000 1060 664 AU #########
> 2009-06-15 03:00:10:000 1060 664 AU # Initiating scheduled install
> 2009-06-15 03:00:10:000 1060 664 AU # Approved updates = 1
> 2009-06-15 03:00:10:109 1060 664 AU <<## SUBMITTED ## AU: Install updates
> / installing updates [CallId = {DA0A5E5A-3119-4296-B1FD-4838071A2258}]
> 2009-06-15 03:00:10:109 1060 2090 Agent *************
> 2009-06-15 03:00:10:109 1060 2090 Agent ** START ** Agent: Installing
> updates [CallerId = AutomaticUpdates]
> 2009-06-15 03:00:10:109 1060 2090 Agent *********
> 2009-06-15 03:00:10:109 1060 2090 Agent * Updates to install = 1
> 2009-06-15 03:00:10:109 7184 2334 CltUI AU client got new directive =
> 'Shutdown', serviceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, return =
> 0x00000000
> 2009-06-15 03:00:10:187 1060 2090 Agent WARNING: fail to get update
> deployments with error 0x80248007
> 2009-06-15 03:00:10:187 1060 2090 Agent * Title = Update for Windows
> Server Update Services (WSUS) 3 Service Pack 1 (KB954960)
> 2009-06-15 03:00:10:187 1060 2090 Agent * UpdateId =
> {9772AEDE-91AB-499A-B1E7-00D357DEAE89}.100
> 2009-06-15 03:00:10:187 1060 2090 Agent * Bundles 1 updates:
> 2009-06-15 03:00:10:187 1060 2090 Agent *
> {2C34B6C0-8AA6-406A-9EF9-69D8D0CAC5D3}.100
> 2009-06-15 03:00:10:281 1060 2090 Agent *********
> 2009-06-15 03:00:10:281 1060 1a54 AU >>## RESUMED ## AU: Installing
> update [UpdateId = {9772AEDE-91AB-499A-B1E7-00D357DEAE89}]
> 2009-06-15 03:00:10:281 1060 2090 Agent ** END ** Agent: Installing
> updates [CallerId = AutomaticUpdates]
> 2009-06-15 03:00:10:281 1060 1a54 AU # WARNING: Install failed, error =
> 0x80240017 / 0x00000000
> 2009-06-15 03:00:10:281 1060 2090 Agent *************
> 2009-06-15 03:00:10:281 1060 1a54 AU Install call completed.
> 2009-06-15 03:00:10:281 1060 1a54 AU # WARNING: Install call completed,
> reboot required = No, error = 0x00000000
> 2009-06-15 03:00:10:281 1060 1a54 AU #########
> 2009-06-15 03:00:10:281 1060 1a54 AU ## END ## AU: Installing updates
> [CallId = {DA0A5E5A-3119-4296-B1FD-4838071A2258}]
> 2009-06-15 03:00:10:281 1060 1a54 AU #############

Interesting errors.

0x80240007 WU_E_INVALIDINDEX The index to a collection was invalid.
0x80248007 WU_E_DS_NODATA The information requested is not in the data
store.


> 2009-06-15 03:00:10:437 1060 22f0 Agent * Found 0 updates and 0
> categories in search; evaluated appl. rules of 0 out of 0 deployed
> entities

This is not normal, either! Unless, of course, you're not actually
synchronizing Win2003 or SBS2003 updates to your WSUS Server and there
actually aren't any updates on the server. This would also possibly explain
the above unusual installation error.


> 2009-06-15 03:01:05:015 1060 22f0 PT Server URL =
> http://XXXXXX:8530/SimpleAuthWebService/SimpleAuth.asmx
> 2009-06-15 03:01:05:828 1060 22f0 PT WARNING: GetCookie failure, error =
> 0x8024400D, soap client error = 7, soap error code = 300, HTTP status code
> = 200
> 2009-06-15 03:01:05:828 1060 22f0 PT WARNING: SOAP Fault: 0x00012c
> 2009-06-15 03:01:05:828 1060 22f0 PT WARNING:
> faultstring:System.Web.Services.Protocols.SoapExce ption: Fault occurred
> at
> Microsoft.UpdateServices.Internal.SoapUtilities.Th rowException(ErrorCode
> errorCode, String message, String[] clientIds)
> at
> Microsoft.UpdateServices.Internal.ClientImplementa tion.GetCookie(AuthorizationCookie[]
> authCookies, Cookie oldCookie, DateTime lastChange, DateTime
> currentClientTime, String protocolVersion)
> at
> Microsoft.UpdateServices.Internal.Client.GetCookie (AuthorizationCookie[]
> authCookies, Cookie oldCookie, DateTime lastChange, DateTime currentTime,
> String protocolVersion)
> 2009-06-15 03:01:05:828 1060 22f0 PT WARNING:
> ErrorCode:ConfigChanged(2)
> 2009-06-15 03:01:05:828 1060 22f0 PT WARNING: Messagenull)
> 2009-06-15 03:01:05:828 1060 22f0 PT WARNING:
> Method:"http://www.microsoft.com/SoftwareDistribution/Server/ClientWebService/GetCookie"
> 2009-06-15 03:01:05:828 1060 22f0 PT WARNING:
> ID:4716ea43-40a6-430c-9ed3-d222f9e99ec2
> 2009-06-15 03:01:05:859 1060 22f0 PT WARNING: Cached cookie has expired or
> new PID is available

> 2009-06-15 03:15:01:343 1060 22f0 Misc Validating signature for
> C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default \wuident.cab:
> 2009-06-15 03:15:01:359 1060 22f0 Misc Microsoft signed: Yes
> 2009-06-15 03:15:01:359 1060 22f0 Misc WARNING: WinHttp:
> SendRequestToServerForFileInformation failed with 0x80190194
> 2009-06-15 03:15:01:359 1060 22f0 Misc WARNING: WinHttp:
> ShouldFileBeDownloaded failed with 0x80190194
> 2009-06-15 03:15:01:359 1060 22f0 Misc WARNING: DownloadFileInternal
> failed for http://XXXXXX:8530/selfupdate/wuident.cab: error 0x80190194

This is an HTTP 404 error trying to find the selfupdate folder on your
server... suggesting that the virtual directory is not there. This is a
known issue after installing the WSUS3SP1 installer, particularly in an
upgrade scenario (or something the installer thinks is an upgrade scenario).

That could also account for the other errors, as well.


--
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

Good morning,

> You probably do not want to configure *servers* to automatically installed
> updates and reboot. The common practice for servers is to use AUOption #3,
> and to install updates interactively at a time when it is convenient to
> reboot the server.

Okay, in our 'Small Business Server Update Services Server Computer Policy'
(that applies to our server) changed it to option #3

> > I found three areas (Default Domain Policy, Small Business Server Client
> > Computer, & Small Business Server Windows Firewall), in which Update
> > Services was configured ,for all authenticated users, of which I was
> > unaware.
> > After installing WSUS 3.0 SP1, I found and changed those policies that
> > dealt with Windows Updates to not configured.
>
> Neither the Default Domain Policy, nor the SBS Windows Firewall policy
> should have any configurations for the WindowsUpdate policy! The SBS
Client
> Computer policy is where the R2 Technologies installation of WSUS3
> configured a policy, and this could be an artifact of having previously
> installed WSUS2 from the R2 Technologies.
>
> Note also that changing a policy back to NOT CONFIGURED, will not UNDO
> anything previously applied by that policy. A policy of this type forces a
> registry value to be set. Reverting the policy back to Not Configured
simply
> ends the forcing of the value at system startup and policy refresh, but if
> the registry has already been configured -- it will continue to function
> with the previously set values (which may not be what you actually want).

I went through the Small Business Server Update Services Server Computer
Policy, Windows Components/Windows Update and changed the options to either
Disabled or Enabled (if the setting was on not configured). Would this go
through the registry and overwrite or reaffirm all the choices that were
affected by the previous three policies that affected Windows Updates
(Default Domain Policy, Small Business Server Client Computer, & Small
Business Server Windows Firewall)?

> > ShouldFileBeDownloaded failed with 0x80190194
> > 2009-06-15 03:15:01:359 1060 22f0 Misc WARNING: DownloadFileInternal
> > failed for http://XXXXXX:8530/selfupdate/wuident.cab: error 0x80190194
>
> This is an HTTP 404 error trying to find the selfupdate folder on your
> server... suggesting that the virtual directory is not there. This is a
> known issue after installing the WSUS3SP1 installer, particularly in an
> upgrade scenario (or something the installer thinks is an upgrade
scenario).
>
> That could also account for the other errors, as well.

We checked IIS and found that the custom WSUS Administration site that was
installed was without a Selfupdate virtual directory. We went to Default Web
Site and saved the Selfupdate folder to a configuration file then went added
a new virtual directory from that file in the WSUS Adminitration website.

Here is the WindowsUpdate.log output during and just after the changes
applied:

2009-06-16 09:23:03:812 1060 664 AU AU received policy change subscription
event
2009-06-16 09:27:38:562 1060 664 AU AU received policy change subscription
event
2009-06-16 09:40:40:843 1060 1894 AU Triggering AU detection through
DetectNow API
2009-06-16 09:40:40:843 1060 1894 AU Triggering Online detection
(non-interactive)
2009-06-16 09:40:40:859 1060 664 AU #############
2009-06-16 09:40:40:859 1060 664 AU ## START ## AU: Search for updates
2009-06-16 09:40:40:859 1060 664 AU #########
2009-06-16 09:40:40:859 1060 664 AU <<## SUBMITTED ## AU: Search for updates
[CallId = {4FB49CE5-3E07-4931-AE1E-A3F661BBD1A3}]
2009-06-16 09:40:40:859 1060 1ed4 Agent *************
2009-06-16 09:40:40:859 1060 1ed4 Agent ** START ** Agent: Finding updates
[CallerId = AutomaticUpdates]
2009-06-16 09:40:40:859 1060 1ed4 Agent *********
2009-06-16 09:40:40:859 1060 1ed4 Agent * Online = Yes; Ignore download
priority = No
2009-06-16 09:40:40:859 1060 1ed4 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-16 09:40:40:859 1060 1ed4 Agent * ServiceID =
{3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}
2009-06-16 09:40:40:859 1060 1ed4 Agent * Search Scope = {Machine}
2009-06-16 09:40:40:875 1060 1ed4 Misc Validating signature for
C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default \wuident.cab:
2009-06-16 09:40:40:890 1060 1ed4 Misc Microsoft signed: Yes
2009-06-16 09:40:40:921 1060 1ed4 Misc Validating signature for
C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default \wuident.cab:
2009-06-16 09:40:40:937 1060 1ed4 Misc Microsoft signed: Yes
2009-06-16 09:40:41:109 1060 1ed4 Misc Validating signature for
C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default \wsus3setup.cab:
2009-06-16 09:40:41:109 1060 1ed4 Misc Microsoft signed: Yes
2009-06-16 09:40:41:125 1060 1ed4 Setup *********** Setup: Checking whether
self-update is required ***********
2009-06-16 09:40:41:125 1060 1ed4 Setup * Inf file:
C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default \wsus3setup.inf
2009-06-16 09:40:41:187 1060 1ed4 Setup Update NOT required for
C:\WINDOWS\system32\cdm.dll: target version = 7.2.6001.788, required version
= 7.1.6001.65
2009-06-16 09:40:41:234 1060 1ed4 Setup Update NOT required for
C:\WINDOWS\system32\wuapi.dll: target version = 7.2.6001.788, required
version = 7.1.6001.65
2009-06-16 09:40:41:265 1060 1ed4 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-16 09:40:41:265 1060 1ed4 Setup Update NOT required for
C:\WINDOWS\system32\wuauclt.exe: target version = 7.2.6001.788, required
version = 7.1.6001.65
2009-06-16 09:40:41:296 1060 1ed4 Setup Update NOT required for
C:\WINDOWS\system32\wuaucpl.cpl: target version = 7.2.6001.788, required
version = 7.1.6001.65
2009-06-16 09:40:41:328 1060 1ed4 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-16 09:40:41:375 1060 1ed4 Setup Update NOT required for
C:\WINDOWS\system32\wuaueng.dll: target version = 7.2.6001.788, required
version = 7.1.6001.65
2009-06-16 09:40:41:453 1060 1ed4 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-16 09:40:41:484 1060 1ed4 Setup Update NOT required for
C:\WINDOWS\system32\wucltui.dll: target version = 7.2.6001.788, required
version = 7.1.6001.65
2009-06-16 09:40:41:500 1060 1ed4 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-16 09:40:41:500 1060 1ed4 Setup Update NOT required for
C:\WINDOWS\system32\wups.dll: target version = 7.2.6001.788, required
version = 7.1.6001.65
2009-06-16 09:40:41:500 1060 1ed4 Setup Update NOT required for
C:\WINDOWS\system32\wups2.dll: target version = 7.2.6001.788, required
version = 7.1.6001.65
2009-06-16 09:40:41:546 1060 1ed4 Setup Update NOT required for
C:\WINDOWS\system32\wuweb.dll: target version = 7.2.6001.788, required
version = 7.1.6001.65
2009-06-16 09:40:41:546 1060 1ed4 Setup * IsUpdateRequired = No
2009-06-16 09:40:42:093 1060 1ed4 PT +++++++++++ PT: Synchronizing server
updates +++++++++++
2009-06-16 09:40:42:093 1060 1ed4 PT + ServiceId =
{3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL =
http://XXXXXX:8530/ClientWebService/client.asmx
2009-06-16 09:43:42:437 1060 1ed4 PT WARNING: Exceeded max server round
trips: 0x80244010
2009-06-16 09:43:42:453 1060 1ed4 PT WARNING: Sync of Updates: 0x80244010
2009-06-16 09:43:42:453 1060 1ed4 PT WARNING: SyncServerUpdatesInternal
failed: 0x80244010
2009-06-16 09:43:42:484 1060 1ed4 Agent * WARNING: Failed to synchronize,
error = 0x80244010
2009-06-16 09:43:42:640 1060 1ed4 Agent * WARNING: Exit code = 0x80244010
2009-06-16 09:43:42:640 1060 1ed4 Agent *********
2009-06-16 09:43:42:640 1060 1ed4 Agent ** END ** Agent: Finding updates
[CallerId = AutomaticUpdates]
2009-06-16 09:43:42:640 1060 1ed4 Agent *************
2009-06-16 09:43:42:640 1060 1ed4 Agent WARNING: WU client failed Searching
for update with error 0x80244010
2009-06-16 09:43:42:640 1060 1484 AU >>## RESUMED ## AU: Search for
updates [CallId = {4FB49CE5-3E07-4931-AE1E-A3F661BBD1A3}]
2009-06-16 09:43:42:640 1060 1484 AU # WARNING: Search callback failed,
result = 0x80244010
2009-06-16 09:43:42:640 1060 1484 AU # WARNING: Failed to find updates
with error code 80244010
2009-06-16 09:43:42:640 1060 1484 AU #########
2009-06-16 09:43:42:640 1060 1484 AU ## END ## AU: Search for updates
[CallId = {4FB49CE5-3E07-4931-AE1E-A3F661BBD1A3}]
2009-06-16 09:43:42:640 1060 1484 AU #############
2009-06-16 09:43:42:656 1060 1484 AU AU setting next detection timeout to
2009-06-16 21:43:42
2009-06-16 09:43:47:671 1060 1ed4 Report REPORT EVENT:
{BA1BFE9B-9493-4634-98E2-A7C2A3DB40F4} 2009-06-16 09:43:42:640-0700 1 148
101 {00000000-0000-0000-0000-000000000000} 0 80244010 AutomaticUpdates
Failure Software Synchronization Windows Update Client failed to detect with
error 0x80244010.
2009-06-16 09:46:11:984 1060 1ed4 Report Uploading 1 events using cached
cookie, reporting URL =
http://XXXXXX:8530/ReportingWebServi...ebService.asmx
2009-06-16 09:46:12:015 1060 1ed4 Report Reporter successfully uploaded 1
events.

Any idea on the cause for the errors?

> As particularly relates to an SBS2003, you need a policy linked to the
> Domain Controllers OU. I'd venture a guess that the previous policy
> configured in the Default Domain Policy is what was getting the SBS2003
> client configured. If you've taken that away, you'll need to configure a
new
> policy and link it to the Domain Controllers OU.

I linked the existing "Small Business Server Update Services Server Computer
Policy" to the Domain Controllers OU. Now the GPO is linked to OurSite.local
and Domain Controllers. Is that alright to do?

Tremendous thanks for your help so far,
Sean Shay

Seems like its working. The server reported its status in the WSUS console
and the WindowsUpdate.log isn't generating any errros. It would seem that
the error may have been caused by exceeding the number of 'trips' to the
WSUS server to check for the updates it needs on the initial try.

Now to get the client machines GPO adjusted.

If you have any other suggestions, please let me know.

Thanks for your help,
Sean Shay

"Sean" <> wrote in message
news:...
> Good morning,
>
> > You probably do not want to configure *servers* to automatically
installed
> > updates and reboot. The common practice for servers is to use AUOption
#3,
> > and to install updates interactively at a time when it is convenient to
> > reboot the server.
>
> Okay, in our 'Small Business Server Update Services Server Computer
Policy'
> (that applies to our server) changed it to option #3
>
> > > I found three areas (Default Domain Policy, Small Business Server
Client
> > > Computer, & Small Business Server Windows Firewall), in which Update
> > > Services was configured ,for all authenticated users, of which I was
> > > unaware.
> > > After installing WSUS 3.0 SP1, I found and changed those policies that
> > > dealt with Windows Updates to not configured.
> >
> > Neither the Default Domain Policy, nor the SBS Windows Firewall policy
> > should have any configurations for the WindowsUpdate policy! The SBS
> Client
> > Computer policy is where the R2 Technologies installation of WSUS3
> > configured a policy, and this could be an artifact of having previously
> > installed WSUS2 from the R2 Technologies.
> >
> > Note also that changing a policy back to NOT CONFIGURED, will not UNDO
> > anything previously applied by that policy. A policy of this type forces
a
> > registry value to be set. Reverting the policy back to Not Configured
> simply
> > ends the forcing of the value at system startup and policy refresh, but
if
> > the registry has already been configured -- it will continue to function
> > with the previously set values (which may not be what you actually
want).
>
> I went through the Small Business Server Update Services Server Computer
> Policy, Windows Components/Windows Update and changed the options to
either
> Disabled or Enabled (if the setting was on not configured). Would this go
> through the registry and overwrite or reaffirm all the choices that were
> affected by the previous three policies that affected Windows Updates
> (Default Domain Policy, Small Business Server Client Computer, & Small
> Business Server Windows Firewall)?
>
> > > ShouldFileBeDownloaded failed with 0x80190194
> > > 2009-06-15 03:15:01:359 1060 22f0 Misc WARNING: DownloadFileInternal
> > > failed for http://XXXXXX:8530/selfupdate/wuident.cab: error 0x80190194
> >
> > This is an HTTP 404 error trying to find the selfupdate folder on your
> > server... suggesting that the virtual directory is not there. This is a
> > known issue after installing the WSUS3SP1 installer, particularly in an
> > upgrade scenario (or something the installer thinks is an upgrade
> scenario).
> >
> > That could also account for the other errors, as well.
>
> We checked IIS and found that the custom WSUS Administration site that was
> installed was without a Selfupdate virtual directory. We went to Default
Web
> Site and saved the Selfupdate folder to a configuration file then went
added
> a new virtual directory from that file in the WSUS Adminitration website.
>
> Here is the WindowsUpdate.log output during and just after the changes
> applied:
>
> 2009-06-16 09:23:03:812 1060 664 AU AU received policy change subscription
> event
> 2009-06-16 09:27:38:562 1060 664 AU AU received policy change subscription
> event
> 2009-06-16 09:40:40:843 1060 1894 AU Triggering AU detection through
> DetectNow API
> 2009-06-16 09:40:40:843 1060 1894 AU Triggering Online detection
> (non-interactive)
> 2009-06-16 09:40:40:859 1060 664 AU #############
> 2009-06-16 09:40:40:859 1060 664 AU ## START ## AU: Search for updates
> 2009-06-16 09:40:40:859 1060 664 AU #########
> 2009-06-16 09:40:40:859 1060 664 AU <<## SUBMITTED ## AU: Search for
updates
> [CallId = {4FB49CE5-3E07-4931-AE1E-A3F661BBD1A3}]
> 2009-06-16 09:40:40:859 1060 1ed4 Agent *************
> 2009-06-16 09:40:40:859 1060 1ed4 Agent ** START ** Agent: Finding
updates
> [CallerId = AutomaticUpdates]
> 2009-06-16 09:40:40:859 1060 1ed4 Agent *********
> 2009-06-16 09:40:40:859 1060 1ed4 Agent * Online = Yes; Ignore download
> priority = No
> 2009-06-16 09:40:40:859 1060 1ed4 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-16 09:40:40:859 1060 1ed4 Agent * ServiceID =
> {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}
> 2009-06-16 09:40:40:859 1060 1ed4 Agent * Search Scope = {Machine}
> 2009-06-16 09:40:40:875 1060 1ed4 Misc Validating signature for
> C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default \wuident.cab:
> 2009-06-16 09:40:40:890 1060 1ed4 Misc Microsoft signed: Yes
> 2009-06-16 09:40:40:921 1060 1ed4 Misc Validating signature for
> C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default \wuident.cab:
> 2009-06-16 09:40:40:937 1060 1ed4 Misc Microsoft signed: Yes
> 2009-06-16 09:40:41:109 1060 1ed4 Misc Validating signature for
> C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default \wsus3setup.cab:
> 2009-06-16 09:40:41:109 1060 1ed4 Misc Microsoft signed: Yes
> 2009-06-16 09:40:41:125 1060 1ed4 Setup *********** Setup: Checking
whether
> self-update is required ***********
> 2009-06-16 09:40:41:125 1060 1ed4 Setup * Inf file:
> C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default \wsus3setup.inf
> 2009-06-16 09:40:41:187 1060 1ed4 Setup Update NOT required for
> C:\WINDOWS\system32\cdm.dll: target version = 7.2.6001.788, required
version
> = 7.1.6001.65
> 2009-06-16 09:40:41:234 1060 1ed4 Setup Update NOT required for
> C:\WINDOWS\system32\wuapi.dll: target version = 7.2.6001.788, required
> version = 7.1.6001.65
> 2009-06-16 09:40:41:265 1060 1ed4 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-16 09:40:41:265 1060 1ed4 Setup Update NOT required for
> C:\WINDOWS\system32\wuauclt.exe: target version = 7.2.6001.788, required
> version = 7.1.6001.65
> 2009-06-16 09:40:41:296 1060 1ed4 Setup Update NOT required for
> C:\WINDOWS\system32\wuaucpl.cpl: target version = 7.2.6001.788, required
> version = 7.1.6001.65
> 2009-06-16 09:40:41:328 1060 1ed4 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-16 09:40:41:375 1060 1ed4 Setup Update NOT required for
> C:\WINDOWS\system32\wuaueng.dll: target version = 7.2.6001.788, required
> version = 7.1.6001.65
> 2009-06-16 09:40:41:453 1060 1ed4 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-16 09:40:41:484 1060 1ed4 Setup Update NOT required for
> C:\WINDOWS\system32\wucltui.dll: target version = 7.2.6001.788, required
> version = 7.1.6001.65
> 2009-06-16 09:40:41:500 1060 1ed4 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-16 09:40:41:500 1060 1ed4 Setup Update NOT required for
> C:\WINDOWS\system32\wups.dll: target version = 7.2.6001.788, required
> version = 7.1.6001.65
> 2009-06-16 09:40:41:500 1060 1ed4 Setup Update NOT required for
> C:\WINDOWS\system32\wups2.dll: target version = 7.2.6001.788, required
> version = 7.1.6001.65
> 2009-06-16 09:40:41:546 1060 1ed4 Setup Update NOT required for
> C:\WINDOWS\system32\wuweb.dll: target version = 7.2.6001.788, required
> version = 7.1.6001.65
> 2009-06-16 09:40:41:546 1060 1ed4 Setup * IsUpdateRequired = No
> 2009-06-16 09:40:42:093 1060 1ed4 PT +++++++++++ PT: Synchronizing server
> updates +++++++++++
> 2009-06-16 09:40:42:093 1060 1ed4 PT + ServiceId =
> {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL =
> http://XXXXXX:8530/ClientWebService/client.asmx
> 2009-06-16 09:43:42:437 1060 1ed4 PT WARNING: Exceeded max server round
> trips: 0x80244010
> 2009-06-16 09:43:42:453 1060 1ed4 PT WARNING: Sync of Updates: 0x80244010
> 2009-06-16 09:43:42:453 1060 1ed4 PT WARNING: SyncServerUpdatesInternal
> failed: 0x80244010
> 2009-06-16 09:43:42:484 1060 1ed4 Agent * WARNING: Failed to
synchronize,
> error = 0x80244010
> 2009-06-16 09:43:42:640 1060 1ed4 Agent * WARNING: Exit code =
0x80244010
> 2009-06-16 09:43:42:640 1060 1ed4 Agent *********
> 2009-06-16 09:43:42:640 1060 1ed4 Agent ** END ** Agent: Finding
updates
> [CallerId = AutomaticUpdates]
> 2009-06-16 09:43:42:640 1060 1ed4 Agent *************
> 2009-06-16 09:43:42:640 1060 1ed4 Agent WARNING: WU client failed
Searching
> for update with error 0x80244010
> 2009-06-16 09:43:42:640 1060 1484 AU >>## RESUMED ## AU: Search for
> updates [CallId = {4FB49CE5-3E07-4931-AE1E-A3F661BBD1A3}]
> 2009-06-16 09:43:42:640 1060 1484 AU # WARNING: Search callback failed,
> result = 0x80244010
> 2009-06-16 09:43:42:640 1060 1484 AU # WARNING: Failed to find updates
> with error code 80244010
> 2009-06-16 09:43:42:640 1060 1484 AU #########
> 2009-06-16 09:43:42:640 1060 1484 AU ## END ## AU: Search for updates
> [CallId = {4FB49CE5-3E07-4931-AE1E-A3F661BBD1A3}]
> 2009-06-16 09:43:42:640 1060 1484 AU #############
> 2009-06-16 09:43:42:656 1060 1484 AU AU setting next detection timeout to
> 2009-06-16 21:43:42
> 2009-06-16 09:43:47:671 1060 1ed4 Report REPORT EVENT:
> {BA1BFE9B-9493-4634-98E2-A7C2A3DB40F4} 2009-06-16 09:43:42:640-0700 1 148
> 101 {00000000-0000-0000-0000-000000000000} 0 80244010 AutomaticUpdates
> Failure Software Synchronization Windows Update Client failed to detect
with
> error 0x80244010.
> 2009-06-16 09:46:11:984 1060 1ed4 Report Uploading 1 events using cached
> cookie, reporting URL =
> http://XXXXXX:8530/ReportingWebServi...ebService.asmx
> 2009-06-16 09:46:12:015 1060 1ed4 Report Reporter successfully uploaded 1
> events.
>
> Any idea on the cause for the errors?
>
> > As particularly relates to an SBS2003, you need a policy linked to the
> > Domain Controllers OU. I'd venture a guess that the previous policy
> > configured in the Default Domain Policy is what was getting the SBS2003
> > client configured. If you've taken that away, you'll need to configure a
> new
> > policy and link it to the Domain Controllers OU.
>
> I linked the existing "Small Business Server Update Services Server
Computer
> Policy" to the Domain Controllers OU. Now the GPO is linked to
OurSite.local
> and Domain Controllers. Is that alright to do?
>
> Tremendous thanks for your help so far,
> Sean Shay
>
>

"Sean" <> wrote in message
news:...


>> Note also that changing a policy back to NOT CONFIGURED, will not UNDO
>> anything previously applied by that policy. A policy of this type forces
>> a
>> registry value to be set. Reverting the policy back to Not Configured
>> simply ends the forcing of the value at system startup and policy
>> refresh,
>> but if the registry has already been configured -- it will continue to
>> function
>> with the previously set values (which may not be what you actually want).

> I went through the Small Business Server Update Services Server Computer
> Policy, Windows Components/Windows Update and changed the options to
> either
> Disabled or Enabled (if the setting was on not configured). Would this go
> through the registry and overwrite or reaffirm all the choices that were
> affected by the previous three policies that affected Windows Updates
> (Default Domain Policy, Small Business Server Client Computer, & Small
> Business Server Windows Firewall)?

Yes.


--
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

"Sean" <> wrote in message
news:...


>> > ShouldFileBeDownloaded failed with 0x80190194
>> > 2009-06-15 03:15:01:359 1060 22f0 Misc WARNING: DownloadFileInternal
>> > failed for http://XXXXXX:8530/selfupdate/wuident.cab: error 0x80190194

>> This is an HTTP 404 error trying to find the selfupdate folder on your
>> server... suggesting that the virtual directory is not there. This is a
>> known issue after installing the WSUS3SP1 installer, particularly in an
>> upgrade scenario (or something the installer thinks is an upgrade
>> scenario).
>>
>> That could also account for the other errors, as well.

> We checked IIS and found that the custom WSUS Administration site that was
> installed was without a Selfupdate virtual directory. We went to Default
> Web
> Site and saved the Selfupdate folder to a configuration file then went
> added
> a new virtual directory from that file in the WSUS Adminitration website.
>
> Here is the WindowsUpdate.log output during and just after the changes
> applied:

I'm a bit confused about the reference to "during and just after the
changes"... the following log snippet basically covers one event from
9:40:40 to 9:46:12. If the creation of the missing selfupdate occurred
*during* that time frame, then these results are inconclusive, and probably
aberrant.

If the creation of the missing v-dir occurred *before* 9:40:40, then we have
a whole new issue. (I'm also assuming that the policy changes that occurred
at 9:23 and 9:27 are a result of the previously noted policy corrections).

> 2009-06-16 09:43:47:671 1060 1ed4 Report REPORT EVENT:
> {BA1BFE9B-9493-4634-98E2-A7C2A3DB40F4} 2009-06-16 09:43:42:640-0700 1 148
> 101 {00000000-0000-0000-0000-000000000000} 0 80244010 AutomaticUpdates
> Failure Software Synchronization Windows Update Client failed to detect
> with
> error 0x80244010.

> 2009-06-16 09:46:11:984 1060 1ed4 Report Uploading 1 events using cached
> cookie, reporting URL =
> http://XXXXXX:8530/ReportingWebServi...ebService.asmx
> 2009-06-16 09:46:12:015 1060 1ed4 Report Reporter successfully uploaded 1
> events.

> Any idea on the cause for the errors?

Not directly, but I'm inclined to think "working on the server" could be a
contributing cause. What were the results of this client's next scheduled
detection?


--
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

"Sean" <> wrote in message
news:...

>> As particularly relates to an SBS2003, you need a policy linked to the
>> Domain Controllers OU. I'd venture a guess that the previous policy
>> configured in the Default Domain Policy is what was getting the SBS2003
>> client configured. If you've taken that away, you'll need to configure a
>> new policy and link it to the Domain Controllers OU.

> I linked the existing "Small Business Server Update Services Server
> Computer
> Policy" to the Domain Controllers OU. Now the GPO is linked to
> OurSite.local
> and Domain Controllers. Is that alright to do?

It's functional, though I'd be more inclined to think you'd want to link
that policy to the =OU= containing the SERVERS and not at the DOMAIN level.

The problem you now have is that you've likely got two different policies,
both linked at the DOMAIN level, that should be linked at individual OUs
containing the computers of that specified type (SERVERS, WORKSTATIONS).

Also, given that this policy is linked at the DOMAIN level, it was being
carred to the Domain Controllers OU ... but, as noted, that's not the ideal
location for the policy link.



--
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