I have used the Microsoft Web Platform Installer to install both Drupal 6 and Drupal 7 on my Windows Server 2008 R2 servers running IIS 7.5. (see: http://www.microsoft.com/web/downloads/platform.aspx)

I'd like to know what file and folder permissions WebPI is modifying (and why) and the web.config additions it is making so that I can manually install Drupal under IIS for those times when the default installation parameters need to be tweeked (such as where the databases are housed).

Changes made to PHP to make it play nice with Windows + IIS would also be helpful.

3 Answers 3


You may be interested in this question.

However, a manual install of Drupal has a few variables.

For all versions of Drupal you will need to install PHP. The recommended way to install PHP is with Fast CGI. (That is also how the WebPI installs it.)

Since you are running Server 2008, it is recommended that you use Mirosoft's URL rewriter if you want clean URLs. (That is also how the WebPI installs it.) If you are using Microsoft's URL rewriter, it will automatically look for a web.config file. Drupal 7 ships with a default one, which I believe will work for Druapl 6 as well.

Then, you need a database. For Drupal 6 your only practical option is MySQL. For Drupal 7 you can choose between MySQL and the more native MSSQL.

Once those three items are installed you are pretty much left with permissions. By default IIS uses C:\inetpub\wwwroot\ for all web served files. For IIS to read those files the local IUSR account needs read permissions. To write the local IUSR account needs write permissions. I believe the recommended behavior currently is IUSR gets read permissions to everything in C:\Inetpub\wwwroot. However write permissions are restricted to only where absoultly needed. The traditional location is ..\sites[sitename]\files as that is the default location for user uploaded files. However Drupal 7 has a fancy web installer for modules. For that to work ..\sites[sitename]\modules and ..\sites\all\modules need to be writeable by the local IUSR account. One final note. For the default Drupal install process to work ..\sites[sitename]\settings.php needs to be writeable by the local IUSR account. However, post install it is usually recommended that file be read onle.


I can't provide a specific answer, but I would try running Process Monitor during the installation. It should the provide some of the answers you are looking for.


I highly recommend using WPI to install all the IIS modules necessary like the latest version of PHP, PHP to SQL and Wincache only. Then going to drupal.org to get everything else. I do not think WPI has the most optimal setup and you will have a lot more control of your setup. It is pretty easy once you do it this way a couple times and you really get to understand what configurations are possible. Drupal provides all kinds of features like Multisite, Custom Installation Profiles, Custom DB abstraction layers etc. I find something new and useful every say just by reading their code and using api.drupal.org.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.