Thanks. I have two questions regarding the contents of that page:

1- Granting full access to the Network Service account to anything defeats its intended purpose - to be a an account with minimal access to the local server that can log in to remote resources. I assume there is additional documentation on how security is to be maintained on the DNN virtual directory and any resources accessed by it, and would appreciate a pointer to it.

2- In Windows Server 2008 R2, the Network Service account is being replaced by a managed service account called ApplicationPoolIdentity. Managed service accounts are new to R2, so perhaps the DNN docs need to be updated accordingly.

M.

Here is a good "definitive source": http://www.iis.net/search.aspx?q=Appl...

Basically, you set permissions on your files using the "virtual user" created by your app pool, instead of Network Service. I followed everything I could find, and still have permission errors until I located this solution: IIS System.Web.AspNetHostingPermission exception on Windows 7 RC

My issues were complicated by using Plesk, then "tweaking" on the backend using IIS. Trust me, if you're using Plesk also, then you want to keep this set to ApplicationPoolIdentity