Home
.. About WSUS Wiki

WSUS
.. WSUS FAQ
.. WSUS on SBS
.. WSUS Troubleshooting
.. WSUS News Groups
.. Known WSUS Issues
.. WSUS Links
.. WSUS Wish List

WSUS Documents
.. WSUS Deployment Guide
.. WSUS Installation Guide
.. WSUS Release Notes
.. WSUS Best Practice

SUS
.. SUS FAQ
.. What Is SUS
.. SUS Troubleshooting
.. SUS Links
.. SUS Known Issues
.. SUS FAQ
.. What Is SUS
.. SUS Troubleshooting
.. SUS Links
.. SUS Known Issues

A common request is for the ability to use a SQL cluster for the WSUS back-end.  Although this is not officially supported, the following steps have been performed by one of our customers and appear to work without problems.  The steps below essentially document how to move the WSUS database from one SQL server to another, without running the WSUS installer for the SQL back-end.  Feel free to play around with and refine these steps, but please be forewarned that this is not officially supported!

1. Follow the instructions from "Deploying Microsoft Windows Server Update Services" for installing a Front End/Back End configuration (Appendix C, Page 99) using the "real" Front End IIS server and a temporary SQL server. Stop at "Step 3: Configure the Front-end Computer to Use the Back-end Computer".
2. Detach the SUSDB database from the temp SQL server.
3. Copy the Database and Log files from the Temporary SQL Servers data directory to the SQL Data directory of the production server.
4. Attach the SUSDB database to the Production SQL server.
5. Add the Front End computer domain account as a new user to the SUSDB database with the same Database Roles as the WSUS Administrators group.
6. Remove the WSUS Adminstrators group from the database that points at the temporary SQL server.
7. Now complete "Step 3: Configure the Front-end Computer to Use the Back-end Computer" of changing the registry value and restarting the update service on the Front End computer.
   

=====================
This posting is provided "AS IS" with no warranties, and confers no rights.
=====================