How to Move WSUS Database From Windows Server 2003 to 2008

I have Windows Server 2003 R2 running WSUS, and am about to replace it with
Windows Server 2008 R2. Rather than install WSUS and have it download all
updates again, I would like to make use of the existing download database.

Is there a way to install WSUS on 2008 and have it 'take over' the WSUS
database? The WSUS database is on the same machine as 2008 is running, so
it's not possible to have 2003 and 2008 running at the same time; 2008 is a
replacement for 2003 on this machine.

TIA

Charles

"Charles" <> wrote in message
news:...
>I have Windows Server 2003 R2 running WSUS, and am about to replace it with
>Windows Server 2008 R2. Rather than install WSUS and have it download all
>updates again, I would like to make use of the existing download database.
>
> Is there a way to install WSUS on 2008 and have it 'take over' the WSUS
> database?

Yes. If you're installing the same version of WSUS, and the database server
is already installed and functioning, you can simply point the installer to
the existing WSUS database.

> The WSUS database is on the same machine as 2008 is running, so it's not
> possible to have 2003 and 2008 running at the same time; 2008 is a
> replacement for 2003 on this machine.

A bit more background on exactly what you've done to get from Win2003R2 with
WSUS to where you are now would help ensure I give you correct advice --
including what database server you were using and are planning to use.


--
Lawrence Garvin, M.S., MCITP:EA, MCDBA
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2009)

My Blog: http://onsitechsolutions.spaces.live.com
Microsoft WSUS Website: http://www.microsoft.com/wsus
My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin

Hi Lawrence

Thanks for the reply. The version of WSUS declares itself to be V3.2.

I have a server with Windows Server 2003 R2 and WSUS on it. I created a
separate partition and installed Windows Server 2008 R2 into that. Before I
wipe 2003 from the disk, I will install the apps I need under 2008,
including WSUS. In so doing, I want to tell the newly installed WSUS to use
the existing WSUS database, and then, eventually, I will wipe 2003 (leaving
the WSUS database behind, of course).

Does that sound reasonable/possible?

Charles


"Lawrence Garvin [MVP]" <> wrote in message
news:758233B1-1ADF-43BC-BA20-...
> "Charles" <> wrote in message
> news:...
>>I have Windows Server 2003 R2 running WSUS, and am about to replace it
>>with Windows Server 2008 R2. Rather than install WSUS and have it download
>>all updates again, I would like to make use of the existing download
>>database.
>>
>> Is there a way to install WSUS on 2008 and have it 'take over' the WSUS
>> database?
>
> Yes. If you're installing the same version of WSUS, and the database
> server is already installed and functioning, you can simply point the
> installer to the existing WSUS database.
>
>> The WSUS database is on the same machine as 2008 is running, so it's not
>> possible to have 2003 and 2008 running at the same time; 2008 is a
>> replacement for 2003 on this machine.
>
> A bit more background on exactly what you've done to get from Win2003R2
> with WSUS to where you are now would help ensure I give you correct
> advice -- including what database server you were using and are planning
> to use.
>
>
> --
> Lawrence Garvin, M.S., MCITP:EA, MCDBA
> Principal/CTO, Onsite Technology Solutions, Houston, Texas
> Microsoft MVP - Software Distribution (2005-2009)
>
> My Blog: http://onsitechsolutions.spaces.live.com
> Microsoft WSUS Website: http://www.microsoft.com/wsus
> My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin
>

"Charles" <> wrote in message
news:O3ZJ$...

> Thanks for the reply. The version of WSUS declares itself to be V3.2.
>
> I have a server with Windows Server 2003 R2 and WSUS on it. I created a
> separate partition and installed Windows Server 2008 R2 into that. Before
> I wipe 2003 from the disk, I will install the apps I need under 2008,
> including WSUS. In so doing, I want to tell the newly installed WSUS to
> use the existing WSUS database, and then, eventually, I will wipe 2003
> (leaving the WSUS database behind, of course).
>
> Does that sound reasonable/possible?

Yes, and thank you for the additional background. (v3.2 is WSUS3SP2).

Since you've created a dual-boot scenario, all of the WSUS content and
databases are still in the original partition. If your ultimate intent is to
wipe the Win2003R2 partition, then we'll need to physically move the content
and databases from the Win2003R2 partition to the Win2008R2 partition.

