Microsoft .Net Framework

[Greg Maxey]

I just recently installed a software application that required Microsoft
..Net Framework to be installed first.

This has resulted in two additional Documents and Settings folders:
LocalService and NetworkService


What are these for? Can I delete them as I don't ever plan on using either.

 

[Vagabond Software]

I just recently installed a software application that required Microsoft
.Net Framework to be installed first.

This has resulted in two additional Documents and Settings folders:
LocalService and NetworkService


What are these for? Can I delete them as I don't ever plan on using
either.



--

Do not delete them. They are system folders designed to allow .NET
Framework related services, such as the aspnet worker process, to run at
privilege levels other than the standard user and Administrator account. It
is also better to start other server services, such as SQL database process,
with LocalService rather than user account privileges.

carl

 

[=?iso-8859-1?Q?Daniel_Mart=EDn_=5BMVP_Windows=5D?=]

That folders represent two 'special' accounts used by Windows service control manager. You must not delete them.

 

[Greg Maxey]

Thanks (Daniel Martin too).

Well, my computer now seems to take twice as long to shutdown and start up.
Could the .Net thing that I have no use for be the cause? If so I will
remove the software that required it and then can I remove the .Net
application?

 

[logan]

yes, and your welcome...


I choose Polesoft Lockspam to fight spam, and you?
http://www.polesoft.com/refer.html

 

[Vagabond Software]

Thanks (Daniel Martin too).

Well, my computer now seems to take twice as long to shutdown and start
up. Could the .Net thing that I have no use for be the cause? If so I
will remove the software that required it and then can I remove the .Net
application?



--

It's not the .NET Framework that is causing the problem. It could very well
be the application that you installed requiring the .NET Framework. If it
uses an MSDE database or launches some other services in a sloppy manor, it
could account for your increased startup and shutdown times.

I guess you could simply try uninstalling the application, checking the
CurrentVersion\Run hive of the Local Machine registry for odd startup
services, and rebooting to see if your problem still exists.

carl