> "TimParker" <tim...[ at ]gmail.com> wrote in message
>
> news:56aaef6f-bea4-4abd-accd-18b566d24ef7[ at ]i76g2000hsf.googlegroups.com...
>
>
>
>
>
> >I am finally getting around to looking at our WSUS install. I started
> > with this agency about 6 months ago and the current install is working
> > great, but I would like to do two things. One is get us upgraded to
> > 3.0 SP1 and two is to get a DRP document update in place on how to
> > rebuild this from backups, etc.
>
> > We have Build 2.0.0.2620, which I believe is 2.0 SP1. I have so far,
> > tried restoring a copy of our database SQL 2000 (SUSDB) and then
> > installing the 2.0 SP1 build file that I found on our network. When I
> > tell it to use the existing server, in this case SQL is installed on
> > the same box. It only shows me a DEFAULT in the database pull down.
>
> > Am I missing any steps between the Database restore and the software
> > install? After I can rebuild the current version and see it all work
> > on my test server then I am going to attempt upgrading it to 3.0.
> > Which I believe will switch to an internal MS database due to our SQL
> > version.
>
> Hi Tim.
>
> With regard to your objective and your DRP document...
>
> 1. You may find it more expeditiuos to simply install a *fresh* copy of WSUS
> 3.0 SP1 rather than try to upgrade your current installation, no matter how
> good it's currently working. Depending on the age of the install, and the
> previous administrative maintenance efforts, your WSUS 2.0 installation may
> be more clogged up with "unneeded" stuff than is worth the effort of
> retaining through an upgrade.
>
> 2. As for the rebuild from backups, et.al. -- you'll find some different
> perspectives on this, but my general take on backing up a WSUS Server really
> depends on two things:
> [a] How large and/or complex is the installation, and
> [b] How much time can you afford to have the WSUS Server offline in case
> of a catastrophic failure.
>
> In general, rebuilding a WSUS Server doesn't take that much longer than it
> would to do a 'restore' from tape (and tape will be a requirement due to the
> multi-gigabyte size of the content store), but if you have stringent
> auditing requirements, or an intense desire to maintain history, or a
> complex group and approvals configuration, then backing up the database may
> be an easier alternative.
>
> If you determine that backing up the database is a preferable solution to
> simply opting for a rebuild-from-scratch, I would suggest simply using the
> built-in database backup tools in the SQL Server Management Studio, backing
> up the database to a folder on the same level as the "WSUSContent" folder,
> and then backing the whole collection to some offline/removable media.
>
> As for the upgrade from WSUS 2.0 to WSUS 3.0 -- my first and strongest
> suggestion is to thoroughly read the Release Notes, Getting Started
> guide(s), and Deployment Guide; then reading them a second time; and then
> doing the upgrade in a test environment, before the production environment.
> The most notable concern is that your existing WSUS 2.0/SQL2000
> installation, when upgraded, will cause the installation of an independent
> installation of the "Windows Internal Database" on your front-end server,
> unless you first address the underlying upgrade from SQL 2000 to SQL 2005..
>
> Also, reading the entire history of this forum (should be 120 days of
> history available on the server) will offer significant insight into the
> several and various issues you might encounter during the process.
>
> If you have specific questions along the way -- feel free to ask!
>
> --
> 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- Hide quoted text -
>
> - Show quoted text -