Configuring ASP.NET in a domain environment

The customer's server is upgraded to a domain server and cannot access ASP.NET.

Information, Microsoft Knowledge Base Article - 315158 provides a solution.

Create a user account called ASPUSER on your computer, then add this account to the user group. Note: This account can also be used if you change the password of the ASPNET account created by .NET Framework. You must know the password of this account because you need to add this password to the section in the later step.

Grant the ASPUSER or ASPNET account "as a batch job login" user permission. Make sure this change appears in the Local Security Policy settings. Note: To grant this account "as a batch job login" user permission, you may have to grant this user permission in each of the following security policies (starting from the control panel / management tool): Domain Controller Security Policy

Domain security policy

Local security strategy

Note: You may have to restart the server so that these changes take effect.

Make sure that the ASPUSER or ASPNET account has the right to access all catalogs and files necessary for the ASPNET_WP.EXE process and provide services for the ASP.NET page. For additional information about what permissions must be granted this account, click the article number below to view the article in the Microsoft Knowledge Base:

317012 Info: Process and request logo in ASP.NET

Open the Machine.config file. The path of this file is:% systemroot% / Microsoft.Net / Framework / V1.0.3705 / Config. (1.1 version of the path ::% systemroot% / microsoft.net / framework / v1.1.4322 / config)

In the section of the Machine.config file, change the username and password properties to the name and password of your account you created in the first step. E.g:

UserName = "domainname / aspuser" password = "aspuserpassword"

I use another way: I can use UserName to be SYSTEM. (Via version 1.1)

This may have some security issues.