Path:
eternal-september.org!reader02.eternal-september.org!feeder.eternal-september.o
rg!.POSTED!not-for-mail
From: Paul 
Newsgroups: microsoft.public.windowsxp.general
Subject: Re: msconfig
Date: Wed, 15 Nov 2017 00:38:43 -0500
Organization: A noiseless patient Spider
Lines: 69
Message-ID: 
References: 
 
 
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Injection-Date: Wed, 15 Nov 2017 05:38:44 -0000 (UTC)
Injection-Info: reader02.eternal-september.org;
posting-host="97aeaa592f71f78b07aa84e71500f94e";
 logging-data="21253";
mail-complaints-to="abuse{at}eternal-september.org";
posting-account="U2FsdGVkX1/+w85+mPCoWZgb5O7lQtjQJDjq4Uw9JqM="
User-Agent: Ratcatcher/2.0.0.25 (Windows/20130802)
In-Reply-To: 
Cancel-Lock: sha1:GD06WUkYek6i5mq3CAJW7Wwg+rk=
Xref: feeder.eternal-september.org microsoft.public.windowsxp.general:134544

J. P. Gilliver (John) wrote:
> In message , Paul
 
> writes:
>> J. P. Gilliver (John) wrote:
> []
>>>  I have "Administrator", "ASPNET", and
"me"; Administrator and me are 
>>> in  "Administrators" group, and ASPNET is in
"Users" group. Any idea 
>>> what  ASPNET might be?
>>
>> https://support.microsoft.com/en-us/help/555299#!en-us%2Fhelp%2F555299
>>
>>   "ASP.NET Machine Account is created when the [.net] 1.1
>>    is installed onto a Windows XP machine."
>>
>>   "If one works with asp.net development work then he/she
>>    must keep that account, otherwise ASP.net projects will
>>    no longer function correctly."  [Oh,my]
>>
>> It's something most people won't be using.
>>
>>   Paul
> 
> Thanks. Is it likely to do any _harm_ if I just ignore it?

It's supposed to be a limited account. I suspect it might be used,
if your machine was running Microsoft IIS web server (a Windows Features
option you can turn on in some flavor of WinXP). Then, you'd be
writing some sort of code to communicate with a web browser
on another machine.

"How To: Use the Network Service Account to Access Resources in ASP.NET"

https://msdn.microsoft.com/en-us/library/ff647402.aspx

And it doesn't appear to be related to the Framework Assistant
that got plunked into Firefox by some .net install. I see ClickOnce
related questions with respect to this, and nothing else.

https://support.microsoft.com/en-us/help/963707/how-to-remove-the-net-framework
-assistant-for-firefox#!en-us%2Fhelp%2F963707%2Fhow-to-remove-the-net-framework
-assistant-for-firefox

And this gives a hint how asp.net works. It's a server side
technology.

https://stackoverflow.com/questions/21462869/does-client-machine-need-net-insta
lled-to-run-asp-net-web-application

    ".Net framework is required for machines [servers]
     hosting ASP.Net application.

     Client only gets HTML/Javascript/CSS, Stuff which
     client's browser can handle.

     No server side code is executed on client."

That suggests the asp.net account (a limited account) is
only useful if you're a web monkey working on the server,
and you're trying to get your asp.net server code to
write to the Event Log and so on. That's when the code
uses that account to access the machine. It suggests, for the
"average Facebook user" (content consumer), you could
delete that account and never know the difference.

Not that I'm about to try.

The account is probably as dangerous as the Guest account.
By being a separate account, it allows a savvy user to
modify things for that specific account and situation.
And not hijack some other account for that purpose.

    Paul
--- Platinum Xpress/Win/WINServer v3.1