Re: Network Service Account
- From: "Joe" <jwdaigle@xxxxxxxxxxxxx>
- Date: Thu, 6 Jul 2006 18:56:04 +0800
Sorry to *** in here, but I assume this means that one should not run the
SQL Server process (et al) as Network Service, but rather as a Domain User
with limited priveleges.
Does this have any bearing on the wisdom of what is best for a ASP.Net
application accessing the database? ie, on Server 2003, an ASP.Net
application would run under the identity of Network Service by default.
Whats better, to keep the default or run the application as a limited access
Domain User?
Thanks,
joe
"Sue Hoegemeier" <Sue_H@xxxxxxxxxxxxx> wrote in message
news:15saa2p0ifmd0f7k8m7sfhskna4aam8hp9@xxxxxxxxxx
I've seen it done in another doc before - don't remember
which one. I think more of what they are getting at is that
you do follow using user or domain accounts as the
recommended accounts. If not using local user or domain
accounts and you are using system accounts, Network Service
would be preferred, don't use Local System.
-Sue
On 30 Jun 2006 06:58:38 -0700, "Bob Lanteigne"
<bob.lanteigne@xxxxxxxxx> wrote:
About 25 % down the page "Microsoft recommends that you not use the
Network
Service account for the SQL Server or the SQL Server Agent services.
Local
User or Domain User accounts are more appropriate for these SQL Server
services."
.
- Follow-Ups:
- Re: Network Service Account
- From: Sue Hoegemeier
- Re: Network Service Account
- Prev by Date: Re: Remove/Add BUILTIN\Administrators 2000 sp4
- Next by Date: Re: SQL 2005 - Searching Encrypted SSN
- Previous by thread: Re: Remove/Add BUILTIN\Administrators 2000 sp4
- Next by thread: Re: Network Service Account
- Index(es):