Internet Information Services
Note: You are currently viewing documentation for Moodle 3.3. Up-to-date documentation for the latest stable version of Moodle is probably available here: Internet Information Services.
IIS installation steps (Windows 7 and above)
- Go to Control panel, click on Programs and Turn Windows features on or off
- Tick "Internet Information Services" and "Internet Information Services / Application Development Features / CGI"
- Install Microsoft Web Platform Installer
PHP installation steps
It is strongly recommended to use only the official MS Platform installer, it automatically installs all necessary components and facilitates easy configuration with PHP manager. Manual installation attempts often fail or may not allow Moodle to function properly. Unfortunately MS does not usually distribute up-to-date version of PHP, you may need to download them manually.
- Install Microsoft Web Platform Installer
- Install latest PHP 5.6.5 or above using Web Platform Installer
- [Optional] Install URL Rewrite 2.0 using Web Platform Installer
Optionally you may install the required components manually:
- Download PHP manager for IIS and install it
- Download latest PHP 5.6.5+ VC11 x86 Non Thread Safe from http://windows.php.net/download/
- Extract the Zip file to a directory such as C:\PHP\
- Install the Visual C++ Redistributable for Visual Studio 2012  - on 64bit Windows install both x86 and x64
- Open the Internet Information Service (IIS) Manager - right click on This computer and select Manage
- Click on PHP Manager icon
- Register new PHP version - select C:\PHP\php-cgi.exe
Warning: PHP needs to be configured via FastCGI in IIS, older CGI interface is known to have problems with some file names.
PHP configuration steps
- Set PHP configuration to values recommended by PHP Manager
- Enable required extensions in the PHP manager: php_intl.dll, php_pgsql.dll
- Enable OPcache extension
- Set your timezone in PHP.ini
- Set appropriate memory limits in PHP.ini
IIS configuration steps
- Setup URL rewriting described below
- Configure IIS to show detailed error pages.
- Set very long CGI timeout - 1 hour or better more.
- In IIS Manager add Moodle dirroot directory as a new virtual directory or set it as site directory
The function slash arguments is required for various features in Moodle to work correctly, as described in Using slash arguments.
IIS 7 should support relative path arguments by default. If it does not work try enabling the following in php.ini
cgi.fix_pathinfo = 1
If you can not modify registry as described below you may try manual configuration of rewrite rules, the PHP installation via Microsoft Web Platform Installer installs necessary URL Rewrite 2.0 module.
Add following rewrite rule to enable support for unicode file names in Moodle and to work around internal file length limitation breaking YUI file serving:
- Matches the Pattern - Regular Expressions -
- Action - Rewrite -
- Append query string - enabled
- Stop processing of subsequent rules - enabled
Optional UTF-8 file name fix
reg add HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\w3svc\Parameters /v FastCGIUtf8ServerVariables /t REG_MULTI_SZ /d REQUEST_URI\0PATH_INFO
By default IIS is configured to stop execution of any PHP script after 5 minutes of activity, this interferes with long running Moodle scripts such as upgrade or cron. The timeout should be increased to at least one hour.
The default IIS account is IIS_IUSRS, make sure it has appropriate access right to Moodle dirroot (read only) and dataroot (read/write) directories.
By default, IIS uses custom error pages that intentionally hide error details on production sites:
But when you're diagnosing problems in Moodle that's not very useful. You can temporarily disable these default error messages in IIS so that you see a specific Moodle error message. To achieve that set the "existingResponse" setting for Custom Error Pages in IIS to “PassThrough” for your Moodle site. The result will be that Moodle displays a more specific message about the error when a problem occurs:
The generic IIS "404" error message which normally does not reveal any details about the problem will no longer be displayed.
The debugging option in Settings>Site administration>Development>Debugging should also be enabled so that you see the debug messages.