Microsoft KB Archive/324393

= How to install the .NET Framework on a cluster =

Article ID: 324393

Article Last Modified on 3/13/2007

-

APPLIES TO


 * Microsoft Internet Information Services 5.0
 * Microsoft .NET Framework 2.0
 * Microsoft .NET Framework 1.1
 * Microsoft .NET Framework 1.0

-



This article was previously published under Q324393



SUMMARY
This step-by-step article describes how to install the Microsoft .NET Framework in a Microsoft Cluster Service (MSCS) configuration to run ASPX pages or Microsoft ASP.NET applications.

This article assumes that you already have Microsoft Internet Information Services (IIS) installed and working on your clustered servers.

For more information about how to cluster IIS, click the following article number to view the article in the Microsoft Knowledge Base:

248025 How to configure clustered IIS virtual servers on Windows 2000 Advanced Server

To see a list of what is not supported in an IIS MSCS configuration, see the &quot;IIS and MSCS Implementation&quot; section of the following Microsoft Web site:

http://www.microsoft.com/technet/prodtechnol/windows2000serv/technologies/iis/deploy/confeat/webclust.mspx

Installation procedures
 Disable any real-time antivirus software on the computer. We recommend that you stop all these services for your particular antivirus software, including any real-time scanning. Use Cluster Administrator to move all the groups to node 1 that are not already on that node. To do this, right-click the groups that you want to move, and then click Move Group. Take all groups that contain IIS Server instances offline. If the group contains the shared disk resource, you may receive an error message that states that you cannot take the quorum resource offline. You can ignore this message.

Note Taking these groups offline prevents the cluster server from failing over during the installation of the .NET Framework because it involves an IISRESET command. Download the .NET Framework version that you want. To do this, visit the following Microsoft Web site:

http://msdn2.microsoft.com/en-us/netframework/aa569263.aspx

 Install the .NET Framework on node 1. Bring all the groups back online. Make sure that the IIS instances also come online. Move your groups to the second node.</li> Again, take all groups on node 2 that contain IIS Server instances offline. You may receive an error message that states that you cannot take the quorum resource offline. You can ignore this message.</li> Install the .NET Framework on node 2.</li> Bring all the groups back online and make sure that all IIS instances come online.</li> Move the groups back and forth between nodes to make sure that the failover is working correctly.</li></ol>

Configure the ASP.NET account
The framework has now been installed correctly. Next, you must configure the account that the ASP.NET pages will run under. To start ASP.NET worker processes in an MSCS configuration, we recommend that you create a common account between the two nodes to run your applications under. You can change this under the <processModel> section of the Machine.config file. This procedure resembles the steps to set up the common IUSR_machinename and IWAM_machinename accounts.

For more information about the steps to set up the common IUSR_machinename and IWAM_machinename accounts, click the following article number to view the article in the Microsoft Knowledge Base:

249603 Using IISSync to synchronize clustered Web sites on Windows 2000 Advanced Server

Note Before you run IISSync between the two nodes, make sure that the hotfix that is listed in the following Microsoft Knowledge Base article is installed so that the process finishes successfully:

326095 COMREPL utility does not respond when you install Microsoft .NET Framework

If you install MSCS on Microsoft Windows 2000 domain controllers, you may experience problems when you start the ASP.NET worker processes.

For more information, click the following article number to view the article in the Microsoft Knowledge Base:

315158 FIX: ASP.NET does not work with the default ASPNET account on a domain controller

<ol> Create a new domain account to use for the ASP.NET processes such as ASPNET. If you have not already done this, grant the appropriate permissions for this account.

For more information, click the following article number to view the article in the Microsoft Knowledge Base:

317012 Process and request identity in ASP.NET

Note When you install the .NET Framework on member servers, an ASPNET account is created locally on each node. Delete these accounts and use the domain account to maintain consistency between both nodes when a failover occurs.</li> On node 1, open the Machine.config file in Notepad. This file is located in the following folder:

Microsoft.NET\Framework\ \Config

Note In this path,  is the version of the .NET Framework that you installed in the &quot;Installation procedures&quot; section.</li> In the <processModel> section of the Machine.config file, change the userName attribute and the password attribute to the user name and the password of the account that you created in step 1.

Note Before you change this information, change the ASPNET password to something that is known. The installation of the .NET Framework generates a random password that prevents .aspx pages from working if you do not use a password such as the following:

userName=&quot;DomainName\ASPNET&quot; password=&quot;ASPNETpassword&quot;

</li> Change the Machine.config file on node 2 also to reflect the same information that you used in step 3, and then save the file.</li> Save the changes to the Machine.config file.</li> Open an .aspx page to test for functionality on node 1.</li> Do a failover on the group that contains your IIS server instances, and then open the same .aspx page on node 2.</li></ol>

You have now successfully configured the ASP.NET account on your cluster servers.

Additional query words: framework cluster MSCS ASP.NET server cluster

Keywords: kbhowtomaster KB324393

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.