Windows Vista Tips

Windows Vista Tips > Newsgroups > Windows Update > Problem after upgrading SUS to WSUS

Reply
Thread Tools Display Modes

Problem after upgrading SUS to WSUS

 
 
drazen_petrek@yahoo.com
Guest
Posts: n/a

 
      08-12-2005
I successfully upgraded our SUS to WSUS, we had only one
central SUS server. WSUS is synchronizing successfully but
there are errors when clients try to update from WSUS.
WSUS was moved to port 80, SUS decomissioned.
Here is an excerpt from one clients WindowsUpdate.log

....
2005-08-11 19:29:21 1460 110 DnldMgr * BITS job initialized, JobId =
{3A73B077-6835-4362-9A31-2EBBFE183AFF}
2005-08-11 19:29:21 1460 110 DnldMgr BITS job
{3A73B077-6835-4362-9A31-2EBBFE183AFF} using proxy =
mostar.ipcck.hr:8080, bypass = <NULL>
2005-08-11 19:29:21 1460 110 DnldMgr * Downloading from
http://192.168.0.22/Content/49/E8E13...1D19FC7249.exe
to
C:\WINDOWS\SoftwareDistribution\Download\S-1-5-18\7718e1060eee576fcd39e9a428223f4e\WindowsXP-KB898461-x86-ENU.exe
(full file).
2005-08-11 19:29:21 1460 110 Agent *********
2005-08-11 19:29:21 1460 110 Agent ** END ** Agent: Downloading
updates [CallerId = AutomaticUpdates]
2005-08-11 19:29:21 1460 110 Agent *************
2005-08-11 19:29:24 1460 110 Report REPORT EVENT:
{6386BF97-F728-4374-BB9F-A3B5F53454C7} 2005-08-11
19:29:19+0200 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software
Synchronization Agent has finished detecting items.
2005-08-11 19:29:24 1460 110 Report REPORT EVENT:
{CD7AE7D9-E176-4E86-9E85-ED3F5C044621} 2005-08-11
19:29:19+0200 1 153 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Pre-Deployment
Check Reporting client status.
2005-08-11 19:29:25 1460 948 DnldMgr WARNING: BITS job
{3A73B077-6835-4362-9A31-2EBBFE183AFF} failed, updateId =
{AE59C5D5-42CA-4290-8FD1-D2DF55AB1FCD}.101, hr = 0x80190197,
BG_ERROR_CONTEXT = 5
2005-08-11 19:29:25 1460 948 DnldMgr Progress failure bytes total =
488176, bytes transferred = 0
2005-08-11 19:29:25 1460 948 DnldMgr Failed job file: URL =
http://192.168.0.22/Content/49/E8E13...1D19FC7249.exe,
local path =
C:\WINDOWS\SoftwareDistribution\Download\S-1-5-18\7718e1060eee576fcd39e9a428223f4e\WindowsXP-KB898461-x86-ENU.exe
2005-08-11 19:29:26 1460 948 DnldMgr WARNING: Download job failed
because of proxy auth or server auth.
....

Looks like BITS is trying to use proxy to download updates which
are on local (LAN) WSUS server. The proxy used is our proxy that
clients use to access Internet. How can I tell BITS on all machines
not to use proxy when downloading updates? As I read about BITS,
looks like its using IE proxy setting of user currently logged in
when it tries to download updates. However the user has proxy
bypass exception defined too, got it through Group Policy:
192.168.*;*.ipcck.hr;*.ipc.hr. However looks like still BITS is
using proxy to access local WSUS...
How to change this?

 
Reply With Quote
 
 
 
 
TaurArian [MVP]
Guest
Posts: n/a

 
      08-13-2005
Perhaps try the WSUS Newsgroup

news://msnews.microsoft.com/microsof...pdate_services
(OE client)
or
http://www.microsoft.com/communities...pdate_services
(web client)


<> wrote in message
news: oups.com...
>I successfully upgraded our SUS to WSUS, we had only one
> central SUS server. WSUS is synchronizing successfully but
> there are errors when clients try to update from WSUS.
> WSUS was moved to port 80, SUS decomissioned.
> Here is an excerpt from one clients WindowsUpdate.log
>
> ...
> 2005-08-11 19:29:21 1460 110 DnldMgr * BITS job initialized, JobId =
> {3A73B077-6835-4362-9A31-2EBBFE183AFF}
> 2005-08-11 19:29:21 1460 110 DnldMgr BITS job
> {3A73B077-6835-4362-9A31-2EBBFE183AFF} using proxy =
> mostar.ipcck.hr:8080, bypass = <NULL>
> 2005-08-11 19:29:21 1460 110 DnldMgr * Downloading from
> http://192.168.0.22/Content/49/E8E13...1D19FC7249.exe
> to
> C:\WINDOWS\SoftwareDistribution\Download\S-1-5-18\7718e1060eee576fcd39e9a428223f4e\WindowsXP-KB898461-x86-ENU.exe
> (full file).
> 2005-08-11 19:29:21 1460 110 Agent *********
> 2005-08-11 19:29:21 1460 110 Agent ** END ** Agent: Downloading
> updates [CallerId = AutomaticUpdates]
> 2005-08-11 19:29:21 1460 110 Agent *************
> 2005-08-11 19:29:24 1460 110 Report REPORT EVENT:
> {6386BF97-F728-4374-BB9F-A3B5F53454C7} 2005-08-11
> 19:29:19+0200 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates
> Success Software
> Synchronization Agent has finished detecting items.
> 2005-08-11 19:29:24 1460 110 Report REPORT EVENT:
> {CD7AE7D9-E176-4E86-9E85-ED3F5C044621} 2005-08-11
> 19:29:19+0200 1 153 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates
> Success Pre-Deployment
> Check Reporting client status.
> 2005-08-11 19:29:25 1460 948 DnldMgr WARNING: BITS job
> {3A73B077-6835-4362-9A31-2EBBFE183AFF} failed, updateId =
> {AE59C5D5-42CA-4290-8FD1-D2DF55AB1FCD}.101, hr = 0x80190197,
> BG_ERROR_CONTEXT = 5
> 2005-08-11 19:29:25 1460 948 DnldMgr Progress failure bytes total =
> 488176, bytes transferred = 0
> 2005-08-11 19:29:25 1460 948 DnldMgr Failed job file: URL =
> http://192.168.0.22/Content/49/E8E13...1D19FC7249.exe,
> local path =
> C:\WINDOWS\SoftwareDistribution\Download\S-1-5-18\7718e1060eee576fcd39e9a428223f4e\WindowsXP-KB898461-x86-ENU.exe
> 2005-08-11 19:29:26 1460 948 DnldMgr WARNING: Download job failed
> because of proxy auth or server auth.
> ...
>
> Looks like BITS is trying to use proxy to download updates which
> are on local (LAN) WSUS server. The proxy used is our proxy that
> clients use to access Internet. How can I tell BITS on all machines
> not to use proxy when downloading updates? As I read about BITS,
> looks like its using IE proxy setting of user currently logged in
> when it tries to download updates. However the user has proxy
> bypass exception defined too, got it through Group Policy:
> 192.168.*;*.ipcck.hr;*.ipc.hr. However looks like still BITS is
> using proxy to access local WSUS...
> How to change this?
>


 
Reply With Quote
 
Robert Aldwinckle
Guest
Posts: n/a

 
      08-13-2005
<> wrote in message
news: oups.com...
>I successfully upgraded our SUS to WSUS, we had only one
> central SUS server. WSUS is synchronizing successfully but
> there are errors when clients try to update from WSUS.
> WSUS was moved to port 80, SUS decomissioned.
> Here is an excerpt from one clients WindowsUpdate.log
>
> ...
> 2005-08-11 19:29:21 1460 110 DnldMgr * BITS job initialized, JobId =
> {3A73B077-6835-4362-9A31-2EBBFE183AFF}
> 2005-08-11 19:29:21 1460 110 DnldMgr BITS job
> {3A73B077-6835-4362-9A31-2EBBFE183AFF} using proxy =
> mostar.ipcck.hr:8080, bypass = <NULL>
> 2005-08-11 19:29:21 1460 110 DnldMgr * Downloading from
> http://192.168.0.22/Content/49/E8E13...1D19FC7249.exe
> to
> C:\WINDOWS\SoftwareDistribution\Download\S-1-5-18\7718e1060eee576fcd39e9a428223f4e\WindowsXP-KB898461-x86-ENU.exe
> (full file).
> 2005-08-11 19:29:21 1460 110 Agent *********
> 2005-08-11 19:29:21 1460 110 Agent ** END ** Agent: Downloading
> updates [CallerId = AutomaticUpdates]
> 2005-08-11 19:29:21 1460 110 Agent *************
> 2005-08-11 19:29:24 1460 110 Report REPORT EVENT:
> {6386BF97-F728-4374-BB9F-A3B5F53454C7} 2005-08-11
> 19:29:19+0200 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software
> Synchronization Agent has finished detecting items.
> 2005-08-11 19:29:24 1460 110 Report REPORT EVENT:
> {CD7AE7D9-E176-4E86-9E85-ED3F5C044621} 2005-08-11
> 19:29:19+0200 1 153 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Pre-Deployment
> Check Reporting client status.
> 2005-08-11 19:29:25 1460 948 DnldMgr WARNING: BITS job
> {3A73B077-6835-4362-9A31-2EBBFE183AFF} failed, updateId =
> {AE59C5D5-42CA-4290-8FD1-D2DF55AB1FCD}.101, hr = 0x80190197,
> BG_ERROR_CONTEXT = 5
> 2005-08-11 19:29:25 1460 948 DnldMgr Progress failure bytes total =
> 488176, bytes transferred = 0
> 2005-08-11 19:29:25 1460 948 DnldMgr Failed job file: URL =
> http://192.168.0.22/Content/49/E8E13...1D19FC7249.exe,
> local path =
> C:\WINDOWS\SoftwareDistribution\Download\S-1-5-18\7718e1060eee576fcd39e9a428223f4e\WindowsXP-KB898461-x86-ENU.exe
> 2005-08-11 19:29:26 1460 948 DnldMgr WARNING: Download job failed
> because of proxy auth or server auth.
> ...
>
> Looks like BITS is trying to use proxy to download updates which
> are on local (LAN) WSUS server. The proxy used is our proxy that
> clients use to access Internet. How can I tell BITS on all machines
> not to use proxy when downloading updates? As I read about BITS,
> looks like its using IE proxy setting of user currently logged in
> when it tries to download updates. However the user has proxy
> bypass exception defined too, got it through Group Policy:
> 192.168.*;*.ipcck.hr;*.ipc.hr. However looks like still BITS is
> using proxy to access local WSUS...
> How to change this?



Use proxycfg -d


<title>KB900935 - How the Windows Update client determines which proxy server to use to connect to the Windows Update Web
site</title>


---


 
Reply With Quote
 
 
 
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Upgrading from WUS Beta2 to WSUS ZTZ Windows Update 1 08-01-2005 10:19 AM
Another WSUS Problem Alessandro Windows Update 1 07-19-2005 01:28 PM
WSUS problem Kermitdafwog Windows Update 1 06-01-2005 03:15 PM
WSUS problem Kermitdafwog Windows Update 0 06-01-2005 03:05 PM
Client WSUS Error In WSUS Console 0x8024400a Don Windows Update 0 05-23-2005 02:37 PM



1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59