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.
Shared disk of some sort is required for the disks that the MSMQ data will be stored on.
The cost of the SAN isn't the main
issue -- it's rather the fact that the
SAN becomes a single point of failure.
SANs aren't really considered a single point of failure. They have redundant controllers, redundant paths from the server to the SAN, redundant paths from the controllers to the spindles. If spindle failure is an issue you can clone the LUN to a second set of disks for maximum redundancy. If you have a second array you can even replicate from one array to another.
Most storage arrays are designed for 99.999% uptime if not more. Some are designed for 99.9999% uptime and some can provide even more uptime than that.
Best Answer
You could write 2 scripts: one to view information about the specific resource group and one to move the group. Then delegate rights to non-admin users to execute those scripts against the cluster(s) using System Frontier. The user won't have to have any rights on the server. Full disclosure... I own the company that makes System Frontier.