|
|
"Lawrence Garvin (MVP)" <onsitech[ at ]community.nospam> wrote in message
news:...
[Quoted Text] > "Massimo Rosen" <mrosenno[ at ]spamcfc-it.de> wrote in message
> news:466E42FF.93CCEDB9[ at ]spamcfc-it.de...
>>> > Actually, there *is* something that causes this for an increasing
>>> > number
>>> > of users. The WSUS 3.0 upgrade will change any non-default port
>>> > configuration of the WSUS website to the default of 8530 without
>>> > warning
>>> > or notice, but will leave a default website setup on port 80 which at
>>> > least has the selfupdate tree, but not much more than that.
>>>
>>> As noted in a previous reply, it doesn't actually do this "without
>>> warning",
>>> although you may have buzzed through the "notice" screen during the
>>> installation/upgrade without noticing.
So... I was wrong that it doesn't provide any warning. The WSUS 3 installer
upgrades wherever the WSUS 2 server is installed.
But there is one scenario I've not tested, that could be problematic. That
would be a server with WSUS 2 installed on the Default Web Site, followed by
the installation of WSS, and then WSS configured to not manage the several
WSUS 2 virtual directories. In this scenario, it's possible that the WSUS 3
installer would detect the WSS on the DWS, and opt to not install WSUS 3 on
the DWS.
Perhaps if I have a couple of free hours this week, I'll explore that
scenario.
>> No, I mean any WSUS Server running on *anything* other than 8530, that
>> explicitly includes 80, that too will get chnaged to 8530 (as this is
>> exactly what happened to me yesterday).
>
> Well... Massimo... I've just gone through a boatload of
> installation/upgrade scenarios, and I didn't observe anything like this
> behavior at all.
>
> But, just to be sure, I'm going to give it one more shot. If you can
> provide me with the exact scenario in which you applied this WSUS3 upgrade
> and had it switch ports on you, that would help -- including a list of
> other web applications installed to the Default Web Site *after* the
> installation of WSUS2.
Otherwise, for the record, I just successfully upgraded a WSUS2SP1 system on
a Default Web Site to WSUS3 on the same Default Web Site.
Screen caps of the process can be downloaded from here:
http://wsusinfo.onsitechsolutions.com/downloads/WSUS2toWSUS3onDWS.doc
(453kb)
I submit that Massimo's server either:
[a] Originally had WSUS3 installed on the alternate virtual server, or
[b] Was not a simple installation of WSUS2SP1 on a Default Web Site.
--
Lawrence Garvin, M.S., MCTS, MCP
Independent WSUS Evangelist
MVP-Software Distribution (2005-2007)
https://mvp.support.microsoft.com/profile=30E00990-8F1D-4774-BD62-D095EB07B36E
Everything you need for WSUS is at
http://technet2.microsoft.com/windowsserver/en/technologies/featured/wsus/default.mspx
And, almost everything else is at
http://wsusinfo.onsitechsolutions.com
.....
|
|
|