|
|
Here is my environment running now: WSUS 2.0, SQL 2000, Server 2003 SP2. I
want to move WSUS to a new server running Server 2003 SP2, SQL 2005 with WSUS
3.0. Should I just backup the WSUS database on the SQL2000 server and restore
it on the SQL2005 server and then install WSUS3.0 on the new server? I want
the wsuscontent file to be on d:\wsus\wsuscontent instead of the default
%windir%\wsus\wsuscontent where it is on the old server or should I just
install WSUS3.0 on the new server and point all of my clients to the new
server in Group Policy and let them start new?
--
Thanks
|
|
"Ralphdjr" <Ralphdjr[ at ]discussions.microsoft.com> wrote in message
news:AD1CDDF4-925F-4999-8E4A-FBA6E7AE11BC[ at ]microsoft.com...
[Quoted Text] > Here is my environment running now: WSUS 2.0, SQL 2000, Server 2003 SP2. I
> want to move WSUS to a new server running Server 2003 SP2, SQL 2005 with
> WSUS
> 3.0. Should I just backup the WSUS database on the SQL2000 server and
> restore
> it on the SQL2005 server and then install WSUS3.0 on the new server?
That might work... but then, it might not. I don't know that the WSUS 3
installer will properly see the WSUS 2.0 formatted databases in the SQL 2005
instance, or merely assume that they're already WSUS 3 databases. Failing to
properly convert the schema would be potentially catastrophic.
You have four options, in my perspective
[1] Do an upgrade-in-place to WSUS 3.0 on the existing server, which will
migrate the SQL 2000 SUSDB database into an instance of Windows Internal
Database; install a *replica* WSUS 3.0 server on the new box on your SQL
2005 installation, and then revert it to an autonomous server after the
replication is completed.
[2] Clone the existing WSUS 2.0 server onto the new system (e.g. NTBACKUP),
and do an upgrade-in-place to WSUS 3.0 on the new hardware.
[3] Use the Approvals Migration tool and export the approvals from the WSUS
2.0 database, install the WSUS 3.0 system as a fresh system, and then import
the approvals migration data.
[4] Discard your entire WSUS 2.0 system and build a new WSUS 3.0 system from
scratch.
> I want
> the wsuscontent file to be on d:\wsus\wsuscontent instead of the default
> %windir%\wsus\wsuscontent where it is on the old server
Using option [1], [3], or [4], simply assign D:\WSUS as the location on the
new server.
If you use option [2], you'll either need to make this location migration
*before* initiating any of the upgrade processes, or *after* completing the
upgrade on the new hardware.
> or should I just
> install WSUS3.0 on the new server and point all of my clients to the new
> server in Group Policy and let them start new?
This really is a function of how well the WSUS 2.0 system has been
"maintained" over the past two years, and whether you're going to keep the
same basic configuration as you currently have. For example, if you've never
performed file maintenance on the content store on your WSUS 2.0 system, or
if your baseline installation for WSUS 2.0 was Windows XP SP1 and Windows
Server 2003 RTM, and now your baseline is Windows XP SP2 and Windows Server
2003 SP2, you may benefit from starting from scratch, rather than trying to
'maintain' or 'clean up' all of the legacy (expired/declined) update
metadata and content currently sitting on your WSUS 2.0 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://www.microsoft.com/wsus
And, almost everything else is at
http://wsusinfo.onsitechsolutions.com
.....
|
|
|