Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...networkservice to ApplicationPoolIdentity change in IIS7/8networkservice to ApplicationPoolIdentity change in IIS7/8
Previous
 
Next
New Post
4/12/2012 11:32 AM
 

OK so in IIS8 on Server 8, the application pool identity is now recommended.

QUOTE "Worker processes in IIS 6.0 and IIS 7 run as NETWORKSERVICE by default,..However, a problem arose over time as more and more Windows system services started to run as NETWORKSERVICE.
This is because services running as NETWORKSERVICE can tamper with other services that run under the same identity."

I resolved this web.config access issue (creating sub-portals or upgrading on a site moved to IIS8). 

So in IIS8 observe that in the applications pool, the DefaultAppPool identity is ApplicationPoolIdentity
Your site is routinely configured to allow control by the application through networkservice, this is in the dnn install docs.
So to modify this for your dnn site, in IIS do: site/properties/advanced/app pool and then update to (for example) DefaultAppPool

Then in (your dnn site) folder, properties, security, edit.
assign (for example)
IIS AppPool\DefaultAppPool
OK and give it full control, apply, OK

==
ref1 = http://learn.iis.net/page.aspx/624/application-pool-identities/
ref2 = http://technet.microsoft.com/en-us/li... 

=

QUESTION : All the foregoing is OK so far, but I haven't worked out how to find an IIS CUSTOM identity in the sitefolder/..security/ dialogue.

I tried with creating a  "Managed service account in the format domainname\accountname.
Important : leave the password blank, and ensure that the account name has a dollar sign ($) at the end.
5.Under Application Pool Tasks, click Stop, and then click Start."

But then I couldn't find it in the assign security properties dialogue.

 

 

 
New Post
4/12/2012 6:24 PM
 
When you configure permissions use

"IIS APPPOOL\websitename" as the user. When you create a website in IIS 7.5 (assume it is the same in 8) a new application is created called websitename (whatever you call the website)

That is the user you need to setup permissions for, but make sure you use the local computer as the location, not an active directory domain

Chris Hammond
Former DNN Corp Employee, MVP, Core Team Member, Trustee
Christoc.com Software Solutions DotNetNuke Module Development, Upgrades and consulting.
dnnCHAT.com a chat room for DotNetNuke discussions
 
New Post
6/28/2013 2:16 AM
 
Chris Hammond wrote:
When you configure permissions use

"IIS APPPOOL\websitename" as the user. When you create a website in IIS 7.5 (assume it is the same in 8) a new application is created called websitename (whatever you call the website)

That is the user you need to setup permissions for, but make sure you use the local computer as the location, not an active directory domain

 Hi Chris,

And what happen when you are hosting multiple sites under the same DNN installation, should we create one Application Pool per site and assign their rights to all these application pool users to the same DNN installation folder like C:\DNNSites\ ?

 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...networkservice to ApplicationPoolIdentity change in IIS7/8networkservice to ApplicationPoolIdentity change in IIS7/8


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out