re:
!> Unfortunately, the method of changing asp_wp.exe identity described on
!>
http://msdn2.microsoft.com/en-us/library/dwc1xthy(vs.80).aspx does not work.
Yes, it does work. I've helped many people set up accounts using those instructions.
You can safely ignore the Application Pool instructions, since W2K doesn't use them.
re:
How can I change the identity of asp_wp.exe (Asp.Net 2.0) process on Windows 2000 Server from
ASPNET to LocalSystem?
Are you sure you don't mean the SYSTEM account ?
Besides impersonating the user, per the article :
<system.web>
<processModel enable="true"
userName="System" />
</system.web>
The "System" account doesn't need a password.
Also, that only works in machine.config, not in web.config.
I'd avoid impersonating the ASP.NET process account in machine.config.
You should do it, for a particular application, in web.config :
<identity impersonate="true" userName="accountname" password="password" />
See:
http://support.microsoft.com/default.aspx/kb/306158
Additionally, run
aspnet_regiis -ga "MachineName\Account"
Additionally, make sure the following ACLs are set :
http://msdn2.microsoft.com/en-us/library/kwzs111e(VS.80).aspx
Also, you don't have to run ASP.NET as the SYSTEM account. In fact, you should *avoid* it.
You can run ASP.NET as *any* account you want to, provided you assign the correct permissions.
If you want to go that way ( and you should ), follow the instructions at :
http://msdn2.microsoft.com/en-us/library/ms998297.aspx
....*and* run the steps detailed above.
Juan T. Llibre, asp.net MVP
asp.net faq :
http://asp.net.do/faq/
foros de asp.net, en español :
http://asp.net.do/foros/
===================================