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.



Thanks,



Scott

Please post instructions for installing Visual Studio .NET Architect on

Windows XP Professional with Visual Studio .NET Enterprise Beta 2

installed.



Does this require uninstalling Beta 2 before trying to install the final

release?



Any other tips would be appreciated.



Carl Olsen, MCSE



> -----Original Message-----

> From: Scott Guthrie [mailto:scottgu@m...]

> Sent: Thursday, January 17, 2002 10:04 PM

> To: ASP+

> Subject: [aspx] ASP.NET and Windows Domain Controllers

> 

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

> 

> Thanks,

> 

> Scott

> 

Yes -- you must fully uninstall Beta2 (both Visual Studio and the .NET

Framework) before installing the final release.  This is true for all

Operating Systems.



Hope this helps,



Scott



-----Original Message-----

From: Carl E. Olsen [mailto:carl-olsen@h...]

Sent: Friday, January 18, 2002 5:17 AM

To: ASP+

Cc: Scott Guthrie

Subject: [aspx] RE: ASP.NET and Windows Domain Controllers





Please post instructions for installing Visual Studio .NET Architect on

Windows XP Professional with Visual Studio .NET Enterprise Beta 2

installed.



Does this require uninstalling Beta 2 before trying to install the final

release?



Any other tips would be appreciated.



Carl Olsen, MCSE



> -----Original Message-----

> From: Scott Guthrie [mailto:scottgu@m...]

> Sent: Thursday, January 17, 2002 10:04 PM

> To: ASP+

> Subject: [aspx] ASP.NET and Windows Domain Controllers

>

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

>

> Thanks,

>

> Scott

>

> ---

> Change your mail options at http://p2p.wrox.com/manager.asp or to

> unsubscribe send a blank email to $subst('Email.Unsub').