Difference between revisions of "Internet Information Services"
Note: You are currently viewing documentation for Moodle 2.5. Up-to-date documentation for the latest stable version of Moodle may be available here: Internet Information Services.
(sync with 26 page)
m (Missing some important potential IIS account names depending on your version of IIS)
|Line 73:||Line 73:|
The default IIS account is ''IIS_IUSRS'',
The default IIS account is ''IIS_IUSRS'' , sure has appropriate access to Moodle dirroot (read only) and dataroot (read/write) directories.
Latest revision as of 22:13, 4 April 2014
IIS installation steps (Windows 7)
- 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 distribute up-to-date version of PHP, you need to download them manually.
- Manually download PHP manager for IIS or use the Miscrosoft Web Platform installer and install it
- Download latest PHP 5.5.x VC11 x86 Thread Safe from http://windows.php.net/download/ (you may also try the Non Thread Safe version)
- 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, older CGI interface is known to have problems with some file names.
PHP configuration steps
- 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
More configuration hints
IIS 7 should support relative path arguments by default, if it does not work try enabling following in your php.ini
cgi.fix_pathinfo = 1
Fix UTF-8 file names
By default IIS is unable to handle unicode characters in files uploaded into Moodle.
reg add HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\w3svc\Parameters /v FastCGIUtf8ServerVariables /t REG_MULTI_SZ /d REQUEST_URI\0PATH_INFO
URL rewriting workaround
If you can not modify registry as described above 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
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 or IUSR in IIS7, or IUSR_MachineName in older versions of IIS. Make sure the account has appropriate access rights to Moodle dirroot (read only) and dataroot (read/write) directories.
By default, IIS contains custom error pages that intentionally hide error details on production sites. When diagnosing problems you may want to disable temporarily the IIS Error Pages so you can see Moodle specific error messages, alongside enabling debugging in Settings>Site administration>Development>Debugging. This blog post about IIS error messages explains how to get more useful error messages when using IIS.