Run Multiple Versions of PHP on IIS

by Tali Smith


The ability to run multiple versions of PHP on one Internet Information Services (IIS) server can provide advantages when using the Microsoft® Web Platform. Some PHP applications rely on functions or features that are available only in certain versions of PHP. If you want to host these applications on one server, you must run different PHP versions side by side. The ability to run multiple versions of PHP on one IIS server also lets you test the newest release of PHP before deploying it to your live Web sites.

The IIS FastCGI handler fully supports running multiple versions of PHP on the same server. You can either use a different extension for each PHP version (for example, .php406 and .php411), or you can use multiple sites with the same base directory and then map the .php extension to the different PHP versions. Note, however, that maintaining multiple instances of PHP means more administrative overhead and more complicated troubleshooting. It is important to consider the consequences carefully before adding extra PHP instances.

Configure the Environment Variables

To run multiple versions of PHP on IIS, start by configuring the environment variables. For example, to use PHP 4 you must ensure that both the path to the PHP 4 root directory and the path to the dynamic-link libraries (DLLs) directory are included in your Path environment variable:

  1. Right-click on My Computer.

  2. Select Properties.

  3. Click on the Advanced tab.

  4. Click on the Environment Variables button.

  5. In the System Variables pane, scroll down until you see the Path variable.

  6. Select the Path variable, and then click the Edit button.

  7. At the beginning of the Variable Value field, type the names of the full paths to the PHP 4 root directory and to the DLLs directory. The path names must be separated by a semicolon.

    You must remove the PHPRC environment variable, because it tells PHP where to look for the Php.ini configuration file. If you have already set the PHPRC variable, follow the procedure above, but instead of editing the Path variable, select the PHPRC variable, and then press Delete.

Create FastCGI Application Process Pools

Next, you create FastCGI application process pools. For example, suppose you want to support PHP 4.4.8, PHP 5.2.1, and PHP 5.2.5 non-thread-safe. Place the corresponding PHP binaries in separate folders on the file system (for example, C:\php448\, C:\php521\ and C:\php525nts), and then create FastCGI application process pools for each PHP version:

C:\>%windir%\system32\inetsrv\appcmd set config /section:system.webServer/fastCGI /+[fullPath='c:\php448\php.exe']

C:\>%windir%\system32\inetsrv\appcmd set config /section:system.webServer/fastCGI /+[fullPath='c:\php521\php-cgi.exe']

C:\>%windir%\system32\inetsrv\appcmd set config /section:system.webServer/fastCGI /+[fullPath='c:\php525nts\php-cgi.exe']

If you have three Web sites (site1, site2, and site3) and each site must use a different PHP version, you can define handler mappings on each site to reference a corresponding FastCGI application process pool. Note that each FastCGI process pool is uniquely identified by a combination of fullPath and arguments properties.

C:\>%windir%\system32\inetsrv\appcmd set config site1 –section:system.webServer/handlers /+"..[name=’PHP448_via_FastCGI’,path=’*.php’,verb=’*’,modules=’FastCgiModule’,scriptProcessor=’c:\php448\php.exe’,resourceType=’Either’]

C:\>%windir%\system32\inetsrv\appcmd set config site2 –section:system.webServer/handlers /+"..[name=’PHP521_via_FastCGI’,path=’*.php’,verb=’*’,modules=’FastCgiModule’,scriptProcessor=’c:\php521\php-cgi.exe’,resourceType=’Either’]

C:\>%windir%\system32\inetsrv\appcmd set config site3 –section:system.webServer/handlers /+"..[name=’PHP525nts_via_FastCGI’,path=’*.php’,verb=’*’,modules=’FastCgiModule’,scriptProcessor=’c:\php525nts\php-cgi.exe’,resourceType=’Either’]


This article uses material from "Using FastCGI to Host PHP Applications on IIS 7.0" published on June 26, 2009.