"Bilbo fake rubbish.domain.org>" <wlp<fauxat> wrote in message
news:...
> I'm planning on migrating SBS2K3 SP2 + WSUS 3.0 SP1 to new hardware.
> I'm planning to do a SWING migration but that doesn't cover WSUS.
>
> Is there any reason to worry with migrating any WSUS data? Can't I
> simply install it on the new SBS and let it take over from there?
Unless you have a complex group heirarchy or complex approval schemes, it's
probably simpler to just reinstall WSUS after the migration and reset your
approvals.
However, you *can* migrate the WSUS from the old machine to the new machine,
and it's not that difficult:
1. Install a new WSUS on the new server. Cancel out of the post-setup
wizard.
2. Copy the subfolders of ~\WSUSContent from the old server to the new
server.
3. Detach the SUSDB from the new server. Move the database files to a "save"
folder.
4. Detach the SUSDB from the old server and copy it to the new server.
5. Attach the original SUSDB on the new server.
and, if the physical pathname of the content on the new server is different
from the original server, then you'll also need to run 'wsusutil movecontent
<logfile> -skipcopy' to reset the pointers to the correct pathname of the
new location.
--
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 MVP Profile:
http://mvp.support.microsoft.com/pro...awrence.Garvin