Member Avatar for Eternal Newbie
Eternal Newbie 30 Newbie Poster

I'm unable to add IIS Apppool\<pool_name> into Permission for both Components and Folders. When using Check Name: seems like there was no matching Apppool name.
My system: IBM server - Windows Server 2003. Beside, I have no experience for Win 03, but have always success with Win 08 - Really needing helps here!

  • 1 Contributor
  • 0 Replies
  • 204 Views

Dani AI

Generated

Note for : the account form IIS APPPOOL\<pool_name> does not exist on Windows Server 2003 (IIS 6). That per-pool virtual account style was introduced later (IIS 7.5 / Windows Server 2008 R2). IIS 6 runs worker processes under built-in service accounts (Network Service, Local Service, LocalSystem) or a specific user you assign to the pool, so the Select Users dialog will not resolve IIS APPPOOL\<pool_name>.

How to fix the permissions issue: open IIS Manager -> Application Pools -> right-click the pool -> Properties -> Identity tab to see which account the pool uses. If it shows Network Service, give the folder permissions to the NETWORK SERVICE account (or NT AUTHORITY\NETWORK SERVICE) via Folder -> Properties -> Security -> Add. If the pool uses a custom user, grant NTFS and COM rights to that user and add it to the local IIS_WPG group so the worker process can run. If the site accesses resources on another server, remember Network Service authenticates on the network as the machine account (DOMAIN\MACHINENAME$), so remote shares must allow the machine account.

For Component / COM+ permissions: open Component Services -> Computers -> My Computer -> COM+ Applications (or DCOM Config for a specific component) -> right-click the application/component -> Properties -> Security tab. Choose Customize for Access and Launch/Activation permissions and add the same account the pool is running under (Network Service or the custom account), giving the required rights.

Best practice: create a dedicated low-privilege local or domain account per site, add it to IIS_WPG, set the app pool to use that account, and grant only the NTFS/COM rights required. Avoid running pools as LocalSystem. Also note Windows Server 2003 is out of support (end of support: July 14, 2015) — upgrading will give safer defaults and per-pool identities like IIS APPPOOL\<name>.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.