# How to assign permissions to ApplicationPoolIdentity account

In IIS 7 on Windows Server 2008, application pools can be run as the "ApplicationPoolIdentity" account instead of the NetworkService account.

How do I assign permissions to this "ApplicationPoolIdentity" account. It does not appear as a local user on the machine. It does not appear as a group anywhere. Nothing remotely like it appears anywhere. When I browse for local users, groups, and built-in accounts, it does not appear in the list, nor does anything similar appear in the list. What is going on?

I'm not the only one with this problem: see Trouble with ApplicationPoolIdentity in IIS 7.5 + Windows 7 for an example.

"This is unfortunately a limitation of the object picker on Windows Server 2008/Windows Vista - as several people have discovered it already, you can still manipulate the ACL for the app-pool identity using command line tools like icacls."

-

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.

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.

The windows service called Application Host Helper Service is the one that does the mappings between IIS and Windows users.

-
It is kind of an odd beast since it's not like a group where the user lives in a group, and it's not like a computer account vs. a user account which are completely different from each other. The app pool account 'overlaps' the app pool identity user. For example, you can have 5 app pools using Network Service and 5 others using custom accounts, but they are 10 different system managed app pool accounts. The advantages are noticed with the c:\inetpub\temp\appPools folder where it's managed automatically and locks the system cleanly. IIS leverages them well. Our use on folders is optional. – Scott Forsyth - MVP Nov 4 '09 at 23:12
Note that if you enter "IIS APPPOOL\DefaultAppPool" directly into the "Select User or Group" (instead of searching for it) when editing permissions, it will be recognized just fine (tested on Win7 x64 and Win2k8 R2 x64). – Milan Gardian Apr 7 '10 at 17:18
You're correct for Win7 and Win2k8 R2. It wasn't implemented in Win2k8 RTM, but is in R2. – Scott Forsyth - MVP Apr 17 '10 at 12:38
Finally got this - if you type the app pool name directly like @Milan Gardian says above and change the location field to the local machine then it works – Ciaran Bruen Jun 14 '13 at 10:49
Thank you so much for the 'two things to be aware of'. I was stumbling on both of these, and this was a clear and simple explanation of the problems and how to achieve what I needed to. It's just a shame none of the MSDN documentation was this clear. – Ian Grainger Nov 14 '13 at 11:00

You have to make sure that the 'From this location' field is set to the local machine and not the domain.

I had the same issue and once I changed that it worked fine.

-

After reading @Scott Forsyth - MVP answer I tried to restart the Application Host Helper Service. That solved the problem for me.

-

You should really be creating groups per "role" and assigning that group accesses on the filesystem. Then add the app pool to the role-specific groups as necessary. This way even if you remove the app pool later (and the virtual user goes poof), you dont have to worry about redoing all the permissions, you just add the replacement app pool to the existing group.

-

I was running WS8 R2 and I could not add IIS APPPOOL\DefaultAppPool via Windows Explorer. The only way it worked was via command line:

cacls [FILE PATH] /T /E /G "IIS APPPOOL\DefaultAppPool":C

-
Strangely, I had to do "IIS AppPool\DefaultAppPool" for it to be accepted. Notice the mixed case - all uppercase, as I did the first time, wasn't accepted from the GUI. – Jeff McJunkin May 19 '15 at 19:58

If this question is about how to execute _sp_send_dbmail in msdb database (using the SQL send Database Mail stored procedure in msdb), here is some work around. Add the .net application user name of your database (which is define on your connection string in your .net app) to the msdb user with "DatabaseMailUserRole" role membership

-