Questions about upgrading 2.0 to 3.0SP2

I am currently planning to update our WSUS 2.0 SP1 (finally) to 3.0SP2 at
the end of this month. After looking at the MS deployment guide for WSUS
3.0SP2 I am fairly confident I can go ahead with the inplace upgrade. It is
currently using MSDE locally on the server so I go with WIDB for the
database.

A couple items I am concerned about:

(1) the "Default Web Site" in IIS is configured to use port "8080". When I
upgrade to version 3.0 will the installer correctly detect and allow me to
continue using port 8080 or will it automatically change over to 80? I don't
think it should be a big deal as I can manually change it back to 8080 but I
am concerned it may mess something up. Has anyone done a similar install?

(2) I am using Group Policy to configure AU on client systems to point to
the WSUS server. Can I expect that the WUA will be upgraded on clients after
they connect to the upgraded server? Are there scenarios when the client WUA
version update fails and if so, how do to best workaround/resolve this?
Thanks.

"Barkley Bees" <> wrote in message
news:e$...

> A couple items I am concerned about:
>
> (1) the "Default Web Site" in IIS is configured to use port "8080". When I
> upgrade to version 3.0 will the installer correctly detect and allow me to
> continue using port 8080 or will it automatically change over to 80?

Actually, I'm surprised that your existing WSUS v2 environment is working in
this configuration. WSUS requires that:
[a] the Default Web Site is enabled, and
[b] the Default Web Site is running on port 80.

> (2) I am using Group Policy to configure AU on client systems to point to
> the WSUS server. Can I expect that the WUA will be upgraded on clients
> after they connect to the upgraded server?

Yes. If your clients' WUAgent has not already been upgraded to v7.2 by
connecting to WU/MU sometime in the past 21 month, this means you're still
running the v5.8 WUAgent (and most unfortunately so). When the clients
connect to the WSUS v3 SP2 server they will be updated to the v7.4 WUAgent.

> Are there scenarios when the client WUA version update fails and if so,
> how do to best workaround/resolve this?

Several . . . and they all revolve around the inability to connect to the
WSUS server.

The best 'workaround' is to ensure you properly upgrade/install the WSUS v3
server.

As for specific scenarios where this occurs, they need to be addressed on a
case-by-case basis, but given that you already have working clients, any
issues encountered will almost certainly be server-side issues, not client
side issues.



--
Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2010)

My Blog: http://onsitechsolutions.spaces.live.com
Microsoft WSUS Website: http://www.microsoft.com/wsus
My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin

Thank you for your reply Lawrence. Yes, we have a bit of an irregular
configuration as we required port 80 for another site on the server. We are
using Group Policy to point the clientsat the server and it has been working
without any issues:

Set the intranet update service for detecting updates:
http://servername:8080
Set the intranet statistics server: http://servername:8080

I did need to create a subdirectory on the other site using port 80 and
point it to SelfUpdate for it to work correctly though.
Our clients a have WUAgent version 7.0.6000.381.


"Lawrence Garvin [MVP]" <> wrote in message
news:OuJwGI%...
> "Barkley Bees" <> wrote in message
> news:e$...
>
>> A couple items I am concerned about:
>>
>> (1) the "Default Web Site" in IIS is configured to use port "8080". When
>> I upgrade to version 3.0 will the installer correctly detect and allow me
>> to continue using port 8080 or will it automatically change over to 80?
>
> Actually, I'm surprised that your existing WSUS v2 environment is working
> in this configuration. WSUS requires that:
> [a] the Default Web Site is enabled, and
> [b] the Default Web Site is running on port 80.
>
>> (2) I am using Group Policy to configure AU on client systems to point
>> to the WSUS server. Can I expect that the WUA will be upgraded on clients
>> after they connect to the upgraded server?
>
> Yes. If your clients' WUAgent has not already been upgraded to v7.2 by
> connecting to WU/MU sometime in the past 21 month, this means you're still
> running the v5.8 WUAgent (and most unfortunately so). When the clients
> connect to the WSUS v3 SP2 server they will be updated to the v7.4
> WUAgent.
>
>> Are there scenarios when the client WUA version update fails and if so,
>> how do to best workaround/resolve this?
>
> Several . . . and they all revolve around the inability to connect to the
> WSUS server.
>
> The best 'workaround' is to ensure you properly upgrade/install the WSUS
> v3 server.
>
> As for specific scenarios where this occurs, they need to be addressed on
> a case-by-case basis, but given that you already have working clients, any
> issues encountered will almost certainly be server-side issues, not client
> side issues.
>
>
>
> --
> Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
> Principal/CTO, Onsite Technology Solutions, Houston, Texas
> Microsoft MVP - Software Distribution (2005-2010)
>
> My Blog: http://onsitechsolutions.spaces.live.com
> Microsoft WSUS Website: http://www.microsoft.com/wsus
> My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin
>