• This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn more.

user accounts

seanicca

VIP Member
VIP Member
Joined
Dec 6, 2005
Messages
2,235
Likes
26
#1
reformatted my pc and installed sp3, now when i start pc i have to log on to my account which never happened before, when i looked in user accounts there is an account called ASP.NET machine A.. i went to delete and windows asked if i wanted to save settings, files etc, i wasnt sure if it was safe to or not, so want to ask if anyone knows what this account is and is it safe to delete??
 

seanicca

VIP Member
VIP Member
Joined
Dec 6, 2005
Messages
2,235
Likes
26
#3
dont know why i didnt think of it before but googled it and found this


What is this new user account for? What created it?

The aspnet_wp or ASP.NET Machine Account is created when the Microsoft .Net Framework 1.1 is installed onto a Windows XP computer. The user is created to run the asp.net worker process used in Microsoft's Internet Information Services, which allows ASP.net to run on your local web server (This is pretty much its only use, it is not used to run normal .net managed executables). There is not a need to worry about this user's presence; it was not created in malicious way.

ASP.net is a programming framework built on the common language runtime (Microsoft .net framework) which can be used on a server to build powerful Web applications. For more information on ASP.net see here


Why does it need another User Account?

Another user account is created for the ASP. Net Worker Process (Aspnet_wp.exe) so that it is not running with administrator privileges. This helps to increase security because if there was a breach the worker process is running as a lowly restricted user rather than having administrator privileges on the local machine. The big complaint with there being another user created is that when it is created it will prevent auto logon had there previously only been one user on the computer.

This can easily be corrected on the first version of the .Net Framework v1.1 by downloading the following registry file which fixes the problem by adding ASPNET to the special accounts list. To do this manually rather than using my file, go to Start > Run and type in regedit. Then create a new DWORD called ASPNET under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\SpecialAccounts\UserList. There is also another manual method which can correct this issue by having the user specify which account should be used for automatic logon (see here for details).

In September 2004 Microsoft released Service Pack 1 for version 1.1 of the .Net Framework, the automatic logon issue was corrected along with further security enhancements, and full support for Windows XP Service Pack 2. To download Service Pack 1 for the framework click here (10.2Mb Download).


Can I delete it?

You can remove this account, but it is vital if you do asp.net development work on your machine.
By removing the account you may find your ASP.net projects will no longer function correctly.

It is possible to recreate the user by issuing the following command from the run dialog (changing the framework version number as appropriate)
%systemroot%\Microsoft.NET\Framework\v1.1.4322\aspnet_regiis.exe /i

just downloaded the registry fix and all back to normal now

cheers
 
Joined
Jul 10, 2007
Messages
6,926
Likes
65
#4
thing is though, in SP3 you wont get that version of .Net - you should get 2.0 or possibly 3.5.
 

seanicca

VIP Member
VIP Member
Joined
Dec 6, 2005
Messages
2,235
Likes
26
#5
thing is though, in SP3 you wont get that version of .Net - you should get 2.0 or possibly 3.5.
just checked add or remove in control panel and i have 1.1, 2 & 3 not sure what any of them are for so i'll leave them as they are all seems ok now
 
Joined
Jul 10, 2007
Messages
6,926
Likes
65
#6
something doesnt seem right about all that to me.

I have never used XP with SP3, but I know under SP2 I would only ever see things like this if there was a problem.
 

little_pob

Jnr admin
Staff member
Jnr Admin
Joined
Dec 10, 2004
Messages
8,692
Likes
344
#7
AFAIK its a standard feature from installing .net. Its just that most people have their computers set to use one account by default, and its usually the administrator account. Those who normally use the welcome screen won't notice any change.

To 'fix', log into an admin account - note that it doesn't have to be the admin account - press [Winkey]+[R]. In the run command that opens type 'control userpasswords2' (without the quotes). On the 'Users' tab uncheck the "Users Must Enter A User Name And Password To Use This Computer" box.

When you do the above a dialogue box should appear, type in the user name and password for the account you want XP to log in to, the default is the account you are doing this from.

NB it is highly recommended that you do not use the administrator's account as the main account.
 

nilrem

Member +
Joined
Mar 10, 2005
Messages
921
Likes
8
#8
I always delete the ASP account on all the builds I have done and never had any probs , machine will just boot into XP without having to select an account
 

oneman

VIP Member
VIP Member
Joined
Aug 23, 2007
Messages
7,504
Likes
103
#9
As other people have said, ASP account is realated to .NET, mainly if you are developing .NET code and run the web server on your computer.

Dotnet v1.1, v2, etc are all different and not backwardly compatible. So just because you have say v3.5 (visual studio 2008) you will not be able to run v2 code (visual studio 2005). So basically, yes you are better having the different versions.
 

Jooooles

Inactive User
Joined
Sep 14, 2006
Messages
6,326
Likes
66
#10
Ive wiped a few computers over the last week never seen this problem before always good to read new stuff though
 
Joined
Jul 10, 2007
Messages
6,926
Likes
65
#11
As other people have said, ASP account is realated to .NET, mainly if you are developing .NET code and run the web server on your computer.

Dotnet v1.1, v2, etc are all different and not backwardly compatible. So just because you have say v3.5 (visual studio 2008) you will not be able to run v2 code (visual studio 2005). So basically, yes you are better having the different versions.
.net 3.5 is fine for everything, you wouldnt normally see the previous versions installed. Instead, the earlier frameworks are available to be referenced if needed.

I use XP on my desktop at work, we use .net and none of our machines have this additional account. To check further, I installed the .net 2.0 framework on a laptop I have here running XP home - it did not give me this problem.

I say again, whenever I have seen this behaviour there has been something wrong with the installation.