PDA

View Full Version : Asp.Net Machine A...'s (new account on my computer?)

acr1965
March 16th, 2007, 10:42 PM
Where did this come from? Is it from one of those .NET Framework updates? I go to check my admin account and this is on the menu...some pic of a karate guy and listed as a limited account and password protected. I am the only person who has ever had access to this machine. And as admin, it looks like I can change it if I wish. Is it safe to delete this? Is the password the same as my admin account password? I never created this limited account named ASP.Net Machine A...'s account. And this is the first time it has appeared on my computer that I have seen.
nick s
March 16th, 2007, 11:09 PM
-{ Quote: "Where did this come from? Is it from one of those .NET Framework updates? I go to check my admin account and this is on the menu...some pic of a karate guy and listed as a limited account and password protected. I am the only person who has ever had access to this machine. And as admin, it looks like I can change it if I wish. Is it safe to delete this? Is the password the same as my admin account password? I never created this limited account named ASP.Net Machine A...'s account. And this is the first time it has appeared on my computer that I have seen." }-I don't remember at what stage of the Windows .net rollouts that the asp.net account gets created, but it is safe to delete.

Nick
acr1965
March 16th, 2007, 11:17 PM
Thanks for the info. But what is the purpose of it? It seems like M$, and all their "security" issues would let someone know if new accounts are being created on their machine.
nick s
March 16th, 2007, 11:39 PM
From What is this new user account for? What created it? (http://www.mvps.org/marksxp/WindowsXP/aspdot.php):

"...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..."

Nick