The first step is to get WSUS3SP2 installed on the Win2008R2 partition
following the procedures documented in Steps 1 thru 4 of the Step By Step
Guide [http://technet.microsoft.com/en-us/l...2(WS.10).aspx], and
verify the basic functionality of the new installation, e.g.
- the WSUS server can synchronize from MU
- the WSUS server can detect/download updates from itself

The next step will be to copy the subfolders of the ~\WSUSContent folder in
the Win2003R2 partition into the ~\WSUSContent folder of the Win2008R2
partition. Only move the SUBfolders, so that the inherited permissions (and
local account SIDs) of the Win2008R2 environment will be properly propagated
to the new subfolders.

Then boot back into the Win2003R2 environment and detach the database from
the database server running in that installation. Procedures for doing this
can be found in the first portion of the Migration from WID to SQL Server
procedures in the WSUS Operations Guide at
[http://technet.microsoft.com/en-us/l...8(WS.10).aspx].

Once the database has been "detached" from the Win2003R2 environment, boot
back into the Win2008R2 environment, and perform the same steps on the newly
created database for the Win2008R2 environment. Move the new (empty)
database off to a safe location to be used as a recovery point if necessary.
Copy the production database files from the Win2003R2 partition to the
Win2008R2 partition, and re-attach the database. You might find it useful to
download and install SQL Server Management Studio Express Edition to assist
in this step.

Your previous Win2003R2 environment should now be fully migrated to your
Win2008R2 environment.

--
Lawrence Garvin, M.S., MCITP:EA, MCDBA
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2009)

My Blog: http://onsitechsolutions.spaces.live.com
Microsoft WSUS Website: http://www.microsoft.com/wsus
My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin

Hi Lawrence

Thanks for the very clear and complete instructions. I shall try this over
the weekend and post back how it goes.

Cheers

Charles


"Lawrence Garvin [MVP]" <> wrote in message
news:6CB02007-E5DA-4173-9B7F-...
> "Charles" <> wrote in message
> news:O3ZJ$...
>
>> Thanks for the reply. The version of WSUS declares itself to be V3.2.
>>
>> I have a server with Windows Server 2003 R2 and WSUS on it. I created a
>> separate partition and installed Windows Server 2008 R2 into that. Before
>> I wipe 2003 from the disk, I will install the apps I need under 2008,
>> including WSUS. In so doing, I want to tell the newly installed WSUS to
>> use the existing WSUS database, and then, eventually, I will wipe 2003
>> (leaving the WSUS database behind, of course).
>>
>> Does that sound reasonable/possible?
>
> Yes, and thank you for the additional background. (v3.2 is WSUS3SP2).
>
> Since you've created a dual-boot scenario, all of the WSUS content and
> databases are still in the original partition. If your ultimate intent is
> to wipe the Win2003R2 partition, then we'll need to physically move the
> content and databases from the Win2003R2 partition to the Win2008R2
> partition.
>
> The first step is to get WSUS3SP2 installed on the Win2008R2 partition
> following the procedures documented in Steps 1 thru 4 of the Step By Step
> Guide [http://technet.microsoft.com/en-us/l...2(WS.10).aspx],
> and verify the basic functionality of the new installation, e.g.
> - the WSUS server can synchronize from MU
> - the WSUS server can detect/download updates from itself
>
> The next step will be to copy the subfolders of the ~\WSUSContent folder
> in the Win2003R2 partition into the ~\WSUSContent folder of the Win2008R2
> partition. Only move the SUBfolders, so that the inherited permissions
> (and local account SIDs) of the Win2008R2 environment will be properly
> propagated to the new subfolders.
>
> Then boot back into the Win2003R2 environment and detach the database from
> the database server running in that installation. Procedures for doing
> this can be found in the first portion of the Migration from WID to SQL
> Server procedures in the WSUS Operations Guide at
> [http://technet.microsoft.com/en-us/l...8(WS.10).aspx].
>
> Once the database has been "detached" from the Win2003R2 environment, boot
> back into the Win2008R2 environment, and perform the same steps on the
> newly created database for the Win2008R2 environment. Move the new (empty)
> database off to a safe location to be used as a recovery point if
> necessary. Copy the production database files from the Win2003R2 partition
> to the Win2008R2 partition, and re-attach the database. You might find it
> useful to download and install SQL Server Management Studio Express
> Edition to assist in this step.
>
> Your previous Win2003R2 environment should now be fully migrated to your
> Win2008R2 environment.
>
> --
> Lawrence Garvin, M.S., MCITP:EA, MCDBA
> Principal/CTO, Onsite Technology Solutions, Houston, Texas
> Microsoft MVP - Software Distribution (2005-2009)
>
> My Blog: http://onsitechsolutions.spaces.live.com
> Microsoft WSUS Website: http://www.microsoft.com/wsus
> My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin
>

I performed the following...

stopped related services to WSUS

copied WSUS directory to new location.

De-installed WSUS, leaving the content and database in place.

Reboot

Install WSUS pointing content and database to new location.

Verify update & synchronization, then delete old directory location.