Skip to main content

Install Application Request Routing Version 2


Goal

To successfully install Microsoft Application Request Routing Version 2 for IIS 7 and its dependent modules. 
The ARR Version 2 installer package contains the following components:
  • Microsoft Application Request Routing Version 2 for IIS 7. 
  • Microsoft URL Rewrite Module Version 2 for IIS 7 RC2.
  • Microsoft Web Farm Management Version 1 for IIS 7.
  • Microsoft External Cache Version 1 for IIS 7.
The steps outlined in this document will install all four components.

Prerequisites

This walkthrough requires the following prerequisites:
  • IIS 7.0 on Windows 2008 (any SKU) or newer where Application Request Routing will be installed.
Important:  ARR Version 2 RTW supports upgrading from ARR Version 1 RTW and from ARR Version 2 RC. If any other version of ARR is already installed, uninstall both ARR and URL Rewrite before proceeding. Note that the corresponding configurations will be lost.

Step 1 - Download Microsoft Application Request Routing Version 2.

Download the Microsoft Application Request Routing release from the following locations:
  • Microsoft Application Request Routing Version 2 for IIS 7 (x86) here.
  • Microsoft Application Request Routing Version 2 for IIS 7 (x64) here.

Step 2 - Install Microsoft Application Request Routing Version 2.

To install Application Request Routing:
1. Open a command prompt with administrator user rights.
2. Stop the WAS and WMSVC processes by entering the following:
   net stop was /y
   net stop wmsvc /y
   This step is necessary because ARR installs a Hotfix (KB 954438).  
3. Run ARRv2_setup_<architecture>.exe:
   ARRv2_ setup_x86.exe
   or
   ARRv2_setup_ x64.exe
4. Accept the End User License Agreement (EULA). 
5. The installers for the four components are launched one after another.
6. Complete the installation.
7. To check the installation status, refer to the %TEMP%\arr_setup.log file. If all packages have installed successfully, you will see the following:
Completed the Microsoft Application Request Routing for IIS7 Setup.
Installation results - Look in the respective msi log files (msiname.log) for more details.
rewrite.msi   Success
webfarm.msi   Success
requestrouter.msi   Success
externaldiskcache.msi   Success
8. (Optional) For troubleshooting purposes, the downloaded executable can be unpackaged. Launch the executable file with /T:<full path> and /C options. This command will unpackage just the four MSIs, which can be launched manually one at a time. If the MSIs are installed manually, they must be installed in the following order:
rewrite.msi 
webfarm.msi 
requestrouter.msi 
externaldiskcache.msi   
For more information, launch the executable file with the /? option.
9. Start the WAS and WMSVC processes by entering the following:
   net start was
   net start wmsvc

Step 3 – Change application pool process model for Application Request Routing.

This step is optional but recommended.
All HTTP requests and responses for the content sites go through Application Request Routing. Given this, you would want the worker process for the Default Web Site on Application Request Routing to always run, regardless of whether the worker processes for some of the sites are running or not.
In this step, you will disable the Idle Time-Out under the application pool process model for the Default Web Site.
To change the application pool process model using the UI:
1.  Launch IIS Manager.
2.  Select Application Pools.
3.  By default, DefaultAppPool is the corresponding application pool for the Default Web Site. Select DefaultAppPool. In the Actions pane, under Edit Application Pool, click Advanced Settings….
4.  Change the Idle Time-out (minutes) value to 0 to disable the setting. Click OK to save the changes.

To change the application pool process model using the command-line:
1.  Open a command prompt with administrator user rights.
2.  Navigate to %windir%\system32\inetsrv.
3.  Using appcmd, enter appcmd.exe set apppool "DefaultAppPool" -processModel.idleTimeout:"00:00:00" /commit:apphost

Step 4 – Change application pool recycling settings for Application Request Routing.

This step is optional but recommended.
Similarly, disable the application pool recycle setting so that the application pool does not recycle unexpectedly for ARR.
To change the application pool recycle setting using the UI:
1.  Launch IIS Manager.
2.  Select Application Pools.
3.  By default, DefaultAppPool is the corresponding application pool for the Default Web Site. Select DefaultAppPool. In the Actions pane, under Edit Application Pool, click Recycling….
4.  Clear the Regular time intervals (in minutes) checkbox.
To change the application pool recycle setting using the command-line:
1.  Open a command prompt with administrator user rights.
2.  Navigate to %windir%\system32\inetsrv.
3.  Using appcmd, enter appcmd.exe set config -section:system.applicationHost/applicationPools /[name='DefaultAppPool'].recycling.periodicRestart.time:"00:00:00" /commit:apphost

Repair

Repairing Application Request Routing involves running the downloaded package again. Follow the steps outlined in Step 2 - Install Microsoft Application Request Routing Version 2.

Remove

To remove Application Request Routing completely, you must remove the four packaged components individually. 
1. Open Control Panel.
2. Click Program and Features.
3. Locate the following four components and uninstall one at a time:
    1. Microsoft Application Request Routing Version 2 for IIS 7
    2. Microsoft External Cache Version 1 for IIS 7
    3. Microsoft URL Rewrite Module Version 2 for IIS 7 RC2
    4. Microsoft Web Farm Framework Version 1 for IIS 7  

Summary

You have now successfully installed Application Request Routing and the dependent modules, and are ready to configure and use the features. For a quick overview and more information, see %PROGRAMFILES%\IIS\Application Request Routing\ARR_ReadMe.htm.


Labels:

Popular posts from this blog

Fixing Tanzu Kubernetes Pod to External Services Connectivity Issues with NSX-T

Fixing Tanzu Kubernetes Pod to External Services Connectivity Issues with NSX-T Last month I got a call from a customer who was pulling their hair out over a networking issue. They had just deployed VMware Tanzu Kubernetes Grid on their vSphere with Tanzu environment, everything looked good in the dashboards, all pods were running, but their applications inside the pods could not reach external databases running on traditional VMs in the same datacenter. The frustrating part was that some pods could reach external services perfectly fine, while others would just timeout. There was no clear pattern. Let me tell you how we figured this out and fixed it. The Initial Problem Here is what the customer setup looked like: vSphere 8.0 with Tanzu enabled NSX-T 4.1.2 for networking Three Tanzu Kubernetes clusters running different microservices applications External PostgreSQL database running on traditional VMs (non-Kubernetes) External API services running on another se...
Read more

Troubleshooting vSAN Storage Policy Migration Failures in VMware Cloud Foundation 9.0

Recently I had a customer who migrated their VMware infrastructure from vSphere 7.0 to VMware Cloud Foundation 9.0. After the migration, they wanted to update their vSAN storage policies to take advantage of the new vSAN ESA (Express Storage Architecture) features. However, when they tried to change the storage policy for their production VMs, the operation kept failing with a cryptic error message. The error they were getting was: "Cannot complete operation due to insufficient resources to satisfy current storage policy." This was strange because they had plenty of disk space available. The vSAN cluster was only at 45% capacity, and all the hosts were healthy. Let me walk through how we troubleshooted and fixed this issue. Understanding the Problem First, let's understand what was happening in their environment: They had a 6-node vSAN cluster running VCF 9.0 vSAN was configured with the new ESA architecture They were trying to migrate VMs fro...
Read more

Unlocking VMware Cloud Foundation 9.0: A Strategic Blueprint for Enterprise Transformation

The evolution of VMware under Broadcom represents not disruption, but clarification—a focused vision toward unified private cloud excellence. As organizations navigate this transformation, the opportunity has never been greater to build truly modern, efficient, and powerful infrastructure with VMware Cloud Foundation. After architecting VMware solutions across diverse enterprise environments, I've observed a pattern: organizations that embrace VMware Cloud Foundation (VCF) strategically—rather than viewing the transition as a burden—emerge with significantly more capable, cost-effective, and future-ready infrastructure. This post shares a practical framework for successfully modernizing your VMware environment, maximizing your investment, and positioning your organization for the AI-driven, cloud-native future. Understanding the VMware Cloud Foundation Vision Let's start with clarity about what Broadcom and VMware are building: VMware Cloud Foundati...
Read more