Good Morning,

I'm an absolute newbie to DNN.  I need to install DNN 4.9.1 to a x64 Windows 2003 Server that hosts multiple sites, one of which is my client's site. 

Questoins:
1.  Where do I install DNN on the server?  Inetpub/www_root/client_site_folder ?
2.  I want the client's existing non-DNN site to remain active while I develop his new DNN site on the server.  How do I do this?

Also, please send any/all links to DNN 4.9.1 host installation tutorials.

Thanks so much for your help!!

You can put the DNN install anywhere that you like. When you configure the website in IIS, you will point at the root directory.

In IIS, just create a new website and configure it. It won't interfere with the client's existing site if you configure it properly. Generally, that means use a different name for the new site. Use the server's IP address, but use a "host header" to route a specific URL to the new website. You'll also need to set up your DNS for the new site.

If you look at the Tutorials page at this site, you'll find a TON of useful tutorials. I also find that Mitchel Sellers' website (mitchelsellers.com) to be quite useful. In particular, Mitchel has made an industry of his install and upgrade instructions. You'll find them in his blog.

Joe,

Thanks for your help. I decided it might be better to install DNN to a test folder c:\inetpub\www_root\xyz.com\test. I configured the SQL Server Express database DotNetNuke on the server and created login with dbo.owner as well.
In IIS, I created an application pool named xyz.com and created a new site named test.xyz.com. In the site properties, local path is set to above directory, application pool xyz.com plus all the other required settings.

Am I now ready to bring up the url xyz.com/test in my browser to execute the DNN install? If not, what other steps are needed?

Thanks,
Sid

Try browsing to the site and see it the DotNetNuke installation comes up. It should come up in the "Installation Wizard" mode, so just follow along with the instructions. Make sure to perform all of the tests at each stage.

Unfortunately I received a 403 forbidden when I called up www.xyz.com/test from my development machine.  A thought:  When I created the site in IIS, I specified it as test.xyz.com.  Should I have instead named it xyz.com/test ?

Thanks Much,

Sid

If the site is defined to be test.xyz.com, you should browse to that URL.

What happends when you do that?

Why did you use xyz.com/test?

This is what I get when I go to test.xyz.com
Server Application Unavailable
The web application you are attempting to access on this web server is currently unavailable. Please hit the "Refresh" button in your web browser to retry your request.

Administrator Note: An error message detailing the cause of this specific request failure can be found in the application event log of the web server. Please review this log entry to discover what caused this error to occur.

I used xyz.com/test as the install directory to keep the DNN files separate from his existing site files.

Joe,

I fixed it. Had to allow Network Service full control to domains folder under www_root.

Thanks so much for your help!!

Yes, that is correct.  That is covered in Mitchel Sellers' blog entries.  I'm sure that is also included in Lee's tutorials, too.