I've got a DNN 7.3.2 instance installed on my desktop computer (Windows 7). The instance is using a SQL 2008 database that's on a separate server. The DNN instance appears to be running fine. When I installed it, though, I used some different settings than what you show in your installation videos. I've seen other videos (on Youtube) that do things a little differently than you did. I'm hoping to get clarification on what's truly needed and what is not. Here's some specifics...

- I gave the Network Service user modify, read & execute, list folder contents, read, and write permissions to the folder where the DNN site files were located. You did the same in your video.
- I gave the IIS_IUSRS user basic read & execute, list folder contents, and read permissions to the folder where the DNN site files were located. You did NOT do this in your video. Instead, you gave the IUSR user these permissions.
- When creating the site in IIS, the application pool I chose (i.e. ASP.NET v4.0) had ApplicationPoolIdentity for the identity property. I did NOT change this to Network Service as you did.

Will these deviations from what you did cause problems later on?

The AppPoold identity user should have FULL privileges for the files and folders in the website's directory. You will need to look at the properties of the AppPool to determine which user is the identiy user for the AppPool.

In the advanced properties window for the AppPool, click on the ApplicationPoolIdentity user which will get you to a window in which you can specify which accoun runs as the identity user. There's a dropdown box that lets you choose on of several built-in account, or you can create a custom user.

The "best practice" for this is to create a custom AppPool for each website on your server, and also create a custom identity user for the AppPool.

A lot of the confusion arises from older versions of Windows (maybe even Win7) where the Network Service account was a default for AppPools.