I am setting up a development version of DNN on a Vista 32 bit box with IIS7. I have unzipped all of the 5.3.1 version to my computer. I have created the web.config file from the development.config file. I have set the permissions to the website directory to give "Network Service" full control. However I still get a "Your site failed the permissions check." error. Additionally, I do not even see the graphics from that directory in the install wizard.

• I checked and the pool for the site uses the "Network Service" user
• I have tried giving "Everybody" full permissions to the directory. All that did was to add the images to the install wizard. (I them removed these permissions.
• I have tried giving the permissions to IIS_Users, Local service, Network, and NOC User (who wver that is) all with no impact.

I have done this dozens of times on a server but my dev box is giving me fits.

Any suggestions about where I might look for this difficulty?

I had thought about that. I had selected my machine as the search for selecting the group but now that I look at the list there is no "Network Service" on my machine. (it only exists on the domain). (I had also tried entering machinename\Network service but that failed.) I checked another machine and was the same. I changed the Authentication in IIS to enable the "Application pool idenity" to be the anonymous user. This got me the images but still not file permission check. Finally I tried moving the whole thing to wwwroot hoping that might have the correct permissions but again no luck.

ps the St. Louis DDN UG you got started is going strong. Ian is doing a great job.

Earlier in the question I said " I have set the permissions to the website directory to give "Network Service" full control. However I still get a "Your site failed the permissions check." error."

I do realize the danger of giving permissions to various users. "Everyone" in particular scared me. However, since I was having a permission problem to trouble shoot I set them, tested the effect, and then removed them. Giving those permissions for a couple of minutes inside my corporate network to a directory buried under various others seems like a reasonable approach.