<processModel>

[Matt Sollars]

Hi, all. I was recently told about changing the <processModel> tag in the
machine.config to allow the ASP.NET worker process to run as a system user.
It was supposed to clear up a problem I was having. I didn't want to do this
on a production server due to the security risks involved, but I did test
the theory on my local development machine. The problem went away, as
promised. However, I am now stuck with that change.

I reverted the <processModel> userName attribute back to "machine". I
restarted IIS. Yet, ASP.NET still runs as a system user. I can even write to
a file on the root of the C-drive from a web page. I've rebooted the
computer as well. Still, my web apps have full priviledges.

Can anyone tell me how I can revert my computer back to using the machine
(ASPNET) user account, as it once did?

Thank you in advance.

--
Matt Sollars
(e-mail address removed)
-------------------
The Hypersite Network
2002 N. Salisbury Blvd.
Suite C
Salisbury, Maryland 21801
T: 410.749.2000
F: 410.219.3400
http://www.hypersite.net

 

[Chris Jackson]

You may need to kill off the aspnet_wp process, which is independent of IIS,
in order to get the changes to "take."

 

[Matt Sollars]

Hi, Chris:

Thanks for the reply.

Shouldn't rebooting the computer (several times) take care of that?

Matt

You may need to kill off the aspnet_wp process, which is independent of IIS,
in order to get the changes to "take."

--
Chris Jackson
Software Engineer
Microsoft MVP - Windows XP
Windows XP Associate Expert
--

 

[MS News \(MS ILM\)]

Are you sure you are modifying the correct machine.config ??
YES: If you have two frameworks 1.0 and 1.1 then each framework will have
its own machine.config.
check that out
is it cached?
doublicate your machine.config and name the old one xxxmachine.config
rename the Copy of machine.config to machine.config
what happens??

 

[Ken Cox [Microsoft MVP]]

I've seen people mistake the syntax comments about processModel for the actual
node. Not saying you changed it back in the wrong place, but it might be worth
a check. Also, if you're running .Net 1.0 and 1.1 you'll want to be sure you
dealing with the correct machine.config each time.


--
Microsoft MVPs have a question for *you*: Are you patched against the Worm?
http://www.microsoft.com/security/security_bulletins/ms03-026.asp



Hi, all. I was recently told about changing the <processModel> tag in the
machine.config to allow the ASP.NET worker process to run as a system user.
It was supposed to clear up a problem I was having. I didn't want to do this
on a production server due to the security risks involved, but I did test
the theory on my local development machine. The problem went away, as
promised. However, I am now stuck with that change.

I reverted the <processModel> userName attribute back to "machine". I
restarted IIS. Yet, ASP.NET still runs as a system user. I can even write to
a file on the root of the C-drive from a web page. I've rebooted the
computer as well. Still, my web apps have full priviledges.

Can anyone tell me how I can revert my computer back to using the machine
(ASPNET) user account, as it once did?

Thank you in advance.

--
Matt Sollars
(e-mail address removed)
-------------------
The Hypersite Network
2002 N. Salisbury Blvd.
Suite C
Salisbury, Maryland 21801
T: 410.749.2000
F: 410.219.3400
http://www.hypersite.net