> The port number it needs to communicate on will be the same as the one the
> admin tool is set to, so check your settings in there. If it's something
> other than port 80 you need to change in your GPO the port number to the
> correct one, i.e.
http://servername:8530 or whatever it is.
>
> If it is port 80 already, I think you've got a different problem, it still
> sounds like an IIS misconfiguration to me though.
> --
> Steve.
>
>
> "David Andrews" wrote:
>
> > Steve
> >
> > I think I used to have a WSUS Administration site before the upgrade but am
> > assuming it removed it since WSUS 3 uses the MMC rather than the web
> > interface.
> >
> > On my WSUS server, in IIS, I only have the Default Website which contains
> > the following:
> >
> > ApiRemoting30
> > ClientWebService
> > Content
> > DssAuthWebServer
> > Inventory
> > ReportingWebService
> > SelfUpdate
> > ServerSyncWebService
> > SimpleAuthWebService
> >
> > The defauit website is set to Port 80.
> >
> > The only other task this server performs is RIS (Remote Installation Server).
> >
> > Currently my GPO for WSUS is just set to the site without any port number.
> >
> > David
> >
> > "Steve-UK" wrote:
> >
> > > You should have a site listed as "WSUS Administration". Go to the properties
> > > of it, change the TCP port to port 80. If you're hosting other websites on
> > > IIS, you will need to change their ports as well to prevent a conflict. This
> > > can get messy, which is why I suggested changing the connection port in the
> > > GPO instead, it's simpler. Usually it would be 8530, but it could be 443 or
> > > 8531 depending on how you set it up.
> > >
> > > I'd only recommend changing the port in IIS if you're only using IIS on that
> > > server for WSUS. You will have at least one other website, the default one,
> > > you can safely change that to some miscellaneous port if you're not using it.
> > > --
> > > Steve.
> > >
> > >
> > > "David Andrews" wrote:
> > >
> > > > Steve
> > > >
> > > > Thanks for your reply.
> > > >
> > > > I seem to be having difficulty locating the client connection port in the
> > > > admin tool and also which site I should be checking in IIS. Could you point
> > > > me in the right direction please?!
> > > >
> > > > I have checked a couple of the May updates and it is listing computers as
> > > > having those updates installed so I 'think' its working but would like to
> > > > double-check the ports following your message.
> > > >
> > > > I usually recieve calls from end users when I approve updates as well and I
> > > > haven't had any this month! You'd think after the years of rolling out
> > > > Windows Updates, they'd be used to it! :-)
> > > >
> > > > Regards
> > > > David
> > > >
> > > > "Steve-UK" wrote:
> > > >
> > > > > Actually it sounds as though you might have a problem, I had the same
> > > > > problem, clients don't install updates after the upgrade. It was a port
> > > > > communication problem, you can figure out which port you're using via the
> > > > > admin tool, try connecting to the server on different ports. (Or check in
> > > > > IIS what port the server is using).
> > > > >
> > > > > Once you've figured out which port, the simplest thing to do is to change
> > > > > the GPO that assigns the server location to the clients. Change it from
> > > > > "
http://servername" to "
http://servername:8530" or whatever the correct port
> > > > > is.
> > > > >
> > > > > The other way of doing it is to change the properties in IIS of the WSUS
> > > > > site so that it responds on port 80.
> > > > > --
> > > > > Steve.
> > > > >
> > > > >
> > > > > "David Andrews" wrote:
> > > > >
> > > > > > Hi.
> > > > > >
> > > > > > Sorry everyone!
> > > > > >
> > > > > > It seems I am misreading the way some of the information is presented in
> > > > > > WSUS 3 and the updates are being installed!
> > > > > >
> > > > > > I think there is a difference in the way WSUS 3.0 reports the computers
> > > > > > requiring updates figure which made me think none of the updates were being
> > > > > > installed correctly.
> > > > > >
> > > > > > David
> > > > > >
> > > > > > "David Andrews" wrote:
> > > > > >
> > > > > > > Hi
> > > > > > >
> > > > > > > I recently upgraded our WSUS 2 server to WSUS 3 after running the RC in a
> > > > > > > test environment without any problems.
> > > > > > >
> > > > > > > The WSUS 3 installation went fine and it updated the local database engine
> > > > > > > to the new version (currently not using SQL Server but intend to move it at
> > > > > > > some point) and it is showing all the registered client computers that I
> > > > > > > could see under WSUS 2 along with their status etc.
> > > > > > >
> > > > > > > I recently approved the May updates for installation and expected them to
> > > > > > > start being rolled out the following morning but it seems the clients are not
> > > > > > > getting the update information like they did prior to the upgrade.
> > > > > > >
> > > > > > > The WSUS 3 details for computers requiring updates has not changed at all
> > > > > > > since approving the May updates and usually I would see this figure reduce
> > > > > > > throughout the day as people rebooted their PCs following the updates being
> > > > > > > installed.
> > > > > > >
> > > > > > > The client computers appear to be reporting their status to the WSUS server
> > > > > > > OK as the reported times are all current.
> > > > > > >
> > > > > > > I cannot see any errors in the event log on the WSUS server and there is
> > > > > > > nothing to suggest any problems except that the clients are being sent the
> > > > > > > updates.
> > > > > > >
> > > > > > > Has anyone else had this or similar issue or suggest where I can look to
> > > > > > > find out why it has stopped working?
> > > > > > >
> > > > > > > Regards
> > > > > > > David