Installing .NET 1.1 on Windows Server® 2008

For use with Enkompass versions 2.0 and later

Introduction

We strongly recommend that you install .NET 1.1 before installing Enkompass.

Enkompass 2.0 will automatically detect a .NET 1.1. installation. If the .NET 1.1 framework is installed, Enkompass will automatically make it available for WSO accounts.

Pre-installation considerations

Before installing .NET 1.1, you should consider a few key points:

• .NET 1.1 may break the ASP.NET state service
• The IIS_IUSRS group will need access permissions to the .NET 1.1 directories in order for .NET 1.1 to work properly with IIS7.
• Do not allow Enkompass to update applicationHost.config while installing .NET 1.1. Settings for .NET 1.1 are in applicationHost.config and must be saved to the Enkompass template before Enkompass overwrites applicationHost.config.
• .NET 1.1 is not an x64 application and will not appear in the IIS7 Manager.

Installation Procedure

Repeat the following procedures on all web servers controlled by Enkompass.

Preventing Enkompass from updating the applicationHost.config file

You may skip this step if this server does not yet have Enkompass installed on it.

To begin, you will need to disable and prevent Enkompass services from running during the installation.

1. Click the Start button.
2. Move your cursor over Administrative Tools and select the Services option from the resulting menu.

This will open the Services manager. Next, stop and disable each service that begins with Enkompass. (This will prevent Enkompass from updating the applicationHost.config file.)

To do this:

1. Select the service you wish to stop.
2. Click the Stop link in the upper left-hand corner of the window.
3. Right-click the service and select Properties.
4. Select Disabled from the Startup type pull-down menu.
5. Click the Apply button before closing the window.

Remember: You will need to repeat the process listed above for every entry that begins with Enkompass.

The Services manager window

Note: Not all services are installed on all servers.

Downloading and installing .NET 1.1 and its required packages

Take the following steps, downloading and installing the packages in the order specified:

1. Download and install the .NET 1.1 installer (dotnetfx.exe).
2. Download and install the .NET 1.1 service pack (NDP1.1sp1-KB867460-X86.exe).
3. Download and install the hotfix to the .NET service pack (NDP1.1sp1-KB886903-X86.exe).
4. Reboot the server.

Reinstalling ASP.NET

After you have rebooted the server, it is likely that the ASP.NET state service will not be functional. You can repair this problem by reinstalling ASP.NET:

1. Open a command prompt by clicking Start and selecting the Command Prompt option from the resulting menu.
2. Navigate to 1 of the 2 following directories using the cd command. (The directory to which you will navigate is dependent upon which other versions of the .NET framework you are running.)
   • C:\Windows\Microsoft.NET\Framework64\v4.0.30319 — Navigate to this directory if .NET 4.0 is installed on your system. (e.g. cd C:\Windows\Microsoft.NET\Framework64\v4.0.30319)
   • C:\Windows\Microsoft.NET\Framework64\v2.0.50727 — Navigate to this directory if .NET 4.0 is not installed on your system. (e.g. cd C:\Windows\Microsoft.NET\Framework64\v2.0.50727)
3. When you have accessed the appropriate directory, issue the following commands:
   • aspnet_regiis -u — This command uninstalls the version of ASP.NET that is currently non-functional on the system.
   • aspnet_regiis -i -enable — This command reinstalls the latest version of the .NET framework that corresponds to the directory in which you are working.

Note: At the time this article was written, .NET 4.0 was the most current version of the .NET framework. If you are using a later version of the .NET framework, you should navigate to the directory that corresponds to the version of the .NET framework you wish to use.

Fixing file permissions for IIS 7

In order for .NET 1.1 to work properly with IIS 7, you will need to fix some file permissions issues. To do this:

• Add read and execute privileges to C:\Windows\Microsoft.NET\Framework\v1.1.4322
• Add every privilege except take ownership to C:\Windows\Microsoft.NET\Framework\v1.1.4322\Temporary ASP.NET Files

For more information about working with file permissions in Windows Server 2008, please visit Microsoft's Understanding Windows File And Registry Permissions article.

Adding .NET 1.1's settings in applicationHost.config to the Enkompass template file

Note: You may skip this step if:

• This server does not yet have Enkompass installed on it.
• This server has not yet been added to an Enkompass cluster.

If you have already installed Enkompass and added this server to an Enkompass cluster, you will need to create a new template:

1. Navigate to C:\Windows\system32\inetsrv\config\
2. Copy and rename the enko_applicationHost.config file to enko_applicationHost.bak

Enkompass will automatically generate a new template file.

Re-enabling and restarting Enkompass services

Note: You may skip this step if you have not yet installed Enkompass on the server.

1. Click the Start button.
2. Move your cursor over Administrative Tools and select the Services option from the resulting menu.

This will open the Services manager. From here, start and enable each service that begins with Enkompass.

1. Select the service you wish to start.
2. Click the Start link in the upper left-hand corner of the window.
3. Right-click the service, and select Properties.
4. Select Automatic from the Startup type pull-down menu.
5. Click the Apply button before closing the window.

Remember: You will need to repeat the process listed above for every entry that begins with Enkompass.