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.
This guide, while written for installing Windows XP alongside an existing Windows 7 installation, should be enough to get you going.
http://www.howtogeek.com/howto/8790/dual-boot-your-pre-installed-windows-7-computer-with-xp/
I've read through the guide, and none of it looks like it would have an issue with Server 2003, but, as it's a process involving your hard drive and the data contained within, I suggest you take a full image of the drive or a backup of all your data before you make any changes with the guide.
Hope this helps :)
regards,
Steve
Best Answer
Just delete the file "bootmgr" in the root of your boot partition.
The post-Vista NTFS boot sector tries to load and run that file, but if it can't find it, it will happily run NTLDR and start the standard NT boot process, just like it used to do before.