Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

WSUS Questions 1

Status
Not open for further replies.

pannivas

IS-IT--Management
Jun 22, 2005
2
DE
i installed WSUS on a couple of servers but on of them is giving me this event id error. i looked it up but i cannot find how to resolve it. Any ideas?

Event ID: 506
Source: Windows Server Update
Category Update Services Service
Description: The SelfUpdate Tree is not working. Clients may not be able to update to the latest WUA client software and communicate with the WSUS Server.
 
Anonymous (Last update 7/12/2005):
Here is something useful that I found out the hard way. If you have a server running WSUS on port 8530 and you have more than 1 website running on port 80, as I did, you have to make sure that the SelfUpdate tree virtual site exists on all of your port 80 sites (I use host headers to point the users to the correct site on the server). When I ran the script to install SelfUpdate tree, it only installed it on 1 of my sites running on port 80, not all of them. To fix this, save the SelfUpdate tree virtual file configuration. Then import it on each of your sites running on port 80. Reset IIS, reset the Update Services service and you should be good to go.

Anonymous (Last update 6/21/2005):
From a newsgroup post: "If you are not using the default website for anything, I would stop the default website, change the port number for the WSUS to port 80, and restart IIS. If you still have some web applications that need port 80 or you prefer to keep WSUS on port 8530, you will need to run installselfupdateonport80.vbs in the \Program Files\Update Services\Setup directory. The will restore the selfupdate virtual folder that SUS removed during it’s uninstall".

See the link to "Automatic Updates must be updated" for additional information on this issue.

Denis Scherbakov (Last update 6/20/2005):
I got this error logged into my event Log after I ran WSUS for the first time. Although it was logged, my SelfUpdate Tree was ok. To test this I restarted Update Services (WSUS) service and the error disappeared. So be aware, that WSUS might sometimes log it by mistake. See the link to “SelfUpdate Tree is not working” for information on this event.

Philipp (Last update 6/16/2005):
See the link to "WSUS Wiki" for information on Windows Server Update Services.
 
Star for Pannivas on this. The link provided got rid of this problem for me. Well mostly. It provided enough insight to figure out the solution.

I had SUS and WSUS installed on the same server. In IIS I had stopped the default webpage and had SUS running on port 80.

To resolve this issue I stopped SUS and started the defaulted website. I then restared the Update Services service and all was well.

Thanks!
Mike
 
I had the same issue... I kept receiving Event 506 after restarting the Update Services. Some clients were reporting in anyway (All XP clients and a few 2000 clients).

I noticed that the SelfUpdate virtual directory was created under both the default web site and the WSUS Administration websites.

BTW: using Windows 2003 SBS with OWA installed on the default website.

Solution: I found that it didn't really matter what port you had the WSUS Administration site bound to (8530 is the default).

Maybe not all steps are required but this worked: (I have several website on this server)

1. Configured WSUS Administration to be on a specific IP (The same IP as the default website)
2. Entered a DNS entry for this IP address: (wsus.server.local)
3. Used this entry for my GPO
4. Punched down to the SelfUpdate Virtual directory in the default website. Unchecked the SSL checkbox for this directory. (I am using SSL for OWA on the default website and of course the certificates do not jive so hense event 506). Make sure that you anonymous account works, etc.
5. Restart the default website and restart Update services
6. A good check is to pop an html file in the selfupdate virtual directory (Program Files/Update Services/Self Update). Goto a client machine and enter the appropriate url (without specifying a port)... (ex. wsus.server.local/selfupdate/myfile.html). If you can get to this anonymously then you should be in good shape...
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top