Update: The original question was for Windows Server 2008, but the solution is easier for Windows Server 2008 R2 and Windows Server 2012 (and Windows 7 and 8). You can add the user through the NTFS UI by typing it in directly. The name is in the format of IIS APPPOOL\{app pool name}. For example: IIS APPPOOL\DefaultAppPool.
IIS APPPOOL\{app pool name}
Note: Per comments below, there are two things to be aware of:
- Enter the string directly into the "Select User or Group" and not in the search field.
- In a domain environment you need to set the Location to your local computer first.
Reference to Microsoft Docs article: Application Pool Identities > Securing Resources
Original response: (for Windows Server 2008) This is a great feature, but as you mentioned it's not fully implemented yet. You can add the app pool identity from the command prompt with something like icacls, then you can manage it from the GUI. For example, run something like this from the command prompt:
icacls c:\inetpub\wwwroot /grant "IIS APPPOOL\DefaultAppPool":(OI)(CI)(RX)
Then, in Windows Explorer, go to the wwwroot folder and edit the security permissions. You will see what looks like a group (the group icon) called DefaultAppPool. You can now edit the permissions.
However, you don't need to use this at all. It's a bonus that you can use if you want. You can use the old way of creating a custom user per app pool and assigning the custom user to disk. That has full UI support.
This SID injection method is nice because it allows you to use a single user but fully isolate each site from each other without having to create unique users for each app pool. Pretty impressive, and it will be even better with UI support.
Note: If you are unable to find the application pool user, check to see if the Windows service called Application Host Helper Service is running. It's the service that maps application pool users to Windows accounts.
I recently installed Apache on Windows Server 2008.
I just downloaded the latest stable release for both software packages.
Note that for PHP, you need to keep this in mind (from http://windows.php.net/download/):
If you are using PHP with Apache 1 or Apache2 from apache.org you need to use the VC6 versions of PHP.
Now the installer will list Apache 2.x as a configuration option.
If you are able to install, but not configure PHP, please comment on my answer, and I will provide you with some directives on how to set up PHP for apache with 2 lines in the configuration file.
Best Answer
This is seems to be covered fairly well in
install.txt
included in the PHP zip downloads.Quoting from that file ...
With that caveat, should just be a matter of installing new version of PHP in new folder and updating IIS config to use the new path.