> I tried two times to install over WSUS 2.0. WSUS 2.0 was originally on port 80.
>
> The first time I tried upgrading it upgraded but changed the port to 8530.
>
> The second time I tried, (after restoring the server from a ghost image) I
> used the command line option /g DEFAULT_WEBSITE=1 and it failed. The log said
> something about "the website could not be found" (sorry. I'm reciting this
> from memory. I'm off work now)
>
> The third time, I tried installing WSUS 3.0 over the failed second install,
> and that's when I got the message that WSUS 3.0 could not be installed on
> port 80 saying that It was either SBS or sharepoint was installed (which are
> both not true).
>
> I already restored the server back to 2.0 so it would work over the weekend.
> Monday when I get back to work I can try it again and generate another log
> file. The only thing I can think of is that I followed the security
> guidelines in the WSUS 2.0 deployment guide (when I upgraded to WSUS 2.0 a
> few years ago) and one of those settings is conflicting with the installer,
> but I'm only guessing here.
>
>
> "Fei Cao (MSFT)" wrote:
>
> > If this is an upgrade over WSUS 2.0, then it will use whatever port WSUS 2.0
> > uses.
> >
> > If it is a fresh install, can you provide setup log under
> > %temp%\WSUSSetup.log?
> >
> > --
> > Fei Cao
> > Microsoft, WSUS
> >
> > This posting is provided "As Is" with no warranties, and confers no rights.
> > Use of included script samples are subject to the terms specified at
> >
http://www.microsoft.com/info/cpyright.htm> >
> > "Ed Fry" <Ed Fry[ at ]discussions.microsoft.com> wrote in message
> > news:5F7BD4B8-D910-4649-B436-5CEC7238E042[ at ]microsoft.com...
> > > I'm installing WSUS 3.0 on my older WSUS 2.0 Mahcine, and I'm getting the
> > > message "You cannot use the default web site..." and it wants to install
> > > WSUS
> > > on port 8530 instead of port 80
> > >
> > > -I am not Using SBS
> > > -Sharepoint is not installed
> > > -there is no web site currently using port 80, or any sites on this server
> > > for that matter.
> > >
> > > Is there a security setting that would cause this error?
> >
> >
> >