Question on upgrading to 3.0 [WiredBox.Net

>I am currently running WSUS 2.0 using an external SQL 2000 server. I want
>to
> upgrade to WSUS 3.0. We do not have a SQL 2005 server, so I assume I need
> to
> go back to Internal database

> "Hollie" <Hollie[ at ]discussions.microsoft.com> wrote in message
> news:F33DB2E9-94B1-4311-82E2-12A69F2C52FD[ at ]microsoft.com...
> >I am currently running WSUS 2.0 using an external SQL 2000 server. I want
> >to
> > upgrade to WSUS 3.0. We do not have a SQL 2005 server, so I assume I need
> > to
> > go back to Internal database
>
> Yep. :-)
>
> > What would be the best procedure for upgrading.
>
> Hmmm... that's an ugly scenario no matter which way you spin it.
>
> > I want to use the same server, and was going to uninstall 2.0
> > first, but was not sure of the correct order to follow.
> > Any help would be appreciated!
>
> Here's a couple of possible scenarios. A critical component of this decision
> making process is *WHY* you're using a back-end server right now with WSUS
> SP1. If you'd doing it "just because it was there", then there's not much of
> an issue proceeding. But, if you were doing it because your front-end server
> didn't have the necessary resources to handle the load, then it's arguable
> whether it would using WSUS3/WID or not.
>
> First option is to upgrade (or install side-by-side) SQL Server 2005 Express
> Edition SP1 on the back-end server. Migrate the WSUS database from SQL
> Server 2000 to SQL Server 2005 Express Edition SP1. Reconfigure WSUS 2.0 to
> use the SQL Server 2005 instance. Uninstall WSUS 2.0 from the back-end
> server. Upgrade the front-end server to WSUS 3.0, which will automagically
> find the back-end SQL Server 2005 Express Edition SP1 installation.
>
> Second option is to uninstall WSUS from the front-end server, reinstall WSUS
> 2 SP1 as a single-server, and then migrate the SQL Server 2000 databases to
> WMSDE. But this can be problematic, if not impossible, because SQL 2000 (and
> SQL 2005) are designed to support migration *from* WMSDE to SQL Server 2000,
> but not back the other way. So, avoid this option, unless it's your *only*
> option, and even then it may not be an option. See the Knowledge Base for
> explicit documentation on the issues and procedures for downgrading a SQL
> Server 2000 database to MSDE/WMSDE.
>
> Third option is to uninstall WSUS from the front-end server, install SQL
> Server 2000 on the front-end server, and then reinstall WSUS 2 SP1 as a
> single server using SQL 2000. Then migrate the WSUS database from the
> back-end server to the front-end server. Finally, perform an in-place
> upgrade from WSUS 2 to WSUS 3, which will automagically convert your SQL
> Server 2000 WSUS database to the Windows Internal Database. Following the
> upgrade, uninstall SQL Server 2000. (Hint: If you're particularly religious
> about licensed software, or you have an organizational policy that strictly
> prohibits installation of unlicensed software, you can use an EVAL Edition
> of SQL Server 2000 to achieve this objective, since the SQL Server 2000 will
> only be installed for a few hours.)
>
>
> Whether you choose option one or option three really depends on your
> particular environment and whether WID on the single-server deployment is a
> better performance solution than SQL Server 2005 Express Edition on a
> back-end server. Cecil may have some thoughts on these two scenarios.
> Personally, I'd avoid the Express Edition on the back-end server unless WID
> on the single-server simply isn't a functional solution. (In which case, SQL
> Express on the back-end probably isn't going to be much better, either!)
>
> So, unless I think of another methodology, my choice would be option #3.
>
>
> --
> 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
> .....
>
>
>
>

> Thank you for your suggestions, very helpful. We used the SQL 2000
> back-end
> server only because we had it, no resource issues.
> If we were not concerned so much about upgrading the database, and are
> fine
> with a new install of wsus 3.0, would I just uninstall wsus 2.0 on the
> front-end server?

> "Hollie" <Hollie[ at ]discussions.microsoft.com> wrote in message
> news:1B1A7388-B2BC-47BB-9274-60804BD88063[ at ]microsoft.com...
> > Thank you for your suggestions, very helpful. We used the SQL 2000
> > back-end
> > server only because we had it, no resource issues.
> > If we were not concerned so much about upgrading the database, and are
> > fine
> > with a new install of wsus 3.0, would I just uninstall wsus 2.0 on the
> > front-end server?
>
> It's not really a choice. The database server *must* be upgraded to some
> edition of SQL 2005. With SQL 2000 installed on the back-end, you really
> only have two options. Upgrade the back-end, or migrate the database to the
> front-end, and then upgrade it.
>
> Uninstalling WSUS 2 on the front-end server would only be necessary in the
> 'not recommended' scenario of trying to migrate the database from SQL 2000
> down to WMSDE on the front-end server. In this case, uninstalling is
> required, because the only way you can get the WMSDE server installed is by
> installing WSUS 2.0.
>
> > And when uninstalling do I check the boxes to remove
> > everything, database and logs.
>
> NO. The content is reusable no matter what. And you definitely don't want to
> remove the databases, because you need to detach/attach the database from
> the back-end server to the front-end server after the WSUS re-installation
> is completed.
>
> > I realize I will need to set everything up
> > again, but it is a very simple wsus server and seems that it might take
> > less
> > time to do that, than try going through all of the steps to upgrade the
> > database.
>
> If you're talking about building a complete WSUS 3.0 server from scratch,
> and totally abandoning your existing WSUS 2.0 databases, that's certainly
> another option. It won't matter whether you remove the database or not,
> since the WSUS 3.0 installer won't know where to look for the database
> unless it's doing an upgrade of an installed WSUS 2.0 server. However,
> there's no need, nor point, in removing the content directories. The content
> directory is version independent, and can be 100% reused.
>
> [1] Uninstall WSUS 2.0, including logs, but not the content. (The database
> doesn't matter.)
> [2] Install WSUS 3.0, which, not finding a database server installed and not
> finding a WSUS 2.0 installed, will prompt you to select:
> [a] To install Windows Internal Database, or
> [b] Connect to a back-end database server.
>
> --
> 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
> .....
>
>
>