You know, the only thing I really care about on that machine other then WSUS is
spiceworks. I am going to migrate spiceworks to another machine temporarily and
do a bare metal rebuild of this server and promote it before I put any kind of
additional services on it. Its probably for the best anyway. Thanks for
everyone's help.
James
----- Original Message -----
From: James Kerr
To: NT System Admin Issues
Sent: Tuesday, July 15, 2008 10:41 AM
Subject: Re: WSUS Problem after dcpromo
Looks like this is the source of my problems at the moment. I have given
access to network service with full control of the WSUS, WSUS database and
update services folder. Could this be an SQL problem?
Event ID 18456 Source MSSQL$MICROSOFT##
Login failed for user 'NT AUTHORITY\NETWORK SERVICE'. [CLIENT: <named pipe>]
----- Original Message -----
From: Anatoly Podgoretsky
To: NT System Admin Issues
Sent: Tuesday, July 15, 2008 9:57 AM
Subject: Re: WSUS Problem after dcpromo
You need grant access for Network Service account too.
Create login and add user associated with this login.
IIS connect to SUSDB with this login
Anatoly Podgoretsky
http://www.podgoretsky.com
----- Original Message -----
From: James Kerr
To: NT System Admin Issues
Sent: Tuesday, July 15, 2008 4:42 PM
Subject: Re: WSUS Problem after dcpromo
Not sure what you mean exactly but I am running the Windows Internal
Database service and it is set to logon a local system. Local system has full
control of both the WSUS and update services folder.
----- Original Message -----
From: Ken Schaefer
To: NT System Admin Issues
Sent: Monday, July 14, 2008 9:10 PM
Subject: RE: WSUS Problem after dcpromo
Grant Network Service permission to login to SQL Server.
That shouldn't have been broken by DCPromo, but maybe it's not there
for some reason.
~ Upgrade to Next Generation Antispam/Antivirus with Ninja! ~
~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm> ~
