SCCM using WSUS

hi,

I have installed the latest version of WSUS and SCCM R2 on a W2k8 server, i
have xp clients, I have created the deployment package etc to deploy critical
updates to my pc's but for some reason the updates are not getting there

Any help to solve this issue would be appreciated
local windowsupdate.log

2009-07-30 14:44:11:312 1488 70 Misc = Process: C:\GCS\System32\svchost.exe
2009-07-30 14:44:11:312 1488 70 Misc = Module: C:\GCS\system32\wuaueng.dll
2009-07-30 14:44:11:203 1488 70 Service *************
2009-07-30 14:44:11:312 1488 70 Service ** START ** Service: Service startup
2009-07-30 14:44:11:312 1488 70 Service *********
2009-07-30 14:44:11:828 1488 70 Agent * WU client version 7.1.6001.65
2009-07-30 14:44:11:828 1488 70 Agent * Base directory:
C:\GCS\SoftwareDistribution
2009-07-30 14:44:11:828 1488 70 Agent * Access type: No proxy
2009-07-30 14:44:11:828 1488 70 Agent * Network state: Connected
2009-07-30 14:44:56:500 1488 70 Agent *********** Agent: Initializing
Windows Update Agent ***********
2009-07-30 14:44:56:500 1488 70 Agent *********** Agent: Initializing
global settings cache ***********
2009-07-30 14:44:56:500 1488 70 Agent * WSUS server:
http://server.domain:8530
2009-07-30 14:44:56:500 1488 70 Agent * WSUS status server:
http://server.domain:8530
2009-07-30 14:44:56:500 1488 70 Agent * Target group: (Unassigned
Computers)
2009-07-30 14:44:56:500 1488 70 Agent * Windows Update access disabled: No
2009-07-30 14:44:57:702 1488 70 DnldMgr Download manager restoring 0
downloads
2009-07-30 14:44:57:717 1488 70 AU ########### AU: Initializing Automatic
Updates ###########
2009-07-30 14:44:57:717 1488 70 AU # AU is not configured yet
2009-07-30 14:44:57:717 1488 70 AU AU is not configured yet, generating
timeout to launch setup wizard
2009-07-30 14:44:57:717 1488 70 AU AU finished delayed initialization
2009-07-30 14:44:57:854 1488 70 Report *********** Report: Initializing
static reporting data ***********
2009-07-30 14:44:57:854 1488 70 Report * OS Version = 5.1.2600.2.0.65792
2009-07-30 14:44:57:885 1488 70 Report * Computer Brand = Dell Inc.
2009-07-30 14:44:57:885 1488 70 Report * Computer Model = OptiPlex 755

2009-07-30 14:44:57:885 1488 70 Report * Bios Revision = A04
2009-07-30 14:44:57:885 1488 70 Report * Bios Name = Phoenix ROM BIOS
PLUS Version 1.10 A04
2009-07-30 14:44:57:885 1488 70 Report * Bios Release Date =
2007-11-05T00:00:00
2009-07-30 14:44:57:885 1488 70 Report * Locale ID = 2057
2009-07-30 14:44:57:885 1488 70 AU AU setting pending client directive to
'Setup Wizard'
2009-07-30 14:45:12:634 1488 70 AU WARNING: AU found no suitable session to
launch client in

thanks

Phil

"Phil" <> wrote in message
news:4483BB6C-52DA-4D8C-88AE-...
> hi,
>
> I have installed the latest version of WSUS and SCCM R2 on a W2k8 server,
> i
> have xp clients, I have created the deployment package etc to deploy
> critical
> updates to my pc's but for some reason the updates are not getting there
>
>
> Any help to solve this issue would be appreciated
> local windowsupdate.log

I'd start with this point:

> 2009-07-30 14:44:57:717 1488 70 AU # AU is not configured yet

And what's with the non-standard naming of the WINDOWS folder ???

2009-07-30 14:44:11:312 1488 70 Misc = Process:
C:\GCS\System32\svchost.exe
2009-07-30 14:44:11:312 1488 70 Misc = Module: C:\GCS\system32\wuaueng.dll
2009-07-30 14:44:11:828 1488 70 Agent * Base directory:
C:\GCS\SoftwareDistribution

--
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 MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin

"Lawrence Garvin [MVP]" wrote:

> "Phil" <> wrote in message
> news:4483BB6C-52DA-4D8C-88AE-...
> > hi,
> >
> > I have installed the latest version of WSUS and SCCM R2 on a W2k8 server,
> > i
> > have xp clients, I have created the deployment package etc to deploy
> > critical
> > updates to my pc's but for some reason the updates are not getting there
> >
> >
> > Any help to solve this issue would be appreciated
> > local windowsupdate.log
>
> I'd start with this point:
>
> > 2009-07-30 14:44:57:717 1488 70 AU # AU is not configured yet
>
> And what's with the non-standard naming of the WINDOWS folder ???
>
> 2009-07-30 14:44:11:312 1488 70 Misc = Process:
> C:\GCS\System32\svchost.exe
> 2009-07-30 14:44:11:312 1488 70 Misc = Module: C:\GCS\system32\wuaueng.dll
> 2009-07-30 14:44:11:828 1488 70 Agent * Base directory:
> C:\GCS\SoftwareDistribution
>
> --
> 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 MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin
>
>
In answer i have the following applied by gpo :

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
Scheduled install time: 13:00

Policy Setting
No auto-restart for scheduled Automatic Updates installations Enabled
Specify intranet Microsoft update service location Enabled
Set the intranet update service for detecting updates: http://server:8530
Set the intranet statistics server: http://server:8530

and we always use a non-standard folder in our buisness setup.

Cheers

Phil

"phil" <> wrote in message
news:488568E4-5C2C-46CF-B545-...

>> I'd start with this point:
>>
>> > 2009-07-30 14:44:57:717 1488 70 AU # AU is not configured yet

> In answer i have the following applied by gpo :

I'd much prefer to see the *actual* export of the registry key or the
*actual* output from GPRESULT.

What you've configured in the policy is never so much significant as what is
(or is *not*, as is usually the case) actually being applied to the target
system.

In this case, the error message is a pretty strong indication that your
policy has not been applied, and the interest here is in obtaining proof
that the policy *has* been applied correctly.



>> And what's with the non-standard naming of the WINDOWS folder ???

> and we always use a non-standard folder in our buisness setup.

Please understand, then, that I'm *VERY* hesitant to get too deep into
something as significant as such a fundamental modification of the OS
installation as changing the name of the %windir% folder.


--
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 MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin