Client WSUS problem - "Launching old AU client"

Hi,

Client not connected - "Launching old AU client"

2005-06-08 09:12:39 1016 920 Misc =========== Logging initialized (build:
5.8.0.2469, tz: +0200) ===========
2005-06-08 09:12:39 1016 920 Misc = Process:
C:\WINDOWS\System32\svchost.exe
2005-06-08 09:12:39 1016 920 Misc = Module:
C:\WINDOWS\system32\wuaueng.dll
2005-06-08 09:12:39 1016 920 Service *************
2005-06-08 09:12:39 1016 920 Service ** START ** Service: Service startup
2005-06-08 09:12:39 1016 920 Service *********
2005-06-08 09:12:39 1016 920 Agent * WU client version 5.8.0.2469
2005-06-08 09:12:39 1016 920 Agent * SusClientId =
'b03bfdcd-0c4d-4483-889a-777ed6d616bd'
2005-06-08 09:12:39 1016 920 Agent * Base directory:
C:\WINDOWS\SoftwareDistribution
2005-06-08 09:12:39 1016 920 Agent * Access type: No proxy
2005-06-08 09:12:39 1016 920 Agent * Network state: Connected
2005-06-08 09:12:55 1016 57c Agent *********** Agent: Initializing Windows
Update Agent ***********
2005-06-08 09:12:55 1016 57c Agent *********** Agent: Initializing global
settings cache ***********
2005-06-08 09:12:55 1016 57c Agent * WSUS server: http://ktneo
2005-06-08 09:12:55 1016 57c Agent * WSUS status server: http://ktneo
2005-06-08 09:12:55 1016 57c Agent * Target group: (Unassigned Computers)
2005-06-08 09:12:55 1016 57c Agent * Windows Update access disabled: No
2005-06-08 09:12:56 1016 57c DnldMgr Download manager restoring 0 downloads
2005-06-08 09:12:56 1016 57c AU ########### AU: Initializing Automatic
Updates ###########
2005-06-08 09:12:56 1016 57c AU AU setting next detection timeout to
2005-06-08 07:12:56
2005-06-08 09:12:56 1016 57c AU # WSUS server: http://ktneo
2005-06-08 09:12:56 1016 57c AU # Detection frequency: 5
2005-06-08 09:12:56 1016 57c AU # Approval type: Scheduled (Policy)
2005-06-08 09:12:56 1016 57c AU # Scheduled install day/time: Every day at
3:00
2005-06-08 09:12:56 1016 57c AU # Auto-install minor updates: No (Policy)
2005-06-08 09:12:56 1016 57c AU # Launching old AU client

The "Launching old AU client" message indicates that the client thinks it's
talking to a SUS 1.0 server. Is the client correctly pointed at the new WSUS
server?

Thanks,
Yasufumi Shiraishi
SDE, Windows Server Update Services
Microsoft

This posting is provided "AS IS" with no warranties, and confers no rights.

"Leszek" <nobody@kontel.pl> wrote in message
news:d86sgi$q4p$2@nemesis.news.tpi.pl...
> Hi,
>
> Client not connected - "Launching old AU client"
>
> 2005-06-08 09:12:39 1016 920 Misc =========== Logging initialized (build:
> 5.8.0.2469, tz: +0200) ===========
> 2005-06-08 09:12:39 1016 920 Misc = Process:
> C:\WINDOWS\System32\svchost.exe
> 2005-06-08 09:12:39 1016 920 Misc = Module:
> C:\WINDOWS\system32\wuaueng.dll
> 2005-06-08 09:12:39 1016 920 Service *************
> 2005-06-08 09:12:39 1016 920 Service ** START ** Service: Service startup
> 2005-06-08 09:12:39 1016 920 Service *********
> 2005-06-08 09:12:39 1016 920 Agent * WU client version 5.8.0.2469
> 2005-06-08 09:12:39 1016 920 Agent * SusClientId =
> 'b03bfdcd-0c4d-4483-889a-777ed6d616bd'
> 2005-06-08 09:12:39 1016 920 Agent * Base directory:
> C:\WINDOWS\SoftwareDistribution
> 2005-06-08 09:12:39 1016 920 Agent * Access type: No proxy
> 2005-06-08 09:12:39 1016 920 Agent * Network state: Connected
> 2005-06-08 09:12:55 1016 57c Agent *********** Agent: Initializing
> Windows
> Update Agent ***********
> 2005-06-08 09:12:55 1016 57c Agent *********** Agent: Initializing global
> settings cache ***********
> 2005-06-08 09:12:55 1016 57c Agent * WSUS server: http://ktneo
> 2005-06-08 09:12:55 1016 57c Agent * WSUS status server: http://ktneo
> 2005-06-08 09:12:55 1016 57c Agent * Target group: (Unassigned
> Computers)
> 2005-06-08 09:12:55 1016 57c Agent * Windows Update access disabled: No
> 2005-06-08 09:12:56 1016 57c DnldMgr Download manager restoring 0
> downloads
> 2005-06-08 09:12:56 1016 57c AU ########### AU: Initializing Automatic
> Updates ###########
> 2005-06-08 09:12:56 1016 57c AU AU setting next detection timeout to
> 2005-06-08 07:12:56
> 2005-06-08 09:12:56 1016 57c AU # WSUS server: http://ktneo
> 2005-06-08 09:12:56 1016 57c AU # Detection frequency: 5
> 2005-06-08 09:12:56 1016 57c AU # Approval type: Scheduled (Policy)
> 2005-06-08 09:12:56 1016 57c AU # Scheduled install day/time: Every day
> at
> 3:00
> 2005-06-08 09:12:56 1016 57c AU # Auto-install minor updates: No
> (Policy)
> 2005-06-08 09:12:56 1016 57c AU # Launching old AU client
>
>
>

Was the WSUS Server installed on the same box as the SUS server?

If so, it may be that the WSUS Server is on port 8530, and the clients
really are talking to the SUS server still:
> 2005-06-08 09:12:55 1016 57c Agent * WSUS server: http://ktneo
> 2005-06-08 09:12:55 1016 57c Agent * WSUS status server: http://ktneo

note the lack of a port number on the URL.


"Yasufumi Shiraishi [MSFT]" <yasufs@microsoft.com> wrote in message
news:%23TUYWJGbFHA.1312@TK2MSFTNGP09.phx.gbl...
> The "Launching old AU client" message indicates that the client thinks
> it's talking to a SUS 1.0 server. Is the client correctly pointed at the
> new WSUS server?
>
> Thanks,
> Yasufumi Shiraishi
> SDE, Windows Server Update Services
> Microsoft
>
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
> "Leszek" <nobody@kontel.pl> wrote in message
> news:d86sgi$q4p$2@nemesis.news.tpi.pl...
>> Hi,
>>
>> Client not connected - "Launching old AU client"
>>
>> 2005-06-08 09:12:39 1016 920 Misc =========== Logging initialized
>> (build:
>> 5.8.0.2469, tz: +0200) ===========
>> 2005-06-08 09:12:39 1016 920 Misc = Process:
>> C:\WINDOWS\System32\svchost.exe
>> 2005-06-08 09:12:39 1016 920 Misc = Module:
>> C:\WINDOWS\system32\wuaueng.dll
>> 2005-06-08 09:12:39 1016 920 Service *************
>> 2005-06-08 09:12:39 1016 920 Service ** START ** Service: Service
>> startup
>> 2005-06-08 09:12:39 1016 920 Service *********
>> 2005-06-08 09:12:39 1016 920 Agent * WU client version 5.8.0.2469
>> 2005-06-08 09:12:39 1016 920 Agent * SusClientId =
>> 'b03bfdcd-0c4d-4483-889a-777ed6d616bd'
>> 2005-06-08 09:12:39 1016 920 Agent * Base directory:
>> C:\WINDOWS\SoftwareDistribution
>> 2005-06-08 09:12:39 1016 920 Agent * Access type: No proxy
>> 2005-06-08 09:12:39 1016 920 Agent * Network state: Connected
>> 2005-06-08 09:12:55 1016 57c Agent *********** Agent: Initializing
>> Windows
>> Update Agent ***********
>> 2005-06-08 09:12:55 1016 57c Agent *********** Agent: Initializing
>> global
>> settings cache ***********
>> 2005-06-08 09:12:55 1016 57c Agent * WSUS server: http://ktneo
>> 2005-06-08 09:12:55 1016 57c Agent * WSUS status server: http://ktneo
>> 2005-06-08 09:12:55 1016 57c Agent * Target group: (Unassigned
>> Computers)
>> 2005-06-08 09:12:55 1016 57c Agent * Windows Update access disabled: No
>> 2005-06-08 09:12:56 1016 57c DnldMgr Download manager restoring 0
>> downloads
>> 2005-06-08 09:12:56 1016 57c AU ########### AU: Initializing Automatic
>> Updates ###########
>> 2005-06-08 09:12:56 1016 57c AU AU setting next detection timeout to
>> 2005-06-08 07:12:56
>> 2005-06-08 09:12:56 1016 57c AU # WSUS server: http://ktneo
>> 2005-06-08 09:12:56 1016 57c AU # Detection frequency: 5
>> 2005-06-08 09:12:56 1016 57c AU # Approval type: Scheduled (Policy)
>> 2005-06-08 09:12:56 1016 57c AU # Scheduled install day/time: Every day
>> at
>> 3:00
>> 2005-06-08 09:12:56 1016 57c AU # Auto-install minor updates: No
>> (Policy)
>> 2005-06-08 09:12:56 1016 57c AU # Launching old AU client
>>
>>
>>
>
>

I've got this same problem on my XP SP2 machine - shows as launching old au
client.

I've got WSUS on a new server on its own IIS site so I've specified the 8530
port.

The WSUS information is all set in group policies and I have other
machines - a mix of W2K, XP SP1 and XP SP2 which are not having this issue,
so I assume the settings are correct and I have something strange on this
machine.

Any other ideas?


"Lawrence Garvin" <onsitechsolutions@news.postalias> wrote in message
news:%23B0pQqHbFHA.1456@TK2MSFTNGP15.phx.gbl...
>
> Was the WSUS Server installed on the same box as the SUS server?
>
> If so, it may be that the WSUS Server is on port 8530, and the clients
> really are talking to the SUS server still:
>> 2005-06-08 09:12:55 1016 57c Agent * WSUS server: http://ktneo
>> 2005-06-08 09:12:55 1016 57c Agent * WSUS status server: http://ktneo
>
> note the lack of a port number on the URL.
>
>
> "Yasufumi Shiraishi [MSFT]" <yasufs@microsoft.com> wrote in message
> news:%23TUYWJGbFHA.1312@TK2MSFTNGP09.phx.gbl...
>> The "Launching old AU client" message indicates that the client thinks
>> it's talking to a SUS 1.0 server. Is the client correctly pointed at the
>> new WSUS server?
>>
>> Thanks,
>> Yasufumi Shiraishi
>> SDE, Windows Server Update Services
>> Microsoft
>>

Post the %windir%\WindowsUpdate.log file for that XP SP2 machine. If all
other machines are working correctly, then there must be an issue unique to
that workstation.

Also, export and post HKLM\Software\Policies\Microsoft\Windows\WindowsUpdate
for that machine.

"ML" <lindeboy@nospam.nospam> wrote in message
news:%23pvVy$ObFHA.720@TK2MSFTNGP15.phx.gbl...
> I've got this same problem on my XP SP2 machine - shows as launching old
> au client.
>
> I've got WSUS on a new server on its own IIS site so I've specified the
> 8530 port.
>
> The WSUS information is all set in group policies and I have other
> machines - a mix of W2K, XP SP1 and XP SP2 which are not having this
> issue, so I assume the settings are correct and I have something strange
> on this machine.
>
> Any other ideas?
>
>
> "Lawrence Garvin" <onsitechsolutions@news.postalias> wrote in message
> news:%23B0pQqHbFHA.1456@TK2MSFTNGP15.phx.gbl...
>>
>> Was the WSUS Server installed on the same box as the SUS server?
>>
>> If so, it may be that the WSUS Server is on port 8530, and the clients
>> really are talking to the SUS server still:
>>> 2005-06-08 09:12:55 1016 57c Agent * WSUS server: http://ktneo
>>> 2005-06-08 09:12:55 1016 57c Agent * WSUS status server: http://ktneo
>>
>> note the lack of a port number on the URL.
>>
>>
>> "Yasufumi Shiraishi [MSFT]" <yasufs@microsoft.com> wrote in message
>> news:%23TUYWJGbFHA.1312@TK2MSFTNGP09.phx.gbl...
>>> The "Launching old AU client" message indicates that the client thinks
>>> it's talking to a SUS 1.0 server. Is the client correctly pointed at the
>>> new WSUS server?
>>>
>>> Thanks,
>>> Yasufumi Shiraishi
>>> SDE, Windows Server Update Services
>>> Microsoft
>>>
>
>

[say-yamai]

I have same trouble.
SUS has still ran "Server-A",and Installed WSUS another one "Server-B".
But,Port No. of "Server-B" is 8530. Some Client is correct connecting to "Server-B",A fiew Client can't connect to "Server-B","WindowUpdate.log" record "Launching old AU client",I seem just change client mode for SUS to WSUS . But ,I don't know how to do.
Anybody help me.

The "Launching legacy AU client" message is confirmation that the WUA is /NOT/
finding your WSUS server, and given the scenario you described, I'd expect
that is because you've left the port suffix off of the configured URL.

Be sure your URL is http://wsusservername:8530, and not the simpler
http://wsusservername (which forces the client to port 80 -- which is the
/SUS/ server.)


"say-yamai" <say-yamai.1xzd3k@DoNotSpam.com> wrote in message
news:say-yamai.1xzd3k@DoNotSpam.com...
>
> I have same trouble.
> SUS has still ran "Server-A",and Installed WSUS another one
> "Server-B".
> But,Port No. of "Server-B" is 8530. Some Client is correct connecting
> to "Server-B",A fiew Client can't connect to
> "Server-B","WindowUpdate.log" record "Launching old AU client",I seem
> just change client mode for SUS to WSUS . But ,I don't know how to do.
> Anybody help me.
>
>
> --
> say-yamai
> ------------------------------------------------------------------------
> say-yamai's Profile: http://forums.techarena.in/members/11123.htm
> View this thread: Client WSUS problem - "Launching old AU client"
> India Forum - http://forums.techarena.in
>

[say-yamai]

Thanks Lawrence Garvin

I have tried the test on port 80,but there are same scenario.
I can't understand that there are exist "find and not" client. They are some environment for WSUS.

Microsoft described as follow

"Deploying Microsoft Windows Server Update Services > Update and Configure the Automatic Updates Client Component


If you point the WSUS client to a SUS server, the WSUS client hibernates and allows the SUS client to function, complete with the old user interface. If you used SUS to deploy Windows XP with SP2, you cannot see the new Automatic Updates user interface. This is called side-by-side mode. None of the new WSUS client functionality is available in side-by-side mode. "

I think escape from Side-by-side mode,then client will find WSUS server.
Is this a wrong answer?

However, if you point the WSUS client to a valid URL that is not an Update
Services server of any type, it will still try to initiate a /SUS/ session --
and FAIL.

The "Launching legacy AU client" message is a guaranteed verification that an
updated WUA client is not finding the /WSUS/ server. I am not saying that it
/is/ finding a SUS server, only that it is /not/ finding the WSUS server.

Please download and run the Client Detection Tool from the Microsoft WSUS
website on the client you obtained the WindowsUpdate.log from. Then post the
complete output from the CDT.

Also, refer to http://wsusinfo.onsitechsolutions.com/articles/020.htm and
verify that all of the links provided can be accessed from Internet Explorer
on this same client system.


"say-yamai" <say-yamai.1y04wo@DoNotSpam.com> wrote in message
news:say-yamai.1y04wo@DoNotSpam.com...
>
> Thanks Lawrence Garvin
>
> I have tried the test on port 80,but there are same scenario.
> I can't understand that there are exist "find and not" client. They are
> some environment for WSUS.
>
> Microsoft described as follow
>
> "Deploying Microsoft Windows Server Update Services > Update and
> Configure the Automatic Updates Client Component
>
>
> If you point the WSUS client to a SUS server, the WSUS client
> hibernates and allows the SUS client to function, complete with the old
> user interface. If you used SUS to deploy Windows XP with SP2, you
> cannot see the new Automatic Updates user interface. This is called
> side-by-side mode. None of the new WSUS client functionality is
> available in side-by-side mode. "
>
> I think escape from Side-by-side mode,then client will find WSUS
> server.
> Is this a wrong answer?
>
>
> --
> say-yamai
> ------------------------------------------------------------------------
> say-yamai's Profile: http://forums.techarena.in/members/11123.htm
> View this thread: Client WSUS problem - "Launching old AU client"
> India Forum - http://forums.techarena.in
>

[say-yamai]

Thanks ,Lawrence Garvin

I have tried CDT,and compare result between Correct Client and not Correct Client.
There is no difference.
Then, I checked regist keys Correct Client and not Correct Client.
I found different keys
It's "[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update]".

I deleted that regist keys on bad Client,and installed regist keys by Correct Client's regist keys.

So,Feel is Good . Client found WSUS Server!!!

Interesting...!!!

Could you document /exactly/ which values you removed from the registry key
HKLM\Software\Microsoft\Windows\CurrentVersion\WindowsUpdate\AutoUpdate ???

Also, /exactly/ which keys did you "install" on the bad client that were
present on the good client?

"say-yamai" <say-yamai.1y6b4i@DoNotSpam.com> wrote in message
news:say-yamai.1y6b4i@DoNotSpam.com...
>
> Thanks ,Lawrence Garvin
>
> I have tried CDT,and compare result between Correct Client and not
> Correct Client.
> There is no difference.
> Then, I checked regist keys Correct Client and not Correct Client.
> I found different keys
> It's
> "[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto
> Update]".
>
> I deleted that regist keys on bad Client,and installed regist keys by
> Correct Client's regist keys.
>
> So,Feel is Good . Client found WSUS Server!!!
>
>
> --
> say-yamai
> ------------------------------------------------------------------------
> say-yamai's Profile: http://forums.techarena.in/members/11123.htm
> View this thread: Client WSUS problem - "Launching old AU client"
> India Forum - http://forums.techarena.in
>

[say-yamai]

Removed registKey setting as follow
----------------------------------------
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update]
"AUOptions"=dword:00000001
"SusServerVersion"=dword:00000001
"NextDetectionTime"="2005-11-09 00:52:43"
"OfflineDetectionPending"=dword:00000001
"ConfigVer"=dword:00000001
"AUState"=dword:00000002
"DetectionStartTime"="2005.11.09 09:36:03"
"LastWaitTimeout"="2005.11.09 05:47:04"
-------------------------------------------
I had removed "Auto Update" ,

Command string is <
Reg Delete "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate" /v "Auto Update">.



Install registkey setting as follow
--------------------------------------
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update]
"AUOptions"=dword:00000001
"ConfigVer"=dword:00000001
"DetectionStartTime"="2005.10.27 14:25:58"
"NextDetectionTime"="2005-11-08 02:21:19"
"BalloonTime"="2005-10-27 05:54:41"
"BalloonType"=dword:00000005
-----------------------------------------

I have do not research "OfflineDetectionPending"=dword:00000001" keys.

I suspect the most likely cause of the 'repair' was the removal of the
"SusServerVersion" value which has been traced, in a couple of instances, to
dysfunction in getting the WUA to work properly.

It may well be that we need to implement a standard diagnotic procedure to
purge the values in this key as well when the client is not working.

Note: Any values needed in this key /will/ be recreated by the WUA as they are
needed.

The AUOptions value is deprecated; it is now contained in
HKLM\Software\Policies\Microsoft\Windows\WindowsUpdate\AU

so you can remove it completely.


"say-yamai" <say-yamai.1y7xfd@DoNotSpam.com> wrote in message
news:say-yamai.1y7xfd@DoNotSpam.com...
>
> Removed registKey setting as follow
> ----------------------------------------
> Windows Registry Editor Version 5.00
>
> [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto
> Update]
> "AUOptions"=dword:00000001
> "SusServerVersion"=dword:00000001
> "NextDetectionTime"="2005-11-09 00:52:43"
> "OfflineDetectionPending"=dword:00000001
> "ConfigVer"=dword:00000001
> "AUState"=dword:00000002
> "DetectionStartTime"="2005.11.09 09:36:03"
> "LastWaitTimeout"="2005.11.09 05:47:04"
> -------------------------------------------
> I had removed "Auto Update" ,
>
> Command string is <
> Reg Delete
> "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate"
> /v "Auto Update">.
>
>
>
> Install registkey setting as follow
> --------------------------------------
> Windows Registry Editor Version 5.00
>
> [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto
> Update]
> "AUOptions"=dword:00000001
> "ConfigVer"=dword:00000001
> "DetectionStartTime"="2005.10.27 14:25:58"
> "NextDetectionTime"="2005-11-08 02:21:19"
> "BalloonTime"="2005-10-27 05:54:41"
> "BalloonType"=dword:00000005
> -----------------------------------------
>
> I have do not research "OfflineDetectionPending"=dword:00000001" keys.
>
>
> --
> say-yamai
> ------------------------------------------------------------------------
> say-yamai's Profile: http://forums.techarena.in/members/11123.htm
> View this thread: Client WSUS problem - "Launching old AU client"
> India Forum - http://forums.techarena.in
>

[say-yamai]

I see,and deeply understand.
Many thanks ,Lawrence Garvin.