Upgrading from WSUS 2.0 to 3.0SP1 including Server Migration Quest

Hi Guys

I have read everything I could get my hands on regarding upgrading to WSUS
3.0SP1 from version 2.0

Current server is Windows 2000 with WSUS 2.0, one replica server same OS and
WSUS version. Caveats, the database information needs to be kept, for reports
etc.

So I can't update to WSUS 3.0SP1 unless I have W2K3 sp1. So I have come up
with the following plan, which I think in theory will work. I haven't tried
it in the test lan yet. I'd appreciate any feedback.

High level steps
1. Backup the WSUS 2.0 database to a file and import into MS SQL 2005 Server
and set permissions as documented
2. Build 2 new W2K3 servers.
3. Copy the WSUS content to the new master server
4. Install WSUS 3.0sp1 on the new master server pointing it to the database
on the MS SQL 2005 server.
5. Install WSUS on the second server and make replica.
6. Test on small group of pcs
7. Update GPOs and stop Update Services on old servers.

Will this work?
Questions I have.
1. What impact will/could there be from the WSUS Server ID in the
database..duplicate on 2 master servers until the old system is shutdown. The
only information on this relates to duplicate IDs on downstream servers,
which I won't have.
2. Will the WSUS 3.0sp1 installation update the database keeping the update
information and settings?
3. Will the database have information on the old replica server? Can this be
cleaned out?

I hope I have included enough information.

Cheers

Cherie

Cherie wrote:

> I have read everything I could get my hands on regarding upgrading to WSUS
> 3.0SP1 from version 2.0
>
> Current server is Windows 2000 with WSUS 2.0, one replica server same OS and
> WSUS version. Caveats, the database information needs to be kept, for reports
> etc.

> 1. Backup the WSUS 2.0 database to a file and import into MS SQL 2005 Server
> and set permissions as documented
> 2. Build 2 new W2K3 servers.
> 3. Copy the WSUS content to the new master server
> 4. Install WSUS 3.0sp1 on the new master server pointing it to the database
> on the MS SQL 2005 server.

I suspect that WSUS 3 won't realise that the database you're pointing it to is a
WSUS 2 database and needs to be upgraded.

It would be safer to install WSUS 2 on a new server, importing the database and
content, then perform an in-place upgrade.

Do you need a backend database? In most environments, particularly in WSUS 3,
the local database is all you need. Check the WSUS 3 deployment guide.

> 1. What impact will/could there be from the WSUS Server ID in the
> database..duplicate on 2 master servers until the old system is shutdown.

Shouldn't cause a problem.

> 2. Will the WSUS 3.0sp1 installation update the database keeping the update
> information and settings?

See above.

> 3. Will the database have information on the old replica server? Can this be
> cleaned out?

I'm not sure about this.

One other approach you could try would be to install a new WSUS 2 replica server
on a Windows 2003 machine, then upgrade the replica to WSUS 3 and turn it into a
master. I'm not sure whether this will work but a failed attempt shouldn't
cause any damage.

Harry.

"Cherie" <Cherie@discussions.microsoft.com> wrote in message
news:F9017D01-6CC6-4D58-8939-20EECA080098@microsoft.com...

> Hi Guys
>
> I have read everything I could get my hands on regarding upgrading to WSUS
> 3.0SP1 from version 2.0
>
> Current server is Windows 2000 with WSUS 2.0, one replica server same OS
> and
> WSUS version. Caveats, the database information needs to be kept, for
> reports
> etc.
>
> So I can't update to WSUS 3.0SP1 unless I have W2K3 sp1. So I have come up
> with the following plan, which I think in theory will work. I haven't
> tried
> it in the test lan yet. I'd appreciate any feedback.
>
> High level steps
> 1. Backup the WSUS 2.0 database to a file and import into MS SQL 2005
> Server
> and set permissions as documented

Don't do this. But you're close on the idea. :-)

> 2. Build 2 new W2K3 servers.
> 3. Copy the WSUS content to the new master server
> 4. Install WSUS 3.0sp1 on the new master server pointing it to the
> database
> on the MS SQL 2005 server.
> 5. Install WSUS on the second server and make replica.
> 6. Test on small group of pcs
> 7. Update GPOs and stop Update Services on old servers.

> Will this work?
> Questions I have.
> 1. What impact will/could there be from the WSUS Server ID in the
> database..duplicate on 2 master servers until the old system is shutdown.

None directly.. except that your copied database won't be updated by the
clients still pointing at the old server.

> 2. Will the WSUS 3.0sp1 installation update the database keeping the
> update
> information and settings?

Maybe...

> 3. Will the database have information on the old replica server?

Yes.

> Can this be cleaned out?

Yes.


Having said all of that... Harry has provided you with two possible
solution, either of which are better than moving around databases outside
the scope of a WSUS installation/upgrade.

The third option that Harry didn't mention is a bit more complicated but
also a possibility.

[1] Upgrade your Windows 2000 system to Windows Server 2003 (you can use an
EVALUATION copy to do this; it's a temporary step).
See http://wsusinfo.onsitechsolutions.com/articles/022.htm for details
on how to best accomplish this upgrade on a WSUS Server.

[2] Verify your existing WSUS 2.0 server is working on Win2003.

[3] Upgrade the WSUS 2.0 server to WSUS 3.0.

[4] Install a new WSUS 3.0 server on your new hardware as a replica of the
server upgraded in [3].

[5] Convert the =new= server from a replica back to a master, after
synchronization is fully complete.

[6] Retire the server upgraded in [3].

[7] Install your new replica.


--
Lawrence Garvin, M.S., MCBMSP, MCTS(x4), MCP
Senior Data Architect, APQC, Houston, Texas
Microsoft MVP - Software Distribution (2005-2008)

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/pro...awrence.Garvin