WSUS « Swollen Technology

Category Archives: WSUS

Windows Update Fix for Windows 2000

August 25, 2008 – 4:59 pm
Posted in WSUS
Leave a Comment

http://djlizard.net/2006/06/28/169/

Reg File Code:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Svchost]
“netsvcs”=hex(7):45,00,76,00,65,00,6e,00,74,00,53,00,79,00,73,00,74,00,65,00,\
6d,00,00,00,49,00,61,00,73,00,00,00,49,00,70,00,72,00,69,00,70,00,00,00,49,\
00,72,00,6d,00,6f,00,6e,00,00,00,4e,00,65,00,74,00,6d,00,61,00,6e,00,00,00,\
4e,00,77,00,73,00,61,00,70,00,61,00,67,00,65,00,6e,00,74,00,00,00,52,00,61,\
00,73,00,61,00,75,00,74,00,6f,00,00,00,52,00,61,00,73,00,6d,00,61,00,6e,00,\
00,00,52,00,65,00,6d,00,6f,00,74,00,65,00,61,00,63,00,63,00,65,00,73,00,73,\
00,00,00,53,00,45,00,4e,00,53,00,00,00,53,00,68,00,61,00,72,00,65,00,64,00,\
61,00,63,00,63,00,65,00,73,00,73,00,00,00,54,00,61,00,70,00,69,00,73,00,72,\
00,76,00,00,00,4e,00,74,00,6d,00,73,00,73,00,76,00,63,00,00,00,57,00,5a,00,\
43,00,53,00,56,00,43,00,00,00,00,00
“rpcss”=hex(7):52,00,70,00,63,00,53,00,73,00,00,00,00,00
“wugroup”=hex(7):77,00,75,00,61,00,75,00,73,00,65,00,72,00,76,00,00,00,00,00
“BITSgroup”=hex(7):42,00,49,00,54,00,53,00,00,00,00,00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Svchost\BITSGroup]
“DefaultRpcStackSize”=dword:00000008

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Svchost\netsvcs]
“CoInitializeSecurityParam”=dword:00000001

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Svchost\wugroup]
“CoInitializeSecurityParam”=dword:00000001

http://djlizard.net/2006/08/14/175/

(edit): 0) Make sure you’re using the latest build of Dial-a-fix.
1) Reboot so you’re starting with a clean slate.
2) Run all of DAF section #5 (Registration center).
3) Run DAF section #3 (WU/WUAU).
4) Start > Run > rundll32.exe setupapi.dll,InstallHinfSection DefaultInstall 132 %systemroot%\inf\au.inf
(Note: the above command is one huge line — it has been wrapped for easier reading)
5) Immediately merge this .reg file: win2ksvchost.reg
6) Reboot.
7) Try Windows Update again. If it fails, try clicking “Flush SoftwareDistribution” in Dial-a-fix (and answer No) and then try Windows Update again.

A simple fix for Microsoft Update problems

March 18, 2008 – 6:52 pm
Posted in WSUS
Leave a Comment

http://blogs.techrepublic.com.com/techofalltrades/?p=130

Event ID: 506 Event Source: Windows Server Update Services

November 30, 2007 – 7:35 pm
Posted in Event Errors, WSUS
Leave a Comment

SYMPTOMS

You may see an event “The SelfUpdate Tree is not working” in the event log, and WSUS Clients may not be able to update to the latest WSUS client software or to communicate with the WSUS Server.

Event ID: 506
Event Source: Windows Server Update Services
Event Category: WUS Service

Description

The SelfUpdate Tree is not working. Clients may not be able to update to the latest WSUS client software and communicate with the WSUS Server. There are several reasons for this potentially happening.

Cause

One reason is that the SelfUpdate service accesses the WSUS server on 127.0.0.1:80. This does not work if you have the website bound to a specific IP address in your IIS configuration.

This can also be caused by incorrect permissions on the self update tree or possibly the entire self update tree or even IIS is corrupted. Another possible time you see this is if the same server that is running WSUS is also running another web site.

Workaround

The specific workaround depends on the exact cause of this error.

TO resolve the issue around using 127.0.0.1, you can either to set your IIS Configuration to respond to “All unassigned” addresses or add 127.0.0.1 to the list of IP addresses used for Selfupdate.

If your issue is around permisiosns, verify that the SelfUpdate virtual folder in IIS includes anonymous access rights for IUSR account.

If you are running multiple web sites on one system, you can try adding a host header for the other web site(s) on your system.

As a final way to solve the issue, remove both WSUS, IIS and reboot. Then re-install IIS and WSUS.

Status

You can work around this in either of ways suggested above.