"Eric Kosh" <> wrote in message
news:...
> Hi
> I working with WSUS 2
> I have installed a new server for WSUS 3
> But before using wsus 3 sp1, I need to transfer some specification for the
> updates.
> To have the same “configuration” of the updates I need to know all the
> update with installation status “mixed” or “not approved”
>
> I’m looking a query sql to answer at my question. Is it possible?
No.
[a] The schemas of the databases are different from WSUS 2 to WSUS 3.
[b] Direct access to the databases of either version is not supported.
[c] Attempting to do what you're considering *will* result in corrupting
one, or both, of those installations.
So, let's back up to the beginning.
The possibilites for migrating WSUS v2 to WSUS v3 have been written about
endlessly over the past two years, and I would imagine a simple websearch
would turn up dozens of discussions about the process -- many of them
authored by me. :-)
Here's a summation of my advice for upgrading WSUS v2 to WSUS v3.
1. If your WSUS v2 server is being synchronized for products, update
classifications, or languages that you do not intent to carry forward to the
WSUS v3 installation (e.g. Windows 2000, SQL 2000, Office XP), you should
consider not trying to migrate content, and simply building WSUS v3 from
scratch.
2. If your WSUS v2 server has not had regular file maintenance performed
(using the WSUSServerDebug.exe tool), then you should seriously consider not
trying to migrate content, and simply building WSUS v3 from scratch.
3. If you're committed to migrating the existing WSUS v2 server to WSUS v3,
here's the best way to approach the situation.
[a] If possible, *upgrade* the existing WSUS v2 server to WSUS v3 in-place.
Of course, this is only possible if the existing WSUS v2 server is already
running on a Windows Server 2003 operating system.
[b] Run the WSUS v3 Server Cleanup Wizard to remove any unneeded metadata
and files from the upgraded server.
[c] Install the new WSUS v3 server as *replica* of the existing (just
upgraded WSUS2->WSUS3) server, and allow it to fully synchronize all
metadata, approvals, and content. Depending on the volume of information on
the original server, this could take overnight, or even over an entire
weekend (copying the update files is the issue here).
[d] Reconfigure the WSUS v3 server as a standalone server. This is a feature
new to WSUS v3 -- the ability to switch between replica and autonomous mode,
on demand.
4. In the event your WSUS v2 server is still running on Windows 2000 Server,
upgrading to WSUS v3 is obviously not an option. In this case, you should
consider using the "Disconnected Server" scenario described in the WSUS v2
Deployment Guide, in combination with the Approval Migration tool contained
in the WSUS v2 API Samples and Tools Kit. It will also require you to
temporarily install your new servers as a WSUS2SP1 server, and then upgrade
it to WSUS v3.
The "Disconnected Server" scenario describes how to replicate the metadata
and content from one WSUS v2 to server to another WSUS v2 server. However,
this procedure does not replicate approvals, and it does not replicate
target groups. You'll have to manually create the necessary target groups on
the new server. Then you can use the Approval Migration tool to migrate the
approvals from the original server to the new server.
Finally, you can upgrade the new server from WSUS2SP1 to WSUS3SP1.
--
Lawrence Garvin, M.S., MCITP:EA, MCDBA
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2009)
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
Similar Threads
Linear Mode
