We've just added a new development server to our office network running Windows Web Server 2008 with IIS7.5 and SQL 2008 R2.
We don't RDP to the server, instead we run IIS Manager and SQL Mgmt Studio remotely and the WWW folder is shared that we have mapped to our computers. Everything is working perfectly apart from one thing.
When we add a new website (and a new app pool is created) we can't set permissions for that new app pool through our shared drive or via RDP. We can see the app pool in IIS though and the super admin for our network can do this without any issues.
Example
User creates a new website/apppool called TEST. In the WWW folder, TEST -> Properties -> Security we try to add IIS AppPool\TEST but it can't find the object. Same thing happens via RDP. User has access to IIS AppPool\DefaultAppPool though.
Super Admin logs in to Dev server and can set permissions for all app pools.
This is quite weird since we're all local admins on the dev box and it's the users creating the AppPools.
Anyone have an idea how to resolve this?
Thanks
Respuesta1
Sounds about right, if I'm parsing the question correctly, but you say "via RDP" and "not using RDP", which makes it tricky to understand.
If I recall correctly, the "IIS AppPool\" provider is the Application Host Helper service, which runs on the local box.
I don't know if that's remotable, I'd assume not, but if it is remotable via RPC, that might explain why admin man can do it.