Upgrade from WSUS 1.0 to 3.0 smauro 6/3/2007 11:54:00 PM My company is currently running wsus 1.0 I want to upgrade to 3.0 the wsus 1.0 installattion is running SQL 2000 SP4. CAn I still use SQL 2000 SP4 or do I need to upgrade to SQL 2005?

Re: Upgrade from WSUS 1.0 to 3.0 "Lawrence Garvin \(MVP\)" <onsitech[ at ]community.nospam> 6/4/2007 12:20:48 AM "smauro" <smauro[ at ]discussions.microsoft.com> wrote in message news:E67275C5-CFDC-4F0A-95B3-8DB9A038C6A4[ at ]microsoft.com... [Quoted Text] > My company is currently running wsus 1.0 I want to upgrade to 3.0 > > the wsus 1.0 installattion is running SQL 2000 SP4. CAn I still use SQL > 2000 SP4 or do I need to upgrade to SQL 2005? Despite my confusion over whether you mean /SUS/ v1.0 or /WSUS/ v2.0, the key point is that WSUS v3 requires some edition of SQL 2005. Assuming you did not mean /SUS/ (which is the v1.0 product), and did mean /WSUS/ (which is actually a v2.0 product), then if you're currently using a licensed version of SQL 2004 SP4 on a single-server deployment, the WSUS v3 installer will automatically install the Windows Internal Database and migrate your WSUS database to the Windows Internal Database. If you're running SQL 2000 SP4 on a back-end server, then you'll need to manually upgrade the SQL 2000 installation to whatever edition of SQL 2005 you plan to use on the back end. There are a couple of ways you can approch such an upgrade: [a] Uninstall WSUS on the backend; Uninstall SQL 2000. Reinstall SQL 2005 and attach the WSUS database. Install WSUS v3. or [b] Upgrade the SQL 2000 installation to SQL 2005 using the documented "upgrade SQL Server" procedures. Install WSUS v3. Depending on the size of your deployment, and whether or not you have a licensed edition of SQL Server 2005 to install, you might also opt to move the WSUS database back to the front-end server, and migrate to a single-server deployment using Windows Internal Database. Much of that is probably dependent on why you chose to use SQL 2000 instead of WMSDE with your WSUS v2 deployment. Note also that upgrading to WSUS v3 also requires: [a] Application of WSUS v2 SP1 before upgrading SQL 2000 to SQL 2005. [b] Application of SQL 2005 SP1 before upgrading to WSUS v3. [c] Windows Server 2003 SP1 or later as the OS on both front-end and back-end servers. If you would like to provide some additional detail, I'd be happy to provide some additional commentary on your options. -- 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 .....

Re: Upgrade from WSUS 1.0 to 3.0 "Lawrence Garvin \(MVP\)" <onsitech[ at ]community.nospam> 6/4/2007 2:39:39 AM "Lawrence Garvin (MVP)" <onsitech[ at ]community.nospam> wrote in message news:u3oRS5jpHHA.5092[ at ]TK2MSFTNGP04.phx.gbl... [Quoted Text] > "smauro" <smauro[ at ]discussions.microsoft.com> wrote in message > news:E67275C5-CFDC-4F0A-95B3-8DB9A038C6A4[ at ]microsoft.com... >> My company is currently running wsus 1.0 I want to upgrade to 3.0 >> >> the wsus 1.0 installattion is running SQL 2000 SP4. CAn I still use SQL >> 2000 SP4 or do I need to upgrade to SQL 2005? > If you're running SQL 2000 SP4 on a back-end server, then you'll need to > manually upgrade the SQL 2000 installation to whatever edition of SQL 2005 > you plan to use on the back end. There are a couple of ways you can > approch such an upgrade: > [a] Uninstall WSUS on the backend; Uninstall SQL 2000. Reinstall SQL > 2005 and attach the WSUS database. Install WSUS v3. > or > [b] Upgrade the SQL 2000 installation to SQL 2005 using the documented > "upgrade SQL Server" procedures. Install WSUS v3. A couple of corrections/enhancements to the above (which also points out the importance of following =documented= procedures, not what I, or somebody else, might write in a message in this forum). [1] Do not install WSUS v3 on the back-end under any circumstances. [2] Uninstalling SQL Server 2000 prior to installing SQL Server 2005 SP1 requires that you *detach* the WSUS database from the SQL Server 2000 instance prior to uninstalling SQL Server 2000. For this reason, it's probably better to use option [b]. Since the WSUS v3 installation procedure will require you to uninstall WSUS v2 on the back-end server (a critical detail which I had forgotten when I wrote [a] and [b] above), the *best* option is really a hybrid of the two noted above: [a] Uninstall WSUS on the backend (required). [b] Upgrade SQL Server 2000 to SQL Server 2005 SP1 (required). [c] Install WSUS v3. (NOTE: WSUSv3 is only installed on the front-end server; there is no longer a requirement to run the installer on the back-end server.) [d] Follow the instructions in the WSUS v3 Deployment Guide, Appendix B, to configure the front-end server to work with the SQL Server 2005 SP1 back-end 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 ..... > > Despite my confusion over whether you mean /SUS/ v1.0 or /WSUS/ v2.0, the > key point is that WSUS v3 requires some edition of SQL 2005. > > Assuming you did not mean /SUS/ (which is the v1.0 product), and did mean > /WSUS/ (which is actually a v2.0 product), then if you're currently using > a licensed version of SQL 2004 SP4 on a single-server deployment, the WSUS > v3 installer will automatically install the Windows Internal Database and > migrate your WSUS database to the Windows Internal Database. > > > Depending on the size of your deployment, and whether or not you have a > licensed edition of SQL Server 2005 to install, you might also opt to move > the WSUS database back to the front-end server, and migrate to a > single-server deployment using Windows Internal Database. Much of that is > probably dependent on why you chose to use SQL 2000 instead of WMSDE with > your WSUS v2 deployment. > > Note also that upgrading to WSUS v3 also requires: > [a] Application of WSUS v2 SP1 before upgrading SQL 2000 to SQL 2005. > [b] Application of SQL 2005 SP1 before upgrading to WSUS v3. > [c] Windows Server 2003 SP1 or later as the OS on both front-end and > back-end servers. > > If you would like to provide some additional detail, I'd be happy to > provide some additional commentary on your options. > -- > 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 > .... > >