|
|
After a *lot* of problems we have finally got our SBS Premium 2003 R2
back to running "Microsoft Windows Server Update Services Service Pack
1" (or that's what Add or Remove Programs says we are running!)
One of the Updates Waiting for Review is "Windows Server Update
Services 3.0 SP1" and I seem to remember the original problem that
took us back to having to rebuild also sorts of things on the server
was just running that update!
So, is there a guide to upgrading WSUS from where we are to where it
wants us to be - preferably specific to SBServer 2003?
TIA,
JohnK
|
|
"John F Kappler" <john[ at ]pceffect.co.uk> wrote in message
news:9v13h45rs8qsbon37do9k0k30s6220a4l6[ at ]4ax.com...
[Quoted Text] > So, is there a guide to upgrading WSUS from where we are to where it
> wants us to be - preferably specific to SBServer 2003?
Well, for starters, the Product Release Notes would be a good place to
start.
http://go.microsoft.com/fwlink/?LinkId=71268
From there I would recommend
"Installing WSUS 3.0 on Windows SBS 2003"
http://go.microsoft.com/fwlink/?LinkId=89081
--
Lawrence Garvin, M.S., MCITP(x2), MCTS(x5), MCP(x7), MCBMSP
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2009)
MS WSUS Website: http://www.microsoft.com/wsus
My Websites: http://www.onsitechsolutions.com;
http://wsusinfo.onsitechsolutions.com
My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
|
|
Thank-you for that. I'm trying to avoid falling in to whatever trap it
was that occurred the last time we tried to go to WSUS 3.0 which
failed and resulted in us having to spend several elapsed weeks (I'm
not joking!) trying to get our SBS2003 R2 back to where it was before
we started....
In the first document you mention, it states that "Software Update
Services 1.0" should be uninstalled before trying to install WSUS 3.0.
According to our Add/Remove programs list we have "Microsoft Windows
Server Update Services Service Pack 1" installed. Is this the same
thing?
Also, under Upgrade Issues it states that if the install fails, we
should re-install the previous version and get it running again.
If this is the same thing as "Software Update Services 1.0", I presume
we re-install it, get it working, then uninstall it, before trying
again. This doesn't sound right but perhaps you can confirm....
We dont seem to be foul of the pre-requisites for SBS installation,
but I'm reluctant to start this again until I'm clear about the
process.....
Thanks
JohnK
On Wed, 5 Nov 2008 09:34:45 -0600, "Lawrence Garvin \(MVP\)"
<lawrence[ at ]news.postalias> wrote:
[Quoted Text] >"John F Kappler" <john[ at ]pceffect.co.uk> wrote in message >news:9v13h45rs8qsbon37do9k0k30s6220a4l6[ at ]4ax.com... > >> So, is there a guide to upgrading WSUS from where we are to where it >> wants us to be - preferably specific to SBServer 2003? > >Well, for starters, the Product Release Notes would be a good place to >start. > > http://go.microsoft.com/fwlink/?LinkId=71268> >From there I would recommend >"Installing WSUS 3.0 on Windows SBS 2003" > > http://go.microsoft.com/fwlink/?LinkId=89081
|
|
"John F Kappler" <john[ at ]pceffect.co.uk> wrote in message
news:5mu5h4t18dakkfeeeabf58eusc4nc0qgrt[ at ]4ax.com...
[Quoted Text] > Thank-you for that. I'm trying to avoid falling in to whatever trap it
> was that occurred the last time we tried to go to WSUS 3.0 which
> failed and resulted in us having to spend several elapsed weeks (I'm
> not joking!) trying to get our SBS2003 R2 back to where it was before
> we started....
>
> In the first document you mention, it states that "Software Update
> Services 1.0" should be uninstalled before trying to install WSUS 3.0.
>
> According to our Add/Remove programs list we have "Microsoft Windows
> Server Update Services Service Pack 1" installed. Is this the same
> thing?
No, it's not. "Microsoft Windows Server Update Services" is WSUS, and this
package is colloquially known as "WSUS 2.0 SP1". This was the product
installed by the SBS2003 R2 Technologies update.
The issue with SUS 1.0 would refer to a scenario in which "Software Update
Services" had been installed (prior to June 2005), and was then upgraded to
WSUS. This *could* be the case on your system. There's no way to determine
this from Add/Remove Programs.
The specific problem with SUS 1.0 has to do with two core issues:
[1] The removal utility for SUS 1.0 did not thoroughly remove all parts of
SUS 1.0, it left the catalog file in the root of the website.
[2] The upgrade documentation from SUS 1.0 to WSUS 2.0 did not actually
provide instructions on how to safely uninstall SUS 1.0, it merely
instructed the admin to 'stop' the SUS 1.0 website and leave it in place. If
the SUS 1.0 installation still exists, it needs to be removed; however,
uninstalling SUS 1.0 will actually break WSUS 2.0 by removing the
/selfupdate and /clientwebservice virtual directories from the Default Web
Site.
Furthermore, there's also a known issue where the WSUS 3.0 SP1 installer
fails to properly recreate the /selfupdate virtual directory in the Default
Web Site (and the /clientwebservice virtual directory is no longer
needed)... so, ironically, the damage originally caused by uninstalling SUS
1.0 is no longer an issue when upgrading to WSUS 3.0 SP1, as that 'repair'
work has to be done post-upgrade regardless (or in the case of
/clientwebservice is now moot).
To recreate the missing /selfupdate virtual directory after completing the
upgrade to WSUS 3.0 SP1:
[a] Create a virtual directory in the Default Web Site named 'selfupdate'
(This may also, in some instances, need to be done in the 'WSUS
Administration 'website.)
[b] Assign the pathname of this virtual directory to C:\Program Files\Update
Services\Selfupdate.
[c] Enable Anonymous Access permissions on the 'selfupdate' virtual
directory via IIS Manager.
Also be aware that in the SBS2003 environment, the customized MMC you've
become used to using with the R2-enhanced WSUS 2.0 SP1 product will cease to
exist, and you'll then use the WSUS 3.0 MMC interface which will *not*
integrate with the SBS2003 Server Manager MMC (as the old RC2 WSUS 2.0 SP1
interface did). I think this is documented in the SBS2003 white paper, but
on the off chance that it isn't, I'm sharing now. <g>)
> Also, under Upgrade Issues it states that if the install fails, we
> should re-install the previous version and get it running again.
Yes, I strongly recommend making a full backup of the SBS2003 server prior
to applying this upgrade, as a precaution; however, as a minimum, you should
backup the WSUS 2.0 installation as described in the WSUS 2.0 documentation,
so that you can easily restore it.
Truth be told, 98% of upgrade failures are traceable back to issues already
documented in the Release Notes, so if you read and resolve the issues as
noted in the Release Notes, you have a high probability of success.
The restore means to restore the WSUS 2.0 SP1 (SBS R2 Technologies)
implementation. The specific details here are that the restore operation is
really limited to the WSUS database itself (and possibly recreating the
virtual directories in the Default Web Site).
The WSUS3 installer will make a backup of the WSUS 2.0 database, but it
writes the database backup to the ~\WSUS folder, which can be
self-destructive if the ~\WSUS folder gets removed (such as by a misguided
'uninstallation' of WSUS after a failed upgrade), thus my earlier
recommendation to make your own backup of the WSUS 2.0 environment before
initiating the upgrade.
--
Lawrence Garvin, M.S., MCITP(x2), MCTS(x5), MCP(x7), MCBMSP
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2009)
MS WSUS Website: http://www.microsoft.com/wsus
My Websites: http://www.onsitechsolutions.com;
http://wsusinfo.onsitechsolutions.com
My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
|
|
|