Comments on: How to migrate WSUS 3.0 from SQL Express to a remote SQL Server

By: Robert

Robert — Thu, 23 Sep 2010 17:50:00 +0000

as addition to Chris’ post:

7.6 right-click the SUSDB and click Properties
7.7 Select Permissions and highlight your Server account
7.8 Grant permissions.

At least when I followed the article and Chris’ post my SUS server only had Connect access to the database. After granting all of the permissions (dont know which are actually necessary, but it doesnt really matter either) the SUS server management worked again.

By: Steve

Steve — Wed, 30 Sep 2009 11:45:20 +0000

Had an issue moving an SP1 DB to an SP2 installation. The console would not connect after attaching the DB. We applied the windows update that updated our WSUS to SP2 from SP1 on the old server, but apparently applying to SP2 update does not update the DB schema. So after uninstalling and leaving all updates and the DB in place, I reinstalled and it said it would update the DB schema to SP2. After that, it worked sucessfully.

By: Colin

Colin — Tue, 26 May 2009 15:33:22 +0000

the App events didnt tell me much i’m afraid. I have got it working now.

Great article, thanks.

By: Paul

Paul — Tue, 26 May 2009 15:31:22 +0000

Colin, your event log should have entries indicating why it would not start.

By: Colin

Colin — Tue, 26 May 2009 14:13:27 +0000

Followed the steps exactly – wsus wont load after server restart.

By: Chris

Chris — Fri, 24 Apr 2009 16:55:41 +0000

Here’s a slightly more detailed #7:
7.1 Right click “Security”, it’s directly under “Databases” from #6. Select New -> Login…
7.2 In “Login name” enter {domain name}\{wsus server}$ (ex, Contoso\wsus01$)
7.3 Select the “User Mappings” page in the upper left
7.4 Check the box next to SUSDB database, under the Default Schem column enter “dbo”
7.5 Click OK

This should be good for most simple installs. This is a bit insecure, as any application on the WSUS server can write anything to the database. If you have anything complicated going on contact a real DBA, and implement real security measures.

By: Paul

Paul — Sun, 19 Apr 2009 12:00:18 +0000

Hi markc, the machine login is added using the SQL management console. Here is a Technet article explaining the general steps:

http://technet.microsoft.com/en-us/library/aa337562.aspx

By: markc

markc — Sun, 19 Apr 2009 11:01:00 +0000

Yes I’m also struggling on step 7. It appears all the ms docs assume knowledge here, as does the above article. Where is this machine login added? Please elaborate with screenshots!

By: Paul

Paul — Fri, 14 Nov 2008 01:38:05 +0000

Hi Philip, you can create a login for a computer account by typing the computer name into the “Login name” field directly, instead of searching for it.

So for example, to add a login for the computer account WSUSSERVER in the domain LAB, you would type LAB\WSUSSERVER$ into the “Login name” field.

Hope that helps.

By: Philip Smth

Philip Smth — Wed, 12 Nov 2008 16:48:41 +0000

This is so helpful – but would you clarify point 7 please? I believe I’m failing in this step (and I’m not an SQL guy…).

I’m trying to add a computer account to the security\logins group in SQL 2005 SP2, but I can only add user, group, or built-in security principal, no computer.