Have a good one going here...
While attempting to resolve a WSUS 3.0 SP1 issue, a admin started the MS technet blog post about removing manually all of WSUS dated 5 Nov 2008, without knowing what the internal windows database does with SBS. I will run down what he did to this point:
Ran the Windows Installer Cleanup Utility pulling out WSUS and MICROSOFT##SSEE
Ran "net stop mssql$microsoft##ssee
Ran "sc delete mssql$microsoft##ssee
removed some registery keys
Noticed the sharepoint files in the \%windir%\SYSMSI\SSEE\MSSQL\DATA dir and stopped
Good news is this:
1. Server has not been restarted
2. He backed up the registery before making any changes
3. Did not delete any files (so he says)
Can any or all of this be undone?
if so, how can I remount the internal database?
Currently in management studio the sbs\microsoft##ssee database is a white ball not running as well as wsus. The other sql databases are running.
The wsus did not uninstall correctly either as the attempt to install WSUS 3.0 SP2 reported an error that another database existed.