At 09:03 PM 2/5/2002 +0100, you wrote: > >Wenn Du blank installiert hast, ist das witzig... processModel l�uft > >�blicherweise "machine" oder "SYSTEM", ein eigener Account ist auch > >m�glich. Bei machine und SYSTEM ist der Account vordefiniert, ebenso das > >Passwort. Der Server ist eh' kein DC? > >Auf dem Rechner war bereits ein IIS5 installiert. Was ist mit processModel >gemeint? >Der Server ist ein DC.
Von ScottGu zum Thema ASP.NET am DC: >By default ASP.NET runs the ASP.NET worker process using a >non-adminitrative windows account called "ASPNET". This restricts what >an ASP.NET application can do on a machine -- and requires >administrators to explicitly grant security permissions. > >However, on Windows Domain Controller machines (this includes the >Windows Small Business Server product) the ASPNET account cannot be used >-- since non-administrative local accounts cannot be created and used >(the security policy of a Windows Domain Controller machine prevents >this). > >If you attempt to use the default ASPNET account when running an ASP.NET >page on a Windows Domain Controller, the worker process will fail to >start -- most likely with an error message similar to the one below: > > "aspnet_wp.exe could not be launched because the username and/or >password supplied in the processModel section of the config file are >invalid" > >To fix this, it is necessary to configure ASP.NET to instead use the >LocalSystem account after setup. This is done by modifying the ><processModel> tag within the Machine.Config configuration file >installed in the below location: > > c:\Windows\Microsoft.Net\Framework\V1.0.3705\Config\Machine.Config > >By default you will find that the <processModel> configuration tag has a >"userName" attribute set to the value: "MACHINE". Changing this value >to "SYSTEM" will cause ASP.NET to instead use the LocalSystem account >when executing. This account *does* have permission to run on Windows >Domain Controllers. > >After making the change to the Machine.Config XML file, save it, and >then restart IIS (iisreset). ASP.NET will then be using the LocalSystem >account to run its worker process, and ASP.NET will function fine on >domain controllers. Nach dieser Anleitung hat er dann noch das gepostet: >In general I think it is a pretty bad idea to run IIS/ASP/ASP.NET on a >domain controller. We actually thought it was so rare for people to do >this that we didn't automate this step as part of setup. But from a few >messages I've seen about this issue, it sounds like it actually does >happen ocassionally in the real world (go figure!). Chris | [aspdedotnet] als [email protected] subscribed | http://www.dotnetgerman.com/archiv/aspdedotnet/ = Listenarchiv | Sie k�nnen sich unter folgender URL an- und abmelden: | http://www.dotnetgerman.com/listen/aspDEdotnet.asp